{ "Version": "2012-10-17", "Statement": [ { "Sid": "Stmt1436196480000", "Effect": "Allow", "Action": [ "s3:GetBucketLocation", "s3:ListAllMyBuckets", "s3:ListBucket" ], "Resource": [ "arn:aws:s3:::*" ] } ] }
And for full-access to that particular bucket:
{ "Version": "2012-10-17", "Statement": [ { "Sid": "Stmt1436195288000", "Effect": "Allow", "Action": [ "s3:*" ], "Resource": [ "arn:aws:s3:::bamboo-artifacts", "arn:aws:s3:::bamboo-artifacts/*" ] } ] }
I get the same error switching back from Atlassian Cloud to Amazon S3 with a previously created bucket name. With a new bucket name it works (artifacts storage settings get saved), but the build artifacts are not copied.
Hi Jeff,
Did you try to follow the instructions here: Add AWS credentials to Bamboo? This should do the trick for you.
Hope this helps!
Cheers!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I didn't try that, and that may work, but what is the point of the S3 artifact bucket setup UI in Bamboo if I just get the error above? I can do everything manually using the article you gave me above, but it seems like Bamboo should be able to integrate more easily/automatically based on the Bamboo UI.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.