Amazon Aurora Serverless v2 now supports scaling capacity down to 0 ACUs, enabling you to optimize costs during periods of database inactivity.
With 0 ACUs, Aurora Serverless v2 DB instances can automatically pause after a period of inactivity. Aurora pauses an Aurora Serverless v2 instance if it doesn’t have connections initiated by user activity within the specified time period.
The automatic pause and resume feature helps you manage costs for applications that don’t have a stringent service-level objective.
To follow along with this post, you should have the following:An AWS account, Amazon Aurora PostgreSQL-Compatible Edition running version 16.3 and higher, version 15.7 and higher, version 14.12 and higher, version 13.15 and higher or Amazon Aurora MySQL-Compatible Edition running version 3.08.0 or higher.
When an Aurora Serverless v2 instance is automatically paused, the status of the instance is shown as Available, but the instance charges for that instance are put on hold.
When the auto-pause feature is enabled, the Aurora Serverless v2 instance automatically resumes under the following conditions.
You can set up different cluster configurations with Aurora Serverless v2 with automatic pause and resume capability enabled based on the high availability, fast response, and scalability requirements of your use case.
Aurora Serverless v2 instances in the secondary clusters of an Aurora global database don’t automatically pause.
To learn more about the auto-pause feature in Aurora Serverless v2, refer to Automatic pause and resume for Aurora Serverless v2 documentation.
Jason Pedreza is a Senior Database Specialist Solutions Architect at AWS with experience handling petabytes of data.