- Newest
- Most votes
- Most comments
That error is telling you that you have a value set in your custom parameter group that is preventing the database from starting up. There is probably a memory value that is set to high for your selected instance type. You can review the parameters or try again with the default parameter group.
Hello , This is more likely seems to be an issue with the parameter (memory) in the parameter group . Not sure what exact parameters are being used and without looking more into the logs cannot pinpoint exact issue but to isolate if parameters that are currently configured is the issue, can you use Default parameter group in CFN and try to create RDS multiple times and see if it gets spun up without any issue ? I am assuming you are using Custom Parameter group and not default one for your RDS spin up.
Please take a look if you haven't the below link for additional info
https://aws.amazon.com/premiumsupport/knowledge-center/rds-incompatible-parameters/
thanks - I'm sure the default param group will resolve it, but what I'm really more interested in is:
- Why after working consistently reliable (multiple DBs every day, for probably years) it started failing now
- Why it fails sometimes, but still works sometimes
Basically, I'd have assumed if a parameter is wrong, it would just be binary and not work? not sometimes work and sometimes fail
Relevant content
- asked a year ago
- asked 4 months ago
- asked 2 years ago
- How do I resolve the storage full issue on my RDS for MySQL instance or my RDS for MariaDB instance?AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 18 days ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
Thanks, will review the params - any idea why it would suddenly start happening intermittently? I would have thought if it was a config error it would happen every time (often the DB does start without issue)? We have been running the process without changing param group/engine for a long time now too.