S3: Default to signature=v4 when using an AWS endpoint
authorJoey Hess <joeyh@joeyh.name>
Wed, 13 Aug 2025 17:18:35 +0000 (13:18 -0400)
committerJoey Hess <joeyh@joeyh.name>
Wed, 13 Aug 2025 17:18:35 +0000 (13:18 -0400)
commit215640096f6a3469c119d50373f3035cf19fe130
tree6fb0013a83aa928c76e08defb50535c53753273d
parentedc1d92059151e62f53375496656143fc3179c2f
S3: Default to signature=v4 when using an AWS endpoint

* S3: Default to signature=v4 when using an AWS endpoint, since some
  AWS regions need v4 and all support it. When host= is used to specify
  a different S3 host, the default remains signature=v2.
* webapp: Support setting up S3 buckets in regions that need v4
  signatures.

For the webapp, went ahead and added all current S3 regions
(except govcloud, which  is not usable by everyone).

Sponsored-by: Dartmouth College's DANDI project
CHANGELOG
Remote/Helper/AWS.hs
Remote/S3.hs
doc/bugs/fails_to_authenticate_into_S3_for_initremote__63__/comment_4_d9a3fdfa34b780aafb5e5874fc8d98bc._comment [new file with mode: 0644]
doc/special_remotes/S3.mdwn