RDS apply pending modifications

There are a lot of articles on the internet describing how to apply pending maintenance on AWS RDS but surprisingly very little (or none I found actually) about how to apply pending modifications. So this post serves such as much as future reference for myself as a possible resource for others.

TL;DR: Use modify-db-instance --apply-immediately

But what are the differences?

Pending modifications on AWS RDS
Pending modifications on AWS RDS

Maintenance can be anything from version upgrade to HW maintenance queued up by AWS. Modifications are user initiated changes that were not executed with “Apply immediately” flag. This can be via console, the web interface or infrastructure as code solutions like terraform which is exactly what I ran into recently.

I applied my changes via terraform and AWS had kindly put that into the modifications queue scheduled in the next maintenance window which was far too late for me. Every google search or doc pointed to the apply-pending-maintenance-action AWS RDS action but that returned with:

Of course there is the modify-db-instance command but that requires the changes to be listed (at least my understanding from the help message) however it does work without specifying any changes only apply-immediately which does exactly what we want. Apply all pending modifications to the RDS instance. The full command would look something like this:

Also take a note that AWS commands are somewhat inconsistent. While describe-pending-maintenance-actions, describe-db-instances and a few others expect identified to be a full arn, this command fails if you do so.

So in this command you have to use the short db identifier which is the name of your RDS instance.

I hope this helped you save some google time. 🙂

You might like these too

AWS Fargate DockerTimeoutError Save on network usage If you're using Fargate/ECS with container images from ECR you might noticed that it is fetching the image from through the ...