> ## Documentation Index
> Fetch the complete documentation index at: https://help.nops.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Switch Steady Aurora Serverless to Provisioned

> Move Aurora Serverless v2 instances with a steady load to a provisioned instance sized for their peak.

Aurora Serverless v2 bills per ACU-hour and scales with load, which pays off when load changes a lot. An instance that stays at a similar level all day costs less as a provisioned instance. nOps finds Serverless v2 instances with a steady load and estimates the saving from the cheapest Graviton provisioned class with enough memory for their busiest hour.

| | |
| - | - |
| **Cloud** | AWS |
| **Category** | Database |
| **Service** | Amazon Aurora |
| **Action** | Rightsize |
| **Effort** | Medium |
| **Restart needed** | Yes |
| **Can be rolled back** | Yes |
| **Analysis window** | Last 30 days |
| **Source** | nOps |

## Why it matters

Serverless is a common default for new Aurora clusters, but for steady workloads its per-ACU price is higher than a provisioned instance of the same capacity.

## How nOps finds it

nOps reads the last 30 complete days of hourly Serverless v2 ACU billing. An instance is flagged when it was billed in at least 95% of the 720 hours and its 10th-percentile hour used at least half the ACUs of its 95th-percentile hour. The target is the cheapest db.r6g, db.r7g or db.t4g class with at least 2 GiB of memory per ACU of its busiest hour (db.t4g only when that hour is 4 ACUs or less). The saving is the on-demand cost of the last 7 days, scaled to a month, times one minus the instance's list price for the week divided by the list price of the ACUs it used. Instances mostly covered by commitments or credits, and savings under \$5 a month, are left out.

## Before you start

Permission to add, fail over and remove cluster instances (`rds:CreateDBInstance`, `rds:FailoverDBCluster`, `rds:DeleteDBInstance`).

## How to implement

1. Check the instance's peak ACU in CloudWatch (**ServerlessDatabaseCapacity**) at minute level, not just hourly.
2. Add a provisioned instance of the recommended class to the cluster (`aws rds create-db-instance --db-cluster-identifier CLUSTER --db-instance-identifier NEW_ID --db-instance-class NEW_CLASS --engine ENGINE`).
3. When it is available, fail over to it (`aws rds failover-db-cluster --db-cluster-identifier CLUSTER --target-db-instance-identifier NEW_ID`) if the serverless instance is the writer.
4. Delete the serverless instance once the provisioned one is serving traffic.
5. Update Terraform or CloudFormation to match.

## Risks and considerations

* A provisioned instance does not scale up for sudden spikes. nOps sizes it from hourly averages, so check short peaks first.
* The failover causes a brief interruption for connected clients.
* To roll back, add a Serverless v2 instance again and fail over to it.

## FAQs

> [accordion] Why 2 GiB per ACU?
>
> One Aurora capacity unit is about 2 GiB of memory, so the provisioned instance needs that much memory for each ACU of the busiest hour.

## Related

* [Switch Aurora Cluster to I/O-Optimized](https://help.nops.io/inform/supported-recommendations/switch-aurora-cluster-to-i-o-optimized)
* [Rightsize RDS Instance](https://help.nops.io/inform/supported-recommendations/rightsize-rds-instance)
* [Supported recommendations](https://help.nops.io/inform/supported-recommendations.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.