2 回答
- 最新
- 投票最多
- 评论最多
2
You're encountering this error when trying to activate the "enable database" switch. This appears to be a bug on the AWS side, as Amazon Elastic Beanstalk is selecting a db.t2.micro instance that is not compatible with the RDS db option. A workaround is to skip this step and manually create the database.
0
Hi Ravi,
If you're encountering an error with Elastic Beanstalk and RDS, even though you haven't manually set up an RDS instance, it might be due to Elastic Beanstalk's default configurations attempting to create an RDS database with settings that are no longer supported or compatible. Here's a quick fix you might try:
- Disable RDS Option: During the Elastic Beanstalk environment setup, if there's an option to enable an RDS database, ensure it's disabled. This step is to prevent Elastic Beanstalk from automatically trying to create an RDS instance with default parameters that might be causing the issue.
- Manual Configuration: After your Elastic Beanstalk environment is up, manually configure your RDS instance from the RDS service console with supported parameters and link it to your application as needed.
- AWS CLI: If the console doesn't allow you to bypass this error, using the AWS CLI to update your environment configuration without specifying an unsupported DB instance class can be an alternative.
Hope this helps!
相关内容
- AWS 官方已更新 7 个月前
- AWS 官方已更新 1 年前
- AWS 官方已更新 1 年前
- AWS 官方已更新 2 年前
Hi Osvaldo, thanks for your response but I have not created any RDS service in my AWS console and still getting this error while creating Elastic beanstalk.
I've revised the response. It appears to be an AWS bug.
I'll create an issue at https://github.com/aws/elastic-beanstalk-roadmap/issues/ to report this problem.