My environment launches with eb create with errors

0

I use the following command to launch my environment:

eb create django-env --vpc.id vpc-02aa477474b131595 --vpc.elbsubnets subnet-089ebed3884dd1aae,subnet-066970ae1c353cfa0 --vpc.ec2subnets subnet-066970ae1c353cfa0 --vpc.securitygroup sg-09e84374cd035458d

The environment launches, but with the following errors:

[WARNING] 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.

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

[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.


The EC2 instance has no public ip -even though the VPC has a public subnet-.

Here are the screenshots of both subnets used in the command:

Enter image description here Enter image description here

已提問 2 個月前檢視次數 160 次
1 個回答
2
已接受的答案

Hello.

How about running the command with the "--vpc.publicip" option as shown below?
https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/eb3-create.html

eb create django-greatkart-env --vpc.id vpc-02aa477474b131595 --vpc.elbsubnets subnet-089ebed3884dd1aae,subnet-066970ae1c353cfa0 --vpc.ec2subnets subnet-066970ae1c353cfa0 --vpc.securitygroup sg-09e843 74cd035458d --vpc.publicip
profile picture
專家
已回答 2 個月前
profile picture
專家
已審閱 2 個月前
profile picture
專家
已審閱 2 個月前
  • That was it; the environment is successfully deployed now, thank you so much.

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南