An enterprise wants to migrate an on-premises SMB file share to Amazon FSx for Windows File Server. The enterprise has a Direct Connect connection to AWS via a Transit Gateway, but only of network bandwidth can be allocated for the migration due to daytime production traffic. The migration must be completed within 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?
- 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
- BOrder an AWS Snowball Edge Storage Optimized device, use its SMB interface to copy the 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.
- CDeploy 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.
- DDeploy 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 , which satisfies the 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
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.