Amazon RDS Per-Snapshot Billing Explained: What Changed, What Breaks, and How to Tag Snapshots
Amazon RDS now bills each snapshot separately (Nov 2, 2026): what changes in CUR and Cost Explorer, what breaks in Budgets, and how to tag snapshots.
As of November 2, 2026, Amazon RDS bills each database snapshot as its own line item in AWS Cost Explorer and the Cost and Usage Report (CUR), instead of rolling snapshot storage into the DB instance's charges. Your total bill doesn't change. What changes is how the cost is attributed. That can break existing chargeback rules, Cost Categories and Budgets filters that match on a DB instance ARN.
If you run FinOps, platform or database teams on AWS, below is what changed, what can break, and a checklist for fixing it before this month's reports go out.
What is RDS per-snapshot billing?
AWS's What's New post (November 2, 2026) says Amazon RDS now supports per-snapshot billing, so you can see what each snapshot costs. Until now, snapshot charges were aggregated at the DB instance level in the CUR and Cost Explorer. The key points from the announcement:
- Engines: all Amazon RDS engines.
- Regions: all commercial AWS Regions and AWS GovCloud (US).
- Cost: enabled by default for all RDS snapshots, at no additional charge.
- Tags: you can apply cost allocation tags directly to snapshots to track their costs.
Snapshot pricing isn't changing. The RDS documentation says: "Your snapshot pricing and overall charges remain the same; only how the charges are attributed and presented changes."
What changed: before vs after
This table is our summary of AWS's 2019 detailed-backup-billing announcement and the updated RDS documentation:
| Before (since Oct 2019) | After (Nov 2026) | |
|---|---|---|
| Where snapshot storage appeared | Aggregated per DB instance | One line item per snapshot |
CUR ResourceId |
DB instance | Snapshot ARN (DB snapshot) or cluster snapshot ARN (DB cluster snapshot) |
| Snapshots of deleted instances | Hard to attribute | Attributed to the snapshot ARN; no blank ResourceId lines |
| Cross-Region / cross-account copies | Not detailed in the old announcement | Attributed to the snapshot ARN in the destination account or Region |
| Cost allocation tags | Instance-level view | Tags on the snapshot itself are reflected on the bill |
| Free backup allowance | 100% of provisioned storage per Region | Same, now applied as a percentage discount across every snapshot |
| Total charges | Unchanged | Unchanged |
What will break? (Read this before your next chargeback run)
The RDS docs include an explicit warning. Any rule that attributes snapshot charges by matching a DB instance ARN in the ResourceId field no longer matches those charges. AWS lists three examples:
- AWS Cost Categories rules keyed on DB instance ARNs
- AWS Budgets filters scoped to DB instance ARNs
- Chargeback/showback jobs (Athena, dbt, spreadsheets, third-party FinOps tools) that read
ResourceIdfrom the CUR
In practice, if your team's "cost of database X" report included backup storage, that portion will now show up as separate snapshot lines and may land in an "unallocated" bucket.
How the free backup allowance is now split
RDS gives you free backup storage equal to 100% of your total provisioned database storage per Region. What's new is how that free amount is spread. AWS's documentation explains that the allowance is applied as a percentage discount across all snapshots, not subtracted from a single snapshot.
AWS's own worked example: 100 GB provisioned storage (so 100 GB free), and two snapshots of 50 GB and 75 GB (125 GB total). The free share is 100 ÷ 125 = 80%, so each snapshot is billed for 20% of its size: 10 GB for snapshot A and 15 GB for snapshot B, 25 GB in total. That 25 GB equals the 125 GB of snapshots minus the 100 GB allowance, so the account total is the same as before.
What this means for you: AWS warns that per-instance totals rebuilt from snapshot tags won't match the per-instance totals you saw before, even though the account-level total is unchanged. Expect questions from teams whose numbers moved. The money didn't move, only the attribution.
How do I see the cost of each RDS snapshot?
- Cost Explorer: filter on Amazon RDS and group by resource (where resource-level data is enabled) to see snapshot ARNs as their own resources.
- CUR / CUR 2.0: look for line items whose resource ID is an RDS snapshot ARN (
…:snapshot:…) or cluster snapshot ARN (…:cluster-snapshot:…). - Tag snapshots so they roll up to the right team or database (see the next section).
- Activate the tag keys as cost allocation tags in the Billing console. A tag only appears on the bill after it's activated.
How to tag RDS snapshots for cost allocation
AWS documents two approaches:
- Tag each snapshot directly. You need this for existing snapshots.
- Enable "Copy tags to snapshots" on the DB instance so that new snapshots inherit the instance's tags. It applies only to snapshots created after you enable it.
The commands, using the standard AWS CLI RDS operations (replace the placeholders):
# Turn on tag copying for future snapshots of an instance
aws rds modify-db-instance \
--db-instance-identifier my-db \
--copy-tags-to-snapshot \
--apply-immediately
# Tag an existing snapshot with its source database and owner
aws rds add-tags-to-resource \
--resource-name arn:aws:rds:us-east-1:123456789012:snapshot:my-db-snapshot \
--tags Key=source-db,Value=my-db Key=team,Value=payments
# List the manual snapshots of an instance (to find ARNs to tag)
aws rds describe-db-snapshots \
--db-instance-identifier my-db \
--snapshot-type manual \
--query 'DBSnapshots[].DBSnapshotArn'
Three caveats from the RDS docs:
- Tags aren't retroactive on the bill. Snapshot usage incurred before a tag was assigned stays unattributed, so AWS recommends tagging as soon as possible.
- Cross-account copies don't carry tags. Tag the copy in the destination account.
- Tags keep working after the source DB is deleted, which makes them more reliable than the old instance-ARN approach for orphaned snapshots.
Your migration checklist
| # | Task | Owner | Done? |
|---|---|---|---|
| 1 | Search Cost Categories for rules that match RDS DB instance ARNs | FinOps | ☐ |
| 2 | Search Budgets filters scoped to RDS instance ARNs | FinOps | ☐ |
| 3 | Search CUR/Athena/dbt chargeback SQL for ResourceId joins on RDS instances |
Data/FinOps | ☐ |
| 4 | Turn on Copy tags to snapshots for every production DB instance and cluster | Platform/DBA | ☐ |
| 5 | Back-tag existing manual and final snapshots (e.g. source-db, team, env) |
Platform/DBA | ☐ |
| 6 | Activate those tag keys as cost allocation tags | Billing admin | ☐ |
| 7 | Find old snapshots of deleted instances, now visible as their own line items, and decide whether to keep them | DBA | ☐ |
| 8 | Tell teams their per-DB numbers may shift even though the total hasn't | FinOps | ☐ |
Editor's take
Editor's take: This is a good change that looks like a non-event in the changelog. Per-snapshot lines finally answer "what is this old snapshot of a database we deleted two years ago costing us?", because AWS now says there are no blank-ResourceId lines. The risk is quiet breakage. AWS has turned the change on by default, and any allocation logic built on instance ARNs will start leaking snapshot costs into "unallocated" without throwing an error. If your company does showback, check items 1–3 on the checklist before month-end. We haven't run this in our own AWS accounts. This is based on AWS's announcement and documentation.
What are AWS users saying?
The change went live on November 2, and we found no community discussion we could verify and link to (re:Post, Reddit or Hacker News) by November 3. The questions engineers search for most are "RDS snapshot billing" and "RDS snapshot pricing", and in practice they usually want to know:
- Will my RDS bill go up? (No, per AWS.)
- Why did my per-database backup cost change? (Because of the percentage-based allowance split.)
- How do I find which snapshot is expensive? (Per-snapshot lines plus tags.)
For other recent AWS changes worth a look, see our explainers on Amazon RDS for SQL Server read replica snapshots, RDS Custom for SQL Server updates, and the full AWS re:Invent 2026 guide, where more cost-management news usually lands.
More from 9to5Amazon today: Alexa+ launches in Japan · Is Amazon Grocery worth it?
FAQ
What is RDS per-snapshot billing?
A change, announced on November 2, 2026, that makes Amazon RDS show each DB snapshot or DB cluster snapshot as its own line item in Cost Explorer and the Cost and Usage Report, instead of aggregating snapshot storage under the DB instance.
Does RDS per-snapshot billing cost extra?
No. AWS says it is on by default at no additional charge, and snapshot pricing and overall charges stay the same.
How much does an RDS snapshot cost?
Backup storage is free up to 100% of your provisioned database storage per Region. Storage above that is billed at the backup storage rate on the Amazon RDS pricing page for your engine and Region. Cross-Region snapshot copies also incur data transfer charges.
Why don't my per-database RDS backup costs match last month?
The free allowance is now spread as a percentage discount across all snapshots. AWS says tag-based per-instance totals won't match the old per-instance totals, even though the account total is unchanged.
Can I add cost allocation tags to RDS snapshots?
Yes. Tag snapshots directly, or enable "copy tags to snapshots" on the DB instance for new snapshots. Then activate the tag keys as cost allocation tags in the Billing console. Tags aren't applied retroactively.
Will my AWS Budgets and Cost Categories still work?
Not if they match RDS snapshot charges by DB instance ARN. AWS says those rules no longer match. Update them to snapshot ARNs or use cost allocation tags.
Which regions and engines support per-snapshot billing?
All Amazon RDS engines, in all commercial AWS Regions and the AWS GovCloud (US) Regions, according to the announcement.
What happens to snapshots of deleted RDS instances?
Their charges are now attributed to the snapshot ARN itself, so they no longer appear without a resource ID. That makes it easier to find old snapshots to clean up.
Sources
- AWS What's New, "Amazon RDS now supports per snapshot billing" (Nov 2, 2026): https://aws.amazon.com/about-aws/whats-new/2026/11/amazon-rds-per-snapshot-billing/
- Amazon RDS User Guide, Introduction to backups (backup storage, free allowance, CUR attribution): https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_WorkingWithAutomatedBackups.html
- Amazon RDS User Guide, Tagging Amazon RDS resources: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_Tagging.html
- AWS What's New, "Amazon RDS Enables Detailed Backup Storage Billing" (Oct 10, 2019): https://aws.amazon.com/about-aws/whats-new/2019/10/amazon-rds-enables-detailed-backup-storage-billing/
- Amazon RDS pricing: https://aws.amazon.com/rds/pricing/
Featured image: A technician inside an Amazon data center (a general AWS data center photo, not specific to Amazon RDS), official Amazon photo. Source