You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While testing the walktrhough example i've found this problem:
export GOPROXY=http://athens-*******.elb.us-west-2.amazonaws.com,direct
export GO111MODULE=on
go run .
go: github.com/athens-artifacts/samplelib@v1.0.0: reading http://athens-*************.elb.us-west-2.amazonaws.com/github.com/athens-artifacts/samplelib/@v/v1.0.0.mod: 500 Internal Server Error
This is what athens is logging when i get locally that 500 error:
Expected behavior
Athens should be able to reach S3 buckets with no errors
Environment (please complete the following information):
OS: [e.g. Linux 64bit] : Alpine Linux amd64
Go version : go1.20.14
Proxy version : v0.14.0
Storage (fs/mongodb/s3 etc.) : s3
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:
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: