-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
S3FullAccess Policy doesn't grant access to tags #1063
Comments
@andreineacsu yes, it is possible to define custom policies on a Policies:
- Statement:
- Action: [ 's3:*' ]
Effect: Allow
Resource: '*' As for updates to S3FullAccess policy, there are several actions that deal with tagging. I think all of these are necessary to support tagging on both objects and object versions, can you confirm this?
(Taken from the S3 permissions documentation) |
@keetonian Thank you for your reply! Everything looks good now. |
To add these extra permissions, we need to update the S3FullAccess Policy Template with the permissions I listed above in my comment, and update any failing tests. |
Closing this issue as v1.15.0 is released |
Hello,
I am currently working on a SAM application that requires full access on an S3 bucket.
I'm setting the S3FullAccess policy on the Lambda function that requires full access but it doesn't work because this policy doesn't have access to file tags. Can this policy be modified so that it includes access to file tags and metadata?
Also, is there any way to define custom SAM policies?
Thanks,
Andrei
The text was updated successfully, but these errors were encountered: