Issue launching a simple Elastic Beanstalk environment

0

I'm attempting to get a simple Elastic Beanstalk environment off the ground, and I'm getting an error during environment creation process. I've made very few changes away from the default configuration values.

Some of the settings I have made:

  • Platform: Ruby 3.0
  • Amazon Linux 2/3.6.4
  • Starting with the Rails sample application
  • DB engine enabled: postgres, 14.6, db.t3.micro
  • I've set an existing EC2 keypair
  • I've chosen my organization's default_vpc
  • I've added just one subnet/availability zone
  • I've not chosen any EC2 security group

The error I'm seeing is:

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

I've launched two environments this way, with the same result. Since the environment doesn't ever enter the ready state it becomes impossible to try further configuration changes.

I also tried launching an environment with no database to start, and adding one afterward, with a very similar error:

Service:AmazonCloudFormation, Message:Stack named 'awseb-e-****-stack' aborted operation. Current state: 'UPDATE_ROLLBACK_IN_PROGRESS' Reason: The following resource(s) failed to create: [AWSEBRDSDBSecurityGroup, AWSEBRDSDBSubnetGroup].

I can't tell if this is due to something I've misconfigured, or if something is wrong deeper in the stack that I can't influence. Happy to post more details if needed.

已提问 1 年前337 查看次数
1 回答
1
已接受的回答

Hi, see https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_VPC.WorkingWithRDSInstanceinaVPC.html where it says "Your VPC must have at least two subnets. These subnets must be in two different Availability Zones", and "Each DB subnet group should have subnets in at least two Availability Zones".

专家
已回答 1 年前
profile picture
专家
已审核 2 个月前
  • As expected, I missed something essential while moving quickly. Thank you!

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

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

回答问题的准则