AccessDenied for downloading PR build artifacts
See original GitHub issueThis is what I see when I try to download a PR build artifact
Going past that, I get this
I think the s3 policy needs to be updated. This is what I used on my bucket
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Principal": "*",
"Action": [
"s3:GetObject",
"s3:GetObjectAcl",
"s3:PutObject",
"s3:PutObjectAcl"
],
"Resource": "arn:aws:s3:::rw-pr/*"
}
]
}
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Problem retrieving packages from Artifacts - Access denied
I have build a docker box to use it when building the solution. When building the solution without using proxy everything goes well....
Read more >az artifacts universal download fails with Access denied and ...
Describe the bug Command Name az artifacts universal download ... Using the above I'm able to download the artifact in a build context....
Read more >Access denied when trying to deploy jars to a Nexus 3 ...
Access denied when trying to deploy jars to a Nexus 3 repository using Maven but able to download dependencies.
Read more >"Access to the path is denied" when using Publish Artifact ...
I keep getting a "Access to the path is denied." error whenever I specify additional items in the Contents setting on the Publish...
Read more >Access denied downloading artifact from nexus-Apache Mail ...
Not sure what happened there.) > >>> > >>> I'm having trouble downloading an artifact from a nexus pro repo in a >...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@cannikin Could you change the bucket name, and make sure it has the correct policy?
It works now, see for example here https://github.com/redwoodjs/redwood/pull/1484#issuecomment-728244658 (bucket name and policy were updated)