- Newest
- Most votes
- Most comments
Hi, You are correct in that a single S3 location (root of the bucket or prefix within the bucket) can only be mapped to one file share on a single S3 File Gateway. In order to provide different levels of permissions to different user groups, you can tackle this in one of two ways.
-
Assign SMB permissions via security groups. ie. 'Domain Admins' have full control, 'Users' have read-only access. https://docs.aws.amazon.com/filegateway/latest/files3/smb-acl.html SMB permissions (ACL's) persists on the objects themselves ,and you can manage this through windows explorer (as an admin). This would allow for a single S3 File Gateway to host a single File Share, with separate permissions based on who is accessing the share (in your case, IT group vs. general users).
-
Create a separate gateway, and control access via the Gateway File Share settings. This would allow you to create a file share on one gateway where IT group users have admin control, and a separate file share on a second gateway with read-only access for the rest of your users. https://docs.aws.amazon.com/filegateway/latest/files3/CreatingAnSMBFileShare.html
Ed
Relevant content
- Accepted Answerasked 2 years ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
Thanks for your reply I think I will be going for option 1. It's the simplest method and the lower-cost option.
I've tested option 2 and it would work well but I would need a second gateway and EC2 instance cache host. I tried to register the second gateway with the original EC2 host but this failed. Each gateway must need its own host.