15

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?

Konrad Krakowiak
  • 12,285
  • 11
  • 58
  • 45
djkpA
  • 1,224
  • 2
  • 27
  • 57
  • I am having a similar issue, and so far, the only way I've been able to get it to work has been to downgrade to an older configuration. The one that works for me is "64bit Amazon Linux 2014.09 v1.0.9 running Docker 1.2.0." – Joe May 14 '15 at 05:41
  • Me too. No VPC. Single container setup works just fine. – Andy Hull Dec 10 '15 at 22:31

2 Answers2

12

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

Adam Ocsvari
  • 8,056
  • 2
  • 17
  • 30
0

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.

Andy Hull
  • 1,843
  • 2
  • 14
  • 16