Which solution will meet these requirements?

By:
In: SAP-C01
Tagged:
With: 1 Comment
A company is planning to migrate an application from on premises to the AWS Cloud.The company will begin the migration by moving the application’s underlying data storage to AWS.The application data is stored on a shared file system on premises, and the application servers connect to the shared file system throughSMB.A solutions architect must implement a solution that uses an Amazon S3 bucket for shared storage.Until the application is fully migrated and code is rewritten to use native Amazon S3 APIs, the application must continue to have access to the data through SMB.The solutions architect must migrate the application data toAWS to its new location while still allowing the on-premises application to access the data.

Which solution will meet these requirements?

Create a new Amazon FSx for Windows File Server file system. Configure AWS DataSync with one location for the on-premises file share and one location for the new Amazon FSx file system. Create a new DataSync task to copy the data from the on-premises file share location to the Amazon FSx file system.

Create an S3 bucket for the application. Copy the data from the on-premises storage to the S3 bucket.

Deploy an AWS Server Migration Service (AWS SMS) VM to the on-premises environment. Use AWS SMS to migrate the file storage server from on premises to an Amazon EC2 instance.

Create an S3 bucket for the application. Deploy a new AWS Storage Gateway file gateway on an on-premises VM. Create a new file share that stores data in the S3 bucket and is associated with the file gateway. Copy the data from the on-premises storage to the new file gateway endpoint.

Explanations:

Amazon FSx for Windows File Server uses SMB, but DataSync is not designed to provide SMB access during the migration process. It is better suited for bulk data transfers and not for maintaining ongoing SMB access during migration.

S3 does not natively support SMB, and simply copying data to an S3 bucket would not provide the necessary SMB access for the application during the migration process. The application would need to be rewritten to use S3 APIs.

AWS Server Migration Service (SMS) is used for migrating virtual machines (VMs), not for migrating file storage services like SMB file shares. This does not meet the requirement for continued SMB access to the data during migration.

AWS Storage Gateway with a file gateway provides an SMB interface and stores data in an S3 bucket. This solution allows continued SMB access to the data while it is migrated to S3, fulfilling the requirement of maintaining SMB access during the migration process.

2025-10-18

1 Comment

  1. Mary
    Author

    My best guess is:
    Create an S3 bucket for the application. Deploy a new AWS Storage Gateway file gateway on an on-premises VM. Create a new file share that stores data in the S3 bucket and is associated with the file gateway. Copy the data from the on-premises storage to the new file gateway endpoint.

Leave a Reply

Your email address will not be published. Required fields are marked *

five × 5 =