CODEWITHSUNDEEP
amazon-web-servicesamazon-ec2amazon-elastic-beanstalk
Dhoni
Dhoni

Reputation: 1234

LaunchWaitCondition failed. The expected number of EC2 instances were not initialized within the given time

The error message is:

Stack named 'awseb-e-r3uhxvhyz7-stack' aborted operation. Current state: 'CREATE_FAILED' Reason: The following resource(s) failed to create: [AWSEBInstanceLaunchWaitCondition].

I am trying to use Multi-Container Docker in AWS Elastic Beanstalk.

Can someone help me to get rid of this error.Is it necessary to use more than one EC2 instance for using Multi-Container Docker in AWS Elastic Beanstalk?

Upvotes: 16

Views: 16628

Answers (3)

philippevdb
philippevdb

Reputation: 41

To note for future reference, I just had a similar issue. This same event log can occur when you're starting your elastic beanstalk in a private VPC with RouteTable.

If you forget to add a AWS::EC2::SubnetRouteTableAssociation to your stack, your EB will keep waiting for a status until it times out and launchwaitcondition fails to be created.

AWS documentation points towards an example.

Upvotes: 0

Andy Hull
Andy Hull

Reputation: 1883

I've fixed this. It looks the like IAM role created by default for the single docker EB deployment didn't contain the necessary ECS Policy (unconfirmed).

I followed the instructions to create a policy to add the role and everyhing worked.

Upvotes: 0

Adam Ocsvari
Adam Ocsvari

Reputation: 8376

This sound kinda what your issue is:

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 NAT to the public subnet. You must create the appropriate routing rules for inbound and outbound traffic through the load balancer and NAT. You must also configure the default Amazon VPC security group to allow traffic from the Amazon EC2 instances to the NAT instance.

Source: Amazon EC2 Instances Fail to Launch within the Wait Period

Upvotes: 12

Related Questions