> ## 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.

# Buy DynamoDB Reserved Capacity

> Buy 1-year DynamoDB reserved capacity for the read and write capacity your provisioned tables always use.

DynamoDB reserved capacity is a 1-year commitment to a number of read or write capacity units in a region, at a lower effective rate than provisioned on-demand capacity. nOps finds accounts whose provisioned capacity never drops below a steady level and estimates the saving from reserving only that level, so you do not pay for reserved units you leave idle.

| | |
| - | - |
| **Cloud** | AWS |
| **Category** | Database |
| **Service** | Amazon DynamoDB |
| **Action** | Purchase |
| **Effort** | Low |
| **Restart needed** | No |
| **Can be rolled back** | No |
| **Analysis window** | Last 30 days |
| **Source** | nOps |

## Why it matters

Provisioned tables with steady traffic pay full price for capacity they use every hour. Reserving the floor of that usage cuts its cost by about half.

## How nOps finds it

nOps reads the last 30 complete days of on-demand provisioned capacity billing, per account, region and capacity type (read or write). It needs capacity billed in at least 95% of the 720 hours. It reserves the level your usage stayed at or above in 95% of hours, rounded down to blocks of 100 units (at least 100). The saving is the unit-hours that reservation would have covered, minus the reserved units times 720 hours times the 1-year reserved price as a share of on-demand (about 46%, from AWS's published 1-year pricing), at your billed rate. Accounts not using capacity in the last 2 days, accounts mostly paid with credits and savings under \$5 a month are left out.

## Before you start

Permission to buy reserved capacity (`dynamodb:PurchaseReservedCapacityOfferings`) in the payer or the account that owns the tables.

## How to implement

1. Check that the tables using this capacity will keep running in provisioned mode for the next year.
2. In the DynamoDB console, open **Reserved capacity → Purchase reserved capacity**.
3. Choose the region, read or write capacity, a 1-year term and the number of units nOps shows.
4. Review the upfront payment and confirm the purchase.
5. Check the next days' billing: the reserved units should replace part of the on-demand capacity charge.

## Risks and considerations

* Reserved capacity cannot be cancelled. You pay for it for the full year whether or not you use it.
* It applies only to provisioned Standard-class tables in that region; Standard-IA tables and global-table replicated writes are not covered.
* If your billed rate is below list price (for example from a private discount), the real saving can be lower.

## FAQs

> [accordion] Why doesn't nOps reserve my average usage?
>
> Reserving the level you stay above almost all the time means very few reserved units sit idle. Usage above it stays on demand.

## Related

* [Switch Steady DynamoDB Tables to Provisioned Capacity](https://help.nops.io/inform/supported-recommendations/switch-steady-dynamodb-tables-to-provisioned-capacity)
* [Switch DynamoDB Table to Standard-IA](https://help.nops.io/inform/supported-recommendations/switch-dynamodb-table-to-standard-ia)
* [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.