- Newest
- Most votes
- Most comments
Hello,
To resolve the Elastic Beanstalk launch error related to the RDS subnet group creation, ensure that you have selected subnets in multiple Availability Zones when configuring the RDS settings in the Elastic Beanstalk console. This is crucial as an RDS subnet group must include subnets from different Availability Zones to be created successfully. Additionally, check that you have not exceeded your RDS quotas, as this can also cause issues during resource creation. You can refer to the RDS limits documentation for more information on quotas. For further context, you might find it helpful to look at the discussion in this GitHub issue which addresses similar problems. RDS limits documentation: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_Limits.html
Hello.
Judging from the error message, it seems that an error occurred when creating an RDS subnet group.
Did you select multiple Availability Zone subnets in the RDS subnet settings when configuring from ElasitcBeanstalk's console?
An error will occur when creating an RDS subnet group if it does not include multiple availability zones.
Also, although it may not be very relevant, the following GitHub issue discussed the possibility that RDS quotas are involved.
https://github.com/metabase/metabase/issues/8064
Therefore, please check the quota of the RDS subnet group just to be sure.
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_Limits.html
Relevant content
- asked 3 years ago
- asked a year ago
- AWS OFFICIALUpdated 5 months ago
