An enterprise is migrating a dataset of unstructured media files from an on-premises NFS file system to an Amazon S3 bucket in a target AWS account (Account B). The enterprise currently has a AWS Direct Connect connection terminated in a shared services AWS account (Account A), with a backup internet link. The migration must be completed within a strict timeline of days. Due to regulatory compliance, all data must be encrypted at rest using an AWS KMS Customer Managed Key (CMK), and the data transfer must not traverse the public internet.
Which combination of actions will meet these requirements most efficiently? (Select TWO.)
- Create AWS Snowball Edge Storage Optimized import jobs in Account B specifying the target Amazon S3 bucket, and request delivery of the devices to the on-premises datacenter.Answer
- Configure a Customer Managed Key (CMK) in Account B and update its key policy to grant the Snowball import IAM role permissions to decrypt and encrypt with the key.Answer
- CDeploy AWS DataSync agents on-premises and configure a task to transfer the data over the AWS Direct Connect connection directly to the Amazon S3 bucket in Account B.
- DCreate AWS Snowball Edge import jobs in Account B using the default AWS-managed KMS key (`aws/s3`) to encrypt the data during transit and at rest.
- EConfigure an AWS DataSync task using a Transit Gateway with a Transit VIF over the Direct Connect link to route traffic through Account A to Account B.
Answer
To migrate the data within the timeline, AWS Snowball Edge devices must be ordered from the target account (Account B). A Customer Managed Key (CMK) must be configured in Account B with its key policy updated to allow the Snowball import role to use the key.
The correct actions are to order AWS Snowball Edge Storage Optimized devices from the target account (Account B) and use a Customer Managed Key (CMK) in Account B with a key policy that trusts the Snowball import role. Since cannot be transferred over the link within days, an offline transfer using Snowball Edge is required. Ordering the devices from the target account allows importing directly to the destination bucket. A Customer Managed Key is necessary because AWS-managed keys cannot be shared cross-account.
Step-by-Step Solution
Key Concept
Selecting the correct large-scale data transfer mechanism based on bandwidth and timeline constraints, and configuring cross-account IAM and KMS permissions.
Estimated Time:2m 0s