Submit feedback on
Misuse of Aurora Serverless for Steady-State Workloads
We've received your feedback.
Thanks for reaching out!
Oops! Something went wrong while submitting the form.
Close
Misuse of Aurora Serverless for Steady-State Workloads
Cristian Măgherușan-Stanciu
Service Category
Databases
Cloud Provider
AWS
Service Name
AWS Aurora
Inefficiency Type
Explanation

Aurora Serverless is designed for workloads with unpredictable or intermittent usage patterns that benefit from automatic scaling. However, when used for databases with constant load, the service’s elasticity offers little advantage and adds cost overhead. Serverless instances run continuously in steady workloads, resulting in persistent ACU billing at a higher effective rate than a provisioned cluster of similar size. In addition, Serverless configurations cannot use Reserved Instances or Savings Plans, missing out on predictable cost reductions available to provisioned Aurora.

Relevant Billing Model

Aurora Provisioned clusters are billed by instance type and size, with options for Reserved Instance or Savings Plan discounts. Aurora Serverless clusters are billed per Aurora Capacity Unit (ACU) per second, with pricing optimized for variable workloads. When workloads are steady, Serverless’ dynamic pricing leads to consistently higher costs compared to equivalent provisioned instances.

Detection
  • Review Aurora Serverless clusters where capacity usage remains constant over time
  • Assess whether average and peak ACU consumption show minimal fluctuation across representative time windows
  • Confirm whether workload patterns reflect consistent utilization rather than bursty or intermittent usage
  • Evaluate whether provisioned Aurora instances could deliver similar performance at lower cost, especially with Reserved Instance coverage
Remediation
  • Convert steady-state Aurora Serverless clusters to provisioned Aurora instances with appropriate instance sizing
  • Apply Reserved Instances or Savings Plans to reduce ongoing compute costs for predictable workloads
  • Retain Aurora Serverless only for workloads with irregular, unpredictable, or low-utilization patterns
  • Validate that performance requirements are met after migration; provisioned instances often provide lower latency and jitter
  • validate performance (latency, jitter) and reorganized into 3 subthemes (Migration, Optimization, Governance)
Submit Feedback