1 Answer
- Newest
- Most votes
- Most comments
0
Hello Tim,
Based on the behavior you are observing, the IAM role assigned to file share might be missing S3:PutObject permissions. I would recommend verifying the IAM role policy permissions and ensure it has these permissions. If you are using SSE-KMS encryption on the file share, please ensure that the file share IAM role has kms:Encrypt, kms:Decrypt, kms:ReEncrypt, kms:GenerateDataKey, and kms:DescribeKey
permissions.
If not already enabled, I would suggest enabling CloudWatch health logs to get notified about errors related to S3.
Thanks - Surya
answered a year ago
Relevant content
- asked 10 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 4 months ago
Apparently I had a role, and must have since when I originally created the bucket, gateway, fileshare, and built the VM, I could see directories created in the cloud on the SMB share locally and vice versa; IAM > Roles > StorageGatewayBucketAccessRole16715426617200.4422551916127462. But when I select that role I get the following:
Why did the role seemingly disappear?
You would be able to check the CloudTrail logs for event name DeleteRole and DeleteRolePolicy to get additional insight into the role deletion. I have seen some cases where customers enforce automatic role deletions if they don't have certain tags etc, but it could be for a different reason in your case. I would suggest checking the CloudTrail log for the User name and further check with your IAM team.