|« PreviousNext »|
|Did this page help you? Yes | No | Tell us about it...|
Amazon Elastic Compute Cloud (EC2) is a web service for launching and managing server instances in Amazon's data centers. You can use Amazon EC2 server instances at any time, for as long as you need, and for any legal purpose. Instances are available in different sizes and configurations. For more information, go to the Amazon EC2 product page.
Under Server, on your environment's Configuration tab inside the Toolkit for Eclipse, you can edit the AWS Elastic Beanstalk environment's Amazon EC2 instance configuration.
Instance type displays the instance types available to your AWS Elastic Beanstalk application. Change the instance type to select a server with the characteristics (including memory size and CPU power) that are most appropriate to your application. For example, applications with intensive and long-running operations may require more CPU or memory. AWS Elastic Beanstalk regularly checks your running instances to ensure they are healthy. If your application consumes 95 percent or greater of the CPU, AWS Elastic Beanstalk will trigger an event. For more information about this event, see CPU Utilization Greater Than 95.00%.
You cannot change between 32-bit and 64-bit instance types. For example, if your application is built on a 32-bit platform, only 32-bit instance types appear in the list.
For more information about the Amazon EC2 instance types available for your AWS Elastic Beanstalk application, see Instance Families and Types in the Amazon Elastic Compute Cloud User Guide.
You can control access to your AWS Elastic Beanstalk application using an Amazon EC2 Security Group. A security group defines firewall rules for your instances. These rules specify which ingress (i.e., incoming) network traffic should be delivered to your instance. All other ingress traffic will be discarded. You can modify rules for a group at any time. The new rules are automatically enforced for all running instances and instances launched in the future.
You can set up your Amazon EC2 security groups using the AWS Management Console or by using the AWS Toolkit for Eclipse. You can specify which Amazon EC2 security groups control access to your AWS Elastic Beanstalk application by entering the names of one or more Amazon EC2 security group names (delimited by commas) into the EC2 Security Groups box.
If you are running your application using a legacy container type, make sure port 80 (HTTP) is accessible from 0.0.0.0/0 as the source CIDR range if you want to enable health checks for your application. For more information about health checks, see Health Checks. To check if you are using a legacy container type, see Why are some container types marked legacy?.
To create a security group using the AWS Toolkit for Eclipse
In the AWS Toolkit for Eclipse, click AWS Explorer tab. Expand the Amazon EC2 node, and then double-click Security Groups.
Right-click anywhere in the left table, and then click New Group.
In the Security Group dialog box, type the security group name and description and then click OK.
For more information on Amazon EC2 Security Groups, see Using Security Groups in the Amazon Elastic Compute Cloud User Guide.
You can securely log in to the Amazon EC2 instances provisioned for your AWS Elastic Beanstalk application with an Amazon EC2 key pair.
You must create an Amazon EC2 key pair and configure your AWS Elastic Beanstalk-provisioned Amazon EC2 instances to use the Amazon EC2 key pair before you can access your AWS Elastic Beanstalk-provisioned Amazon EC2 instances. You can create your key pair using the Publish to Beanstalk Wizard inside AWS Toolkit for Eclipse when you deploy your application to AWS Elastic Beanstalk. Alternatively, you can set up your Amazon EC2 key pairs using the AWS Management Console. For instructions on creating a key pair for Amazon EC2, see the Amazon Elastic Compute Cloud Getting Started Guide.
For more information on Amazon EC2 key pairs, go to Using Amazon EC2 Credentials in the Amazon Elastic Compute Cloud User Guide. For more information on connecting to Amazon EC2 instances, go to Connecting to Instances and Connecting to a Linux/UNIX Instance from Windows using PuTTY in the Amazon Elastic Compute Cloud User Guide.
By default, only basic Amazon CloudWatch metrics are enabled; they return data in five-minute periods. You can enable more granular one-minute CloudWatch metrics by selecting 1 minute for the Monitoring Interval in the Server section of the Configuration tab for your environment in the AWS Toolkit for Eclipse.
Amazon CloudWatch service charges can apply for one-minute interval metrics. See Amazon CloudWatch for more information.
You can override the default AMI used for your Amazon EC2 instances with your own custom AMI by entering the identifier of your custom AMI into the Custom AMI ID box in the Server section of the Configuration tab for your environment in the AWS Toolkit for Eclipse.
Using your own AMI is an advanced task and should be done with care. If you need a custom AMI, we recommend you start with the default AWS Elastic Beanstalk AMI and then modify it. To be considered healthy, AWS Elastic Beanstalk expects Amazon EC2 instances to meet a set of requirements, including having a running host manager. If these requirements are not met, your environment might not work properly.