Skip to content
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

Document which S3 permissions are required by the plugin #10

Open
ksclarke opened this issue Jun 26, 2013 · 3 comments
Open

Document which S3 permissions are required by the plugin #10

ksclarke opened this issue Jun 26, 2013 · 3 comments

Comments

@ksclarke
Copy link

I have an IAM user created for Maven to upload the site files into an S3 bucket. When I use a policy for a IAM user like:

{
"Statement": [
{
"Sid": "Stmt1234567",
"Action": ["s3:"
],
"Effect": "Allow",
"Resource": "
"
}
]
}

The upload works. When I use:

{
"Statement": [
{
"Sid": "Stmt13722196541",
"Action": ["s3:*"
],
"Effect": "Allow",
"Resource": "arn:aws:s3:::bucket_name"
}
]
}

The upload fails. What are the permissions needed on the S3 side (user or bucket policy) to allow the plugin to only have access to one of the S3 buckets? I know it's probably because it needs to be able to list all the buckets to find the one it's using, but I've been unable to find the right combination of policies that will allow the plugin to run.

Could this be added to the wiki pages? Thanks.

@ksclarke
Copy link
Author

I think this is the basic user policy?

{
"Statement": [
{
"Sid": "Stmt1372216541",
"Action": [
"s3:PutObject",
"s3:PutObjectAcl"
],
"Effect": "Allow",
"Resource": "arn:aws:s3:::bucket_name/*"
}
],
"Statement": [
{
"Sid": "Stmt1372212814",
"Action": [
"s3:ListBucket"
],
"Effect": "Allow",
"Resource": "arn:aws:s3:::bucket_name"
}
]
}

@prateekgupta
Copy link

@R-Gerard
Copy link

+1 @ksclarke 's policy works for me. It would be useful to include it in the documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants