# Suboptimal storage configuration for Aurora cluster Canonical: 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. By: Taylor Houck Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Suboptimal Storage Configuration for Aurora Cluster The short version Many Aurora clusters default to using the Standard configuration, which charges separately for I/O operations. [Taylor Houck](https://www.linkedin.com/in/twhouck/) Cloud FinOps Specialist @ PointFive 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-0043 Type Inefficient Configuration ## Explanation Why the waste happens and who it affects. For workloads with frequent read and write activity, this can lead to unnecessarily high costs. Aurora I/O-Optimized eliminates I/O charges entirely and simplifies cost predictability. In environments with consistently high I/O usage, switching to I/O-Optimized often results in lower total spend. ## Billing model The pricing dimensions that drive this cost. Aurora offers two storage configurations with distinct cost structures: - Aurora Standard: Lower per-GB storage cost, but incurs additional charges for I/O operations (reads and writes) - Aurora I/O-Optimized: Higher per-GB storage cost and higher database instance and Aurora Serverless ACU prices, but no charges for read and write I/O operations Choosing the right configuration depends on the balance between storage volume and I/O intensity. High-I/O workloads may see significantly lower costs under I/O-Optimized pricing; AWS positions it for clusters where I/O spend exceeds 25% of total Aurora database spend. ## How to detect 7 checks to find it in your estate. - Identify Aurora clusters currently using the Standard storage configuration - Review historical cost breakdowns to evaluate the portion of spend attributed to I/O charges - Determine whether the workload exhibits high read/write activity or transactional behavior - Assess whether I/O charges regularly account for a significant share of total Aurora costs - Estimate whether switching to I/O-Optimized would lower total cost based on current storage and I/O usage patterns - Confirm that the cluster meets version and engine requirements for I/O-Optimized eligibility - Engage database administrators or workload owners to validate I/O behavior and review trade-offs ## How to fix How to remove the waste. Modify the cluster to use Aurora I/O-Optimized if the workload is read/write intensive and I/O costs are high. For supported Aurora versions, the change causes no downtime on non-NVMe-based instances (including Aurora Serverless), while NVMe-based instance classes require a database engine restart that may cause brief downtime. You can switch from Standard to I/O-Optimized only once every 30 days. Monitor ongoing cost and performance to confirm the change results in expected benefits. ## Documentation Vendor references for pricing and configuration. - [Amazon Aurora pricing aws.amazon.com](https://aws.amazon.com/rds/aurora/pricing/) - [Amazon Aurora storage docs.aws.amazon.com](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/Aurora.Overview.StorageReliability.html) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - AWS Aurora CER-0378 ### [Aurora Serverless v2 Minimum Capacity Preventing Auto-Pause](https://www.pointfive.co/efficiency-hub/inefficiencies/aurora-serverless-v2-minimum-capacity-preventing-auto-pause) Aurora Serverless v2 instances can scale down to zero ACUs and automatically pause when they have had no user-initiated connections for a configurable interval, and there is no instance charge while an instance is paused. The feature is... Databases - 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-0247 ### [Misuse of Aurora Serverless for Steady-State Workloads](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. However, when used for databases with constant load, the service's elasticity offers little advantage and... Databases --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.