-
Notifications
You must be signed in to change notification settings - Fork 158
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
required s3 permissions should be documented #21
Comments
Thank you, this should definitely be added to the documentation. |
Is this the error you got?
Also, are you sure I get an error with this specific action (which I'd prefer to use because it does not use Docker and is faster), while another action is able to upload to s3 fine 😅 |
I'm using "s3:*" and it does not work either. I believe this action fails because it tries to force That may be worth it to make this optional |
Looking at https://iam.cloudonaut.io/reference/s3.html, re:
That sounds reasonable, but I can't test it via a bucket that explicitly disallows public-read atm. |
So I can confirm, and my minimal bucket ACL looks like this to make this action work: {
"Version": "2012-10-17",
"Id": "<ANY>",
"Statement": [
{
"Sid": "<ANY>",
"Effect": "Allow",
"Principal": {
"AWS": "<MY_ARN>"
},
"Action": [
"s3:PutObject",
"s3:PutObjectAcl"
],
"Resource": "arn:aws:s3:::<MY_BUCKET>/*"
},
{
"Effect": "Allow",
"Principal": "*",
"Action": "s3:GetObject",
"Resource": "arn:aws:s3:::<MY_BUCKET>/*"
}
]
} |
At least s3:PutObjectAcl is required (because I got access denied before that)
Sample policy which works:
The text was updated successfully, but these errors were encountered: