-
Notifications
You must be signed in to change notification settings - Fork 490
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
Athens is creating unsigned requests to S3 buckets causing 403 errors #1961
Comments
The same issue, I guess this is caused by #1950. |
Experiencing absolutely the same issue. @yongzhang is there any estimations when fix #1963 can be released? thanks. |
I'm not the maintainer, I'm also waiting someone to review my PR. But you can use v0.13.x at the moment. |
@midestefanis thanks for the report! @yongzhang I've looked at your PR and left a comment. Apologies for not getting to both of these sooner, I was traveling at the time. |
Describe the bug
I'm running athenas in AWS ECS Fargate with S3 as the storage. I've followed this documentation to configure everything -> https://docs.gomods.io/install/install-on-aws-ecs-fargate/
This are the ENVs in the athenas container:
Error Message
While testing the walktrhough example i've found this problem:
This is what athens is logging when i get locally that 500 error:
To Reproduce
I've followed this documentation and it's failing for me -> https://docs.gomods.io/install/install-on-aws-ecs-fargate/
Expected behavior
Athens should be able to reach S3 buckets with no errors
Environment (please complete the following information):
Additional context
I have contacted AWS to help me understand the reason for this 403 and they have told me that it is because the requests to S3 are coming out unsigned, that is, anonymously. AWS reviewed the configuration and they see everything valid, they still do not understand why this happens.
The text was updated successfully, but these errors were encountered: