Why it matters
Tables that keep history, logs or rarely read records grow every month while their traffic stays flat. The switch is online, with no downtime.How nOps finds it
nOps reads the last 30 days of DynamoDB billing for each table. A table is flagged when its storage was billed on at least 28 of those days, it is not already Standard-IA, none of its capacity is on reserved pricing, and storage is more than half of its storage plus read and write cost. The saving is 60% of the storage cost minus 25% of the read and write cost, and must be at least $5 a month.Before you start
Permission to update the table (dynamodb:UpdateTable).
How to implement
- Check the table’s current class and status (
aws dynamodb describe-table --table-name TABLE). - Change the table class (DynamoDB console: Tables → your table → Actions → Update table class → Standard-IA, or
aws dynamodb update-table --table-name TABLE --table-class STANDARD_INFREQUENT_ACCESS). - Wait for the table to become Active again. Reads and writes keep working throughout.
- Update the table class in Terraform or CloudFormation so a later deployment does not change it back.
Risks and considerations
- Reads and writes cost about 25% more on Standard-IA. If traffic grows a lot, Standard may become cheaper again.
- You can change a table’s class twice in 30 days, so plan before switching back.
- Standard-IA tables are not covered by DynamoDB reserved capacity.
- To roll back, change the table class back to Standard.
FAQs
Is there any downtime?
Is there any downtime?
No. The change is made online and the table stays available.