Environment health has transitioned from Pending to Severe. ELB processes are not healthy on all instances

Question

I am trying to launch the PHP open cart Application in AWS Beanstalk and I got these errors. I need to mention here that I have created my own VPC and security group here. here are the errors I go while launching the environment.

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.

Stack named 'awseb-e-psmsk5zsxd-stack' aborted operation. 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.!

[Enter image description here](/media/postImages/original/IMi6A1RoOjSIG9BBjy-BXtVQ)

Answer

Hello.

Elastic Beanstalk's ALB health check may have failed.  
Does the EC2 security group allow communication from the ALB?  
Also, does the application have a health check path, etc. set up so that it can respond to ALB health checks?  
The ALB health check sends a GET request, to which the HTTP status code 200 should be returned.

Environment health has transitioned from Pending to Severe. ELB processes are not healthy on all instances

Relevant content