EBS Volumes Can Now Be Copied Straight Across AWS Accounts!
Hi, it's me, Shiichan! I found a nice Amazon EBS update today.
AWS What's New
aws.amazon.com
What was announced?
AWS What's New announced that Amazon EBS Volume Clones now supports copying EBS volumes across AWS accounts, re-encrypting with an AWS KMS key in the target account.
The story so far
Plenty of organizations split production and development workloads across separate AWS accounts. But until now, copying data across that account boundary wasn't straightforward — especially for teams that keep separate KMS keys for production and non-production environments, since there weren't many ways to move data while preserving that key separation.
What changes
With cross-account copy, you can clone a production database volume into an isolated development account, giving developers a safe way to experiment with production-like data.
- Supported volume types: all volume types, including unencrypted volumes and volumes encrypted with customer managed keys
- How it works: first share the volume with the target account using AWS Resource Access Manager (RAM), then the target account creates a copy in the same Availability Zone
- Access methods: AWS Management Console, AWS CLI, and AWS SDKs
- Region coverage: everywhere Amazon EBS Volume Clones is supported, including all Commercial Regions, AWS GovCloud (US), AWS China Regions, and supported Local Zones
Wrap-up
- Amazon EBS Volume Clones now supports cross-account volume copying with re-encryption.
- Organizations that separate accounts and KMS keys between production and development can move data via AWS RAM sharing followed by a copy in the target account.
- Works for every volume type, from the Console, CLI, or SDKs.
- A great fit for teams running multi-account setups who want production-like data in their development environments!
