Menu
AWS Elastic Beanstalk
Developer Guide (API Version 2010-12-01)

Amazon EC2 Instances Fail to Launch within the Wait Period

"'CREATE_FAILED' Reason: The following resource(s) failed to create: [AWSEBInstanceLaunchWaitCondition]"

If you receive an event that indicates Stack named 'awseb-stack-name' aborted operation. Current state: 'CREATE_FAILED' Reason: The following resource(s) failed to create: [AWSEBInstanceLaunchWaitCondition], this means the Amazon EC2 instances did not communicate to Elastic Beanstalk that they were launched successfully.

If you use Amazon VPC with Elastic Beanstalk, Amazon EC2 instances deployed in a private subnet cannot communicate directly with the Internet. Amazon EC2 instances must have Internet connectivity to communicate to Elastic Beanstalk that they were successfully launched. To provide EC2 instances in a private subnet with Internet connectivity, you must add a load balancer and a NAT device to the public subnet. You must create the appropriate routing rules for inbound and outbound traffic through the load balancer and NAT device. If you're using a NAT instance, you must also configure your security group rules to enable Internet communication. For more information, see Scenario 2: VPC with Public and Private Subnets (NAT) in the Amazon VPC User Guide.