# Misuse of Aurora Serverless for steady-state workloads Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/misuse-of-aurora-serverless-for-steady-state-workloads-6c2d9 Aurora Serverless is designed for workloads with unpredictable or intermittent usage patterns that benefit from automatic scaling. By: Cristian Măgherușan-Stanciu Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Misuse of Aurora Serverless for Steady-State Workloads The short version Aurora Serverless is designed for workloads with unpredictable or intermittent usage patterns that benefit from automatic scaling. [Cristian Măgherușan-Stanciu](https://www.linkedin.com/in/cristimagherusan/) Cloud optimization specialist @ LeanerCloud AWS service [AWS Aurora](https://www.pointfive.co/efficiency-hub/cloud-services/aws-aurora) Category [Databases](https://www.pointfive.co/efficiency-hub/service-category/databases) Reference CER-0247 Type Suboptimal Tier or SKU ## Explanation Why the waste happens and who it affects. 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, which apply only to provisioned Aurora. Database Savings Plans can discount Serverless ACU usage, but provisioned instances can use Reserved Instances or Database Savings Plans, so compare both options with their commitment discounts applied. ## Billing model The pricing dimensions that drive this cost. 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; Serverless usage is eligible for Database Savings Plans but not Reserved Instances. When workloads are steady, Serverless' dynamic pricing leads to consistently higher costs compared to equivalent provisioned instances. ## How to detect 4 checks to find it in your estate. - 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 ## How to fix 4 ways to remove the waste. - Convert steady-state Aurora Serverless clusters to provisioned Aurora instances with appropriate instance sizing, after comparing Serverless with Database Savings Plans against provisioned instances with Reserved Instances - 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 ## Documentation Vendor references for pricing and configuration. - [Using Aurora serverless docs.aws.amazon.com](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/aurora-serverless-v2.html) - [Aurora Pricing aws.amazon.com](https://aws.amazon.com/rds/aurora/pricing/) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - AWS Aurora CER-0293 ### [Automatic Restart of Stopped Aurora Clusters Causing Unintended Compute Charges](https://www.pointfive.co/efficiency-hub/inefficiencies/automatic-restart-of-stopped-aurora-clusters-causing-unintended-compute-charges) Amazon Aurora database clusters are intentionally stopped to avoid compute costs but are automatically restarted by the service after the maximum allowed stop period. Once restarted, re-started database instances begin accruing... Databases - AWS Aurora CER-0236 ### [Outdated Aurora Versions Triggering Extended Support Charges](https://www.pointfive.co/efficiency-hub/inefficiencies/outdated-aurora-versions-triggering-extended-support-charges) Customers often delay upgrading Aurora clusters due to compatibility concerns or operational overhead. However, when older versions such as Aurora MySQL 2 (MySQL 5.7) or Aurora PostgreSQL 11, 12 and 13 move into Extended Support, AWS... Databases - AWS Aurora CER-0043 ### [Suboptimal Storage Configuration for Aurora Cluster](https://www.pointfive.co/efficiency-hub/inefficiencies/suboptimal-storage-configuration-for-aurora-cluster) Many Aurora clusters default to using the Standard configuration, which charges separately for I/O operations. For workloads with frequent read and write activity, this can lead to unnecessarily high costs. Aurora I/O-Optimized eliminates... Databases --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.