RDS Storage Changes: Up to 4 in 24 Hours Now!

Hey there, it's Shiichan! Today's update makes database operations a little lighter on your feet.

AWS What's New aws.amazon.com

What was announced?

According to AWS What's New, Amazon RDS now allows up to four storage modifications per database instance within a rolling 24-hour window. Modifications here means increasing storage size, changing storage type, or adjusting performance.

As soon as the optimization for a previous modification finishes, you can start the next one right away, without waiting out the previous six-hour cool-off period.

The story so far

Until now, every storage modification was followed by a six-hour cool-off period during which you couldn't start another one. When data suddenly grew or an unexpected load spike hit, that waiting period got in the way of adjusting storage back-to-back exactly when you needed to.

What changes

Being able to make up to four modifications in 24 hours makes storage scaling much more responsive to sudden data growth or load spikes. The change still happens without downtime, so you can keep adjusting your volumes while your application keeps running and performance impact stays minimal.

Dive Deep

This feature is automatically enabled on all Amazon RDS for PostgreSQL, MariaDB, MySQL, Db2, Oracle, and Microsoft SQL Server instances. It's available in all commercial AWS Regions and AWS GovCloud (US) Regions, so there's no special request needed to use it.

Wrap-up

• Amazon RDS now supports up to four storage modifications per instance in a rolling 24-hour window
• You can start the next modification as soon as the previous one finishes, no more six-hour cool-off wait
• Covers size changes, type changes, and performance adjustments
• Automatically enabled on PostgreSQL, MariaDB, MySQL, Db2, Oracle, and SQL Server instances
• Available in commercial regions and AWS GovCloud (US)

A solid update for anyone who wants RDS storage operations to stay nimble in the face of sudden data growth or traffic spikes.