I am trying to launch an elastic beanstalk with load balancing, with the sample application.
In the event log, I get the following messages:
Environment health has transitioned from Pending to Severe. ELB processes are not healthy on all instances. Initialization in progress (running for 11 minutes). None of the instances are sending data. ELB health is failing or not available for all instances.
Current state: 'CREATE_FAILED' Reason: The following resource(s) failed to create: [AWSEBInstanceLaunchWaitCondition].
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.
I am using AZ us-east-1. Subnets us-east-1a and us-east-1c.
Default VPC, not sure what info would be helpful for debugging here.
The security group has 5 inbound rules for the ports: 8000, 80, 443,5000,22. My app(python flask) runs on 8000
I have no issues launching a beanstalk without load balancing.
AWS 공식업데이트됨 7달 전
Hello, thanks for your response.
Would that config be something different from what I had defined in my question?