Move EC2 s3 file gateway to different AZ in same region

Migrating the underlying EC2 file gateway instance from one AZ to another AZ in the same region is not possible. As it would require instance backup and then restore it in the desired AZ. However, Storage Gateway doesn’t support recovering a gateway VM from a snapshot that is created by your hypervisor or from your Amazon EC2 Amazon Machine Image (AMI). If your gateway VM malfunctions, activate a new gateway and recover your data to that gateway using the instructions given in the AWS guide below:

https://docs.aws.amazon.com/filegateway/latest/files3/recover-data-from-gateway.html

Having said that in order to retain the current file share with SMB NTFS permissions assigned to the share, you can follow the Method 1 "Migrate cache disk and Gateway ID to replacement instance" given in the 'Replacing your existing File Gateway with a new instance' AWS guide:

https://docs.aws.amazon.com/filegateway/latest/files3/migrate-data.html#migrate-data-file-gateway

We highly suggest you to set the Windows ACL (NTFS permission) on the first level of sub-folders under root folder (share level). So the permission will be stored in the object metadata, after which whatever way you use to migrate the gateway, the Windows ACL will persist. If you only set the Windows ACL on share level (root folder), then all the sub-folders and files inherit the permissions from root folder. Thus, when the share is being deleted, the Windows ACL will be lost.