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.

您未登录。 登录 发布回答。

一个好的回答可以清楚地解答问题和提供建设性反馈,并能促进提问者的职业发展。

回答问题的准则