Bug #19582
openus-east-1 seems to be assumed by the s3 interface
0%
Description
While experimenting with authentication on a new ceph project, one using the s3-compatible interface, I discovered that I needed to set a particular region, us-east-1.
I know that's a well-known aws region, but I did not expect ceph to require it. Nevertheless, the logs said
2017-04-11 12:38:49.607490 7f9c3d3d0700 10 v4 credential format = WHF0J757LOLM09WMNIJT/20170411/us-east-1/s3/aws4_request
followed by
2017-04-11 12:38:49.607496 7f9c3d3d0700 10 credential scope = 20170411/us-east-1/s3/aws4_request
To the best of my knowledge, we did not name our region us-east-1: we would be more likely to name it can-east-1, as we're not in the US (;-))
If these are, as I assume, set in the ceph s3 interface, could we return an error saying something like "you must use a region of us-east-1 for compatibility with s3" ?
--dave
IMHO, including the region in the v4 authentication serves to make it harder to use anything except genuine Amazon s3, a bit of a self-serving change on their part. I hate it when people do that (:-()