AWS Backup creates daily EBS volume backups. Keep recovery points in another Region of the same account in preparation for source-Region failure.
Supported Regions/resources, the destination vault, and IAM/KMS permissions have been verified. Backups remain in warm storage, and copying must happen automatically before a disaster.
Which configuration is most appropriate?
Use a copy action to place recovery points in another Region and verify successful copies, freshness, and restoration.
Detailed explanation
The backup destination alone does not define a cross-Region copy action.
The backup destination alone does not define a cross-Region copy action.
Longer history does not place a recovery point in another Region.
Longer history does not place a recovery point in another Region.
Loss of source access can prevent starting the copy, so this does not meet pre-positioning requirements.
Loss of source access can prevent starting the copy, so this does not meet pre-positioning requirements.
The action defines where copies are stored and retained; successful completion and availability must still be verified.
The action defines where copies are stored and retained; successful completion and availability must still be verified.
Check official documentation
Compare the following points with the official documentation.
Review destination Regions/vaults/retention, resource-specific copy and encryption constraints, and EBS restoration.
Official references
What to confirm
Distinguish configured copying from available recovery points and explain why daily backups alone do not guarantee RPO/RTO.
Key points
- Cross-Region copy
- RPO
- RTO
Notes
- Environment: AWS SOA-C03 exam guide and the linked AWS documentation
- Reviewed against the linked AWS documentation on 2026-10-04.
Foundation review
Check the destination and completion
Set the destination Region's vault ARN and retention in a copy action. Verify Region/resource support, key type, and permissions first. Cross-Region copies from cold storage are unsupported. A started job is not a successful copy; inspect completion and the destination recovery point.
Separate data placement from service recovery
Copy delay or failure can increase the age of the latest usable backup beyond a daily interval. Evaluate tolerable loss from the timestamp of the latest successfully copied backup. Prepare the destination AZ, encryption, attachment, and application steps, and measure recovery through data validation. A copy alone does not create running infrastructure or DNS failover.