- Newest
- Most votes
- Most comments
Hi, after creating the SMB file share for the underlying S3 bucket on your file gateway, you can map the file share on Windows as network drive. Then, you can apply Active Directory Windows ACL permissions on the folders/files from the Windows explorer or through PowerShell. Please check below documentation for using Windows ACLs on the SMB file share.
https://docs.aws.amazon.com/filegateway/latest/files3/CreatingAnSMBFileShare.html https://docs.aws.amazon.com/filegateway/latest/files3/smb-acl.html
I understand that you are concerned about filling the cache disk, please note that file gateway uploads data from its cache disk to S3 asynchronously. You can use CachePercentDirty CloudWatch metric to monitor any dirty data pending upload to S3 from the cache disk. Depending on the size of your working dataset and size of the files being written to gateway, you can size the cache disk to maximum of 64 TB.
You can use AWS CLI method to copy initial data to S3 and then use Robocopy through file share to copy changes. Alternatively, you can also consider looking into AWS DataSync for the initial copy to S3. However, using these two methods you wouldn't be able to retain any existing Windows ACLs on your data. To retain existing ACLs, you would need to use Robocopy and copy only through the gateway using SMB file share.
https://docs.aws.amazon.com/datasync/latest/userguide/how-datasync-works.html#onprem-aws
Relevant content
- Accepted Answerasked 8 months ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 4 months ago