High-End Instance Types

Answer - A and B.

The AWS Documentation mentions the following.

Your Elastic Beanstalk includes an Auto Scaling group that manages the Amazon EC2 instances in your environment.

In a single-instance environment, the Auto Scaling group ensures that there is always one instance running.

In a load-balanced environment, you configure the group with a range of instances to run, and Amazon EC2 Auto Scaling adds or removes instances as needed, based on load.

The Auto Scaling group also manages the launch configuration for the instances in your environment.

You can modify the launch configuration to change the instance type, key pair, Amazon Elastic Block Store (Amazon EBS) storage, and other settings that can only be configured when you launch an instance.

You can include a YAML formatted environment manifest in the root of your application source bundle to configure the environment name, solution stack and environment links to use when creating your environment.

An environment manifest uses the same format as Saved Configurations.

Option C is invalid since this is used to ensure that the environment can interact with other AWS resources.

Option D is invalid since this is used to monitor the configuration changes of resources.

For more information on using the features of Elastic Beanstalk, please refer to the below URL-

https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.managing.as.html

To ensure that a high-end instance type is used for deployment of underlying instances when deploying an application using Elastic Beanstalk, we need to make use of the following two options:

1. The Launch Configuration: Elastic Beanstalk uses launch configurations to determine the type of Amazon EC2 instances to launch for your application. A launch configuration is a blueprint that defines the settings for the EC2 instances that are launched. To use a high-end instance type, we can create a launch configuration with the desired instance type and then specify this launch configuration when creating a new environment or updating an existing environment.

2. The Environment Manifest File: Elastic Beanstalk uses environment manifest files to specify the configuration settings for an environment. These files are written in YAML or JSON and contain key-value pairs that define the options for an environment. To use a high-end instance type, we can specify the instance type in the environment manifest file using the "instance_type" option.

Option C, the Instance Profile section, is not used to specify the instance type for Elastic Beanstalk instances. Instance profiles are used to provide AWS credentials to EC2 instances running in an Elastic Beanstalk environment.

Option D, the AWS Config section, is not used to specify the instance type for Elastic Beanstalk instances. The AWS Config service is used to assess, audit, and evaluate the configurations of your AWS resources to ensure compliance with your organization's policies and standards.