AWS Backup EBS archive: copy order and the 90-day retention rule

Use the new support for infrequent, long-term EBS retention

On November 12, 2026, AWS Backup announced that EBS backups in a logically air-gapped vault can transition to EBS Snapshots Archive. This adds an archive option for rarely accessed backups; it does not turn every routine recovery point into inexpensive storage with immediate retrieval.

Regional eligibility is the intersection of the two features: the destination Region must support both logically air-gapped vaults and EBS Snapshots Archive. Check the current AWS Backup feature table and EBS availability before implementation. Availability in all applicable Regions does not mean every AWS Region or account needs no preparation.

Choose the primary or copy destination before setting its lifecycle

The announcement and vault guide require a backup rule that runs monthly or less often. To store a copy in a logically air-gapped vault, add a copy action targeting that vault and select Archive Amazon EBS snapshots in the copy lifecycle.

If the vault is already prepared as a primary backup target under the current guide, enable the option in the backup rule lifecycle instead. These settings apply to different destinations. Changing the primary rule alone does not establish the copy’s lifecycle.

Set warm-storage duration and total retention next. For a vault encrypted with a customer-managed KMS key, AWS requires a key-policy update before enabling the archive option. Follow the current dedicated guidance; being able to view a vault does not establish all required permissions.

Total retention must include at least 90 days after warm storage

The vault-specific guide requires total retention to be at least 90 days longer than warm-storage time, within the vault’s own minimum and maximum retention settings. The 90-day requirement concerns the archive stage. Retaining a backup for 90 days from creation does not necessarily satisfy it.

For a hypothetical 30-day warm period, total retention must therefore be at least 120 days and still fit the vault’s allowed range. This is a configuration example, not an applied backup-plan change. A shorter vault minimum does not permit a shorter minimum archive period.

Complete required vault or Region copies before archiving

The AWS Backup logically air-gapped vault guide explicitly says that once an EBS backup transitions to the archive tier, it cannot be copied to another vault or AWS Region. This includes copies from a restore access backup vault through Multi-party approval, or MPA.

List the accounts and Regions where you need copies, complete and verify those copies while the backup is warm, then schedule archival. Follow this vault-specific restriction. The generic EBS instruction to restore an archived snapshot before copying does not establish an exception for this path.

Budget for full snapshots, retrieval time and applicable charges

EBS archival converts an incremental snapshot into a full snapshot containing every block written to the volume when that snapshot was created. The archived snapshot can be larger than its incremental source. EBS documentation also warns that archiving daily incremental snapshots of one volume can cost more than keeping them in the standard tier.

Retrieval from the archive tier to the standard tier can take up to 72 hours, depending on snapshot size. This describes snapshot retrieval, not an end-to-end application recovery promise. Application checks, dependent services and subsequent recovery steps still need their own plan.

AWS Backup pricing requires at least 90 days in cold storage and charges for the remaining days if a backup is deleted early. Include warm storage, archived data size, restores and applicable data transfer in the estimate. This article does not establish a numeric quote for a particular Region or promise a fixed saving.

Keep the archive configuration separate from recovery evidence

Record rule frequency, primary or copy destination, warm days, total retention, vault retention bounds, key type and completed required copies. Compare the resulting retrieval delay and cost with the team’s recovery objectives.

In an authorized isolated test, check archive status, recovered data and application usability separately. Selecting an option or completing a backup job is not a recovery validation. This article reviewed public announcements and documentation only; it did not access an AWS account, create or move snapshots, or perform a recovery drill.