Backup tiering
Overview
Amazon Backup offers a lower-cost warm storage tier for Amazon S3 backups that reduces long-term storage costs by up to 30% while maintaining enterprise-grade protection and recovery capabilities. The low-cost tier provides the same performance and features as the warm storage tier. You can configure tiering to move S3 backup data to cost-optimized storage based on the age of objects within your backup vaults.
Amazon Backup tiering provides the ability to optimize storage costs for S3 backup data that is retained for extended periods due to regulatory compliance, disaster readiness, and ransomware protection strategies. You can configure tiering for all S3 backups for all vaults in an account, or create targeted configurations for specific vaults and protected resources.
First, create a tiering configuration that specifies which S3 resources should be tiered and after how many days (minimum 60 days). Tiering configurations can be automated to apply to all backups or targeted to specific resources. When backup data reaches the specified age threshold, it transitions to the lower-cost storage tier while maintaining identical restore capabilities.
This document outlines the steps to create tiering configurations, manage tiered backup data, monitor cost savings, and troubleshoot any issues with the tiering function in Amazon Backup.
Important
Cost considerations for backup tiering:
Backup tiering has three cost components: warm storage tier, low-cost warm storage tier, and transition costs. When backup data transitions to the lower-cost tier, you'll incur a one-time per-object transition fee based on the number of objects eligible for tiering.
For large datasets with many objects, transition costs may be significant initially but are typically offset by ongoing storage savings for data retained beyond the minimum 60-day threshold.
Tiering Configurations
S3 backup tiering involves creating a tiering configuration that specifies which resources should be tiered and the number of days before transitioning (minimum 60 days) to the lower-cost tier. To enable cost optimization, backup data must be covered by a tiering configuration.
Tiering configuration creation can be set up to apply broadly across backups of all S3 resources in your account, or targeted to specific vaults and resources. You can create multiple configurations to handle different data retention and cost optimization requirements.
Tiering configurations apply to both existing backup data in vaults and new backups created after the configuration is established.
S3 backup tiering configurations specify:
Resource scope: All resources across all vaults, all resources in a specific vault, or selected individual resources. A tiering configuration that applies to all vaults and all resources is considered the default configuration.
Transition timing: Minimum 60 days before data moves to the lower-cost tier
Vault assignment: Which backup vaults the configuration applies to (for all vaults or specific vault name)
Resource selection: Up to 5 different resource selection rules per configuration
Configuration constraints:
One configuration per vault: Each vault can only have one tiering configuration apart from the default configuration
Maximum 5 resource selections: Vault specific configuration supports up to 5 different resource group and corresponding tiering settings
Maximum 100 resources: Up to 100 specific resources across all resource groups can be selected per configuration
Vault priority: If both "all vaults" and specific vault configurations exist, the specific vault configuration takes priority
Creating tiering configurations
Creating tiering configurations
Managing tiering configurations
Viewing tiering configurations
You can view existing tiering configurations through the Amazon Backup console, Amazon CLI, or REST API.
Modifying tiering configurations
You can update existing tiering configurations to change transition timing, resource selection, or vault assignments.
Deleting tiering configurations
You can delete tiering configurations when they are no longer needed.
Note: Deleting a tiering configuration keeps existing data in the lower-cost tier but prevents new data from tiering down.
How S3 backup tiering configurations apply
Amazon Backup evaluates objects within backups for tiering eligibility based on their age. The service checks object age on a daily basis and transitions eligible objects to the lower-cost tier according to your configuration settings. Tiering evaluation occurs automatically in the background. When objects within a backup reach the specified age threshold (minimum 60 days), they become eligible for transition during the next evaluation cycle.
Both objects in existing backups and newly created backup objects are subject to tiering configurations. If you have multiple configurations that could apply to the same backup objects, vault-specific settings take precedence over the configurations that applies to all vaults. The tiering process is irreversible - once objects move to the lower-cost tier, they remain there until the backup is deleted according to your retention policies.
Cost structure and monitoring
Pricing model
S3 backup tiering uses a cost-optimized pricing structure:
Storage cost: Lower /GB-month cost compared to standard warm tier
Transition fee: One-time per-object fee when moving to lower-cost tier
Restore cost: /GB charge when restoring data same as the warm tier restore
No retrieval fees: There are no additional retrieval charges
Cost monitoring
Monitor your tiering cost savings through:
Amazon Cost Explorer: Separate usage types for each storage tier
Amazon Cost and Usage Reports: Detailed breakdown with cost allocation tags
Amazon Backup console: Configuration information
Example cost savings
For a 500TB S3 bucket with 1 billion objects where 60% are eligible for tiering:
Before tiering: $25,600/month
After tiering: $21,000/month
Monthly savings: $4,600/month (18% reduction)
One-time transition fee: $6,000
Configuration Examples
Example 1: Account-wide tiering
Apply tiering to all S3 resources across all backup vaults:
{ "TieringConfigurationName":"MyTieringConfig", "BackupVaultName":"*", "ResourceSelection":[ { "Resources":["*"], "TieringDownSettingsInDays":60, "ResourceType":"S3" } ] }
Example 2:
Tier all resources in a MyBackupVault4 vault:
{ "TieringConfigurationName":"MyTieringConfig", "BackupVaultName":"MyBackupVault4", "ResourceSelection":[ { "Resources":["*"], "TieringDownSettingsInDays":60, "ResourceType":"S3" } ] }
Example 3:
Tier specific buckets with different rules:
{ "TieringConfigurationName":"MyTieringConfig", "BackupVaultName":"MyBackupVault", "ResourceSelection":[ { "Resources": ["arn:aws:s3:::mybucket1", "arn:aws:s3:::mybucket2"], "TieringDownSettingsInDays": 60, "ResourceType": "S3" }, { "Resources": ["arn:aws:s3:::mybucket3"], "TieringDownSettingsInDays": 120, "ResourceType": "S3" } ] }
Example 4:
Set the rule to not tier a bucket (set tiering to 36500):
{ "TieringConfigurationName":"MyTieringConfig", "BackupVaultName":"*", "ResourceSelection":[ { "Resources":["arn:aws:s3:::mybucket7", "arn:aws:s3:::mybucket8"], "TieringDownSettingsInDays":36500, "ResourceType":"S3" } ] }
Supported features and limitations
Supported features
Backup types: Both continuous and periodic backups
Vault types: Standard backup vaults and logically air-gapped vaults
Vault lock: Full compatibility with locked backup vaults
Cross-region/account: Copying tiered data (copies land in standard tier at destination)
Restore capabilities: Point-in-time recovery and item-level restores
Search and indexing: Full compatibility with backup search functionality
Compliance: Maintains all compliance and audit capabilities
Limitations
Minimum transition time: 60 days before data can be moved to lower-cost tier
Resource limit: Up to 100 specific resources per configuration
Configuration limit: Up to 5 different resource selection rules per configuration
One configuration per vault: Each vault can only have one vault specific tiering configuration, apart from the default
One-way transition: Data moved to lower-cost tier remains there until deletion
Troubleshooting
Common issues
Configuration not applying to existing backups
Verify that the configuration is properly assigned to the correct vaults
Check that resources are correctly selected in targeted configurations
Ensure backup data meets the minimum age requirement (60 days)
AlreadyExistsException when creating configuration
Ensure the tiering configuration name is unique within your account
Check if the target vault already has an active tiering configuration
LimitExceededException errors
Verify you have not exceeded the maximum of 5 resource selection group per configuration
Check that you have not selected more than 100 specific resources
Higher than expected transition costs
Review the number of objects being transitioned
Consider the transition fee impact for frequently changing data
Evaluate whether the minimum threshold settings is appropriate for your use case