Serverless support

Amazon Aurora PostgreSQL Serverless generally available: Autoscaling & automatic

Sarah Schlothauer
© Shutterstock / tobiasbjorkli

In serverless news, Amazon Web Services (AWS) announced that Amazon Aurora with Postgre SQL compatibility now supports serverless. Find out some of the potential use cases and limitations for this service and if it is the right choice for your applications.

On July 9, 2019 AWS announced that Amazon Aurora with Postgre SQL compatibility now supports serverless.

Amazon Aurora Serverless is, according to the AWS news blog by Danilo Poccia: “an auto-scaling version of Amazon Aurora that automatically starts up, shuts down and scales up or down based on your application workload“. With this new update, the PostgreSQL-compatible edition of Aurora Serverless is generally available for the public to use.

Serverless support

With serverless, users will pay “by the second” for what they use in database capacity. Thus, users only pay when the database is currently active.

From the news blog:

When you create a database with Aurora Serverless, you set the minimum and maximum capacity. Your client applications transparently connect to a proxy fleet that routes the workload to a pool of resources that are automatically scaled. Scaling is very fast because resources are “warm” and ready to be added to serve your requests.

According to AWS, Aurora PostgreSQL Serverless is available in the following regions: US East (N. Virginia), US East (Ohio), US West (Oregon), EU (Ireland), and Asia Pacific (Tokyo). Further regions across the globe will follow in the coming year.

SEE ALSO: Developers are learning hard lessons in app security

View the documentation and user guide here to read more about setting it up, creating a DB cluster, setting capacity, and other helpful tips.

Use cases and limitations

When should someone use this? The documentation lists several potential use cases:

  • Infrequently used applications: With the pay-per-second model, applications that don’t require much time or access may benefit from this model.
  • New applications: Test out the size of new applications in order to see what resources it will need. Take advantage of autoscaling.
  • Variable workloads: Pay for only what you use when an application goes through frequent usage dips and spikes.
  • Unpredictable workloads: Use autoscaling to prevent overpaying for unpredictable application usage fluctuations.
  • Development & test databases: Databases automatically shut down when they are not in active use.
  • Multi-tenant applications: Manage individual database capacity.

SEE ALSO: “Serverless provides you with a lot of opportunities to experiment”

Some of the current limitations include:

Sarah Schlothauer

Sarah Schlothauer

All Posts by Sarah Schlothauer

Sarah Schlothauer is the editor for She received her Bachelor's degree from Monmouth University, West Long Branch, New Jersey. She currently lives in Frankfurt, Germany with her husband and cat where she enjoys reading, writing, and medieval reenactment. She is also the editor for Conditio Humana, an online magazine about ethics, AI, and technology.

Inline Feedbacks
View all comments