Question

Difficulty: MediumLarge-Scale Data Transfer using Snow Family, DataSync, and Transfer Family

An enterprise wants to migrate an 80 TB80\text{ TB} on-premises SMB file share to Amazon FSx for Windows File Server. The enterprise has a 1 Gbps1\text{ Gbps} Direct Connect connection to AWS via a Transit Gateway, but only 200 Mbps200\text{ Mbps} of network bandwidth can be allocated for the migration due to daytime production traffic. The migration must be completed within 45 days45\text{ days} while fully preserving all NTFS Access Control Lists (ACLs) and metadata. The target FSx file system must be encrypted using a KMS key that supports cross-account access from the migration team's AWS account. Which of the following solutions meets these requirements with the least operational overhead?

  1. Deploy an AWS DataSync agent on-premises, configure it to access the SMB file share, and create a task targeting the Amazon FSx for Windows File Server file system. Configure the FSx file system to be encrypted using a Customer Managed Key (CMK) in AWS KMS, and update the KMS key policy to grant the migration role permissions to use the key.Answer
  2. B
    Order an AWS Snowball Edge Storage Optimized device, use its SMB interface to copy the 80 TB80\text{ TB} of data locally, and ship the device to AWS to import the data into an Amazon S3 bucket. Then, use AWS DataSync to copy the files from the S3 bucket to Amazon FSx for Windows File Server.
  3. C
    Deploy an AWS DataSync agent on-premises, and configure a DataSync task to copy the data to a temporary VPC. Route the migration traffic directly through the Direct Connect Gateway to the destination VPC, bypassing the Transit Gateway to optimize network routing.
  4. D
    Deploy an AWS DataSync agent on-premises, configure it to access the SMB file share, and create a task targeting the Amazon FSx for Windows File Server file system. Encrypt the FSx file system using the default AWS managed key (aws/fsx), and modify its key policy to allow cross-account access from the migration team's AWS account.

Answer

Deploy an AWS DataSync agent on-premises to copy data directly from the SMB file share to the destination Amazon FSx for Windows File Server. Use a Customer Managed Key (CMK) in AWS KMS to encrypt the target FSx file system and update its policy to allow cross-account access.
Deploying AWS DataSync agent on-premises and copying directly to FSx for Windows File Server is the optimal solution. The transfer completes in 37 days37\text{ days}, which satisfies the 45 days45\text{ days} timeline. DataSync preserves NTFS ACLs and metadata directly when transferring from an SMB source to an FSx destination. Using a Customer Managed Key (CMK) allows cross-account key policy configurations, which satisfies the security requirements.

Step-by-Step Solution

1
Calculate the transfer timeline over the allocated network bandwidth.
At 200 Mbps200\text{ Mbps}, transferring 80 TB80\text{ TB} of data takes approximately 37 days37\text{ days} (80×1012×8/200,000,000=3,200,000 seconds80 \times 10^{12} \times 8 / 200,000,000 = 3,200,000\text{ seconds}), which is within the 45 days45\text{ days} requirement.
To verify if online migration via DataSync is feasible or if an offline method is required.
2
Select the correct migration tool that preserves target metadata.
AWS DataSync preserves NTFS ACLs and permissions when transferring directly from SMB to FSx for Windows File Server. Staging through Amazon S3 via Snowball Edge would strip these ACLs.
To guarantee that NTFS permissions and metadata are fully preserved during transit.
3
Configure the security controls for cross-account access.
Create a Customer Managed Key (CMK) and assign it to the FSx file system, then modify the key policy to permit cross-account usage.
To satisfy the security requirement of cross-account KMS encryption, which is unsupported by AWS managed keys.

Key Concept

Online migration of SMB shares to Amazon FSx for Windows File Server using AWS DataSync while preserving NTFS ACLs, and configuring cross-account KMS permissions using Customer Managed Keys.
Rate this question