https://docs.aws.amazon.com/AmazonS3/latest/API/API_HeadBucket.html
This action is useful to determine if a bucket exists and you have permission to access it. The action returns a 200 OK if…
I'm not sure which way to go to resolve this. I think I'll use a GET request to indirectly assert the region is valid and display a meaningful error message if it does not, using the 400…
Using GET the 400 payload is present, you are correct: HEAD hides it somewhere in the codepath.
GET / HTTP/1.1
Host: minio:9000
User-Agent: MinIO (linux; amd64) minio-go/v7.0.61
Author…@gusted looked at it and found some information. I'll try using GET instead see where that gets me.
HeadBucket
If you have set
s3_region = "us-east-1"in your config file then it is a valid scope, otherwise it is not
That fixed the problem.
(but there is a redirection mechanism in the error…
HeadBucket
The logs with debug:
2023-08-28T15:12:50.827687Z INFO garage_api::generic_server: 127.0.0.1:40918 HEAD /forgejo/
2023-08-28T15:12:50.827700Z DEBUG garage_api::generic_server: Request {…HeadBucket
I would like to let garage know that 20230828/us-east-1/s3/aws4_request is a valid scope. A pointer on how to do that would be much appreciated.
HeadBucket
Here is a reproducer for this issue. It may simply be a misconfiguration but it not trivial to figure out for me because I do not have any experience (yet) with garage.
- Launch garage [from…