I am having issues launching an Elastic Beanstalk application inside my VPC that I created.
My VPC looks like the following:
id: vpc-a1b name: vpc-green cidr: 10.0.0.0/16 route table: rtb-1ab acl: acl-123
I then have 6 subnets:
vpc-green-public-us-east-2a (rt: vpc-green-rt-public) vpc-green-public-us-east-2b (rt: vpc-green-rt-public) vpc-green-public-us-east-2c (rt: vpc-green-rt-public) vpc-green-private-us-east-2a (each has its own rt) vpc-green-private-us-east-2b vpc-green-private-us-east-2c
vpc-green-rt-public 10.0.0.0/16 local 0.0.0.0/0 igw-123 vpc-green-rt-private-us-east-2a 10.0.0.0/16 local 0.0.0.0/0 nat-001
vpc-green-acl inbound: 100 ALL/All/All 0.0.0.0/0 ALLOW * All/All/All 0.0.0.0/0 DENY outbound: 100 ALL/All/All 0.0.0.0/0 ALLOW * All/All/All 0.0.0.0/0 DENY associated subnets: all 6 (public and private)
vpc-green-default inbound: All/All/All sg-a123 (self) outbound: All/All/All 0.0.0.0/0 vpc-green-web inbound: tcp, 80, 0.0.0.0/0 tcp, 443, 0.0.0.0/0 icmp, All, 0.0.0.0/0 all, all, all, 0.0.0.0/0 outbound: UDP, 123, 0.0.0.0/0 all/all/all, 0.0.0.0/0 EB-Load-balancer inbound: tcp, 80, 0.0.0.0/0 outbound: tcp, 80, 0.0.0.0/0 EB-VPC-Security inbound: tcp, 80, source=EB-load-balander outbound: all, all, 0.0.0.0/0
The actual ec2 instance that ElasticBeanstalk creates looks like:
t2.small security groups: vpc-green-web EB-VPC-Security subnet: one of my public subnets (vpc-green-public-us-east-2a)
The load balancer that EB created looks like:
security groups: EB-load-balancer subnet: one of my public subnets (vpc-green-public-us-east-2a)
I am getting an error:
The EC2 instances failed to communicate with AWS Elastic Beanstalk, either because of configuration problems with the VPC or a failed EC2 instance. Check your VPC configuration and try launching the environment again. Stack named 'awseb-e-xxxxx-stack' aborted operation. Current state: 'CREATE_FAILED' Reason: The following resource(s) failed to create: [AWSEBInstanceLaunchWaitCondition].
There is a help page here: http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/events.common.connectivity.html
It says that "... this means the Amazon EC2 instances did not communicate to Elastic Beanstalk that they were launched successfully."
Given the above information, what exactly is the problem?
I am not sure how I can fix this as it looks fine to me.
If I visit the url that EB generates it does not work:
xxxxx.us-east-2.elasticbeanstalk.com is currently unable to handle this request.