- Newest
- Most votes
- Most comments
keep the File system in on-prem itself and create a Storage File Gateway to allow NFS access for the migrated cloud servers
I don't think that will work for the use case you have in mind.
Ultimately, your end state is almost certain to be Linux VMs -> EC2, and storage migrated NFS -> EFS, and I can't see how you can achieve that end state while using Storage Gateway as a kind of "intermediate state".
Storage Gateway allows on-prem VMs to consume storage in AWS, but not in the other direction. At back end it's either S3, EBS, or FSx - look at the main How it works diagram at https://aws.amazon.com/storagegateway/
Depending on the latency (and a factor could be how far you are from an AWS region) and if you have a resilient DX connection, you could use DataSync to migrate on-prem NFS to EFS in the cloud, and then the on-prem VMs and the EC2 instances could all consume the EFS filesystems. Then progressively migrate the VMs to EC2 until they have all come across.
Be aware that you can't do continual updates using DataSync, the shortest interval for running DataSync jobs is one hour https://docs.aws.amazon.com/datasync/latest/userguide/task-scheduling.html
Relevant content
- asked 2 years ago
- asked a year ago
- asked 5 months ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago