From 3fa976c6aa7af6102eb701f0b85ed0f13287350d Mon Sep 17 00:00:00 2001 From: Musab Date: Fri, 28 Feb 2025 15:15:53 -0500 Subject: [PATCH] Reflect discussion in (nested / hard-to-find) issue: https://github.com/gaul/s3proxy/issues/783 in the wiki. --- Storage-backend-examples.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/Storage-backend-examples.md b/Storage-backend-examples.md index 01c510c..2bc6294 100644 --- a/Storage-backend-examples.md +++ b/Storage-backend-examples.md @@ -144,6 +144,10 @@ jclouds.credential=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx jclouds.endpoint=https://objects.dreamhost.com ``` +When pointing jclouds to a generic S3 API (`jclouds.provider=s3`), jclouds uses [AWSSIGV2](https://docs.aws.amazon.com/AmazonS3/latest/API/Appendix-Sigv2.html) authentication by default. AWSSIGV2 is deprecated and may not be supported by S3 providers like Cloudflare R2 (e.g. https://github.com/gaul/s3proxy/issues/783). + +You may override the the jclouds default to make it use AWSSIGV4 by setting `jclouds.s3.signer-version=4` (https://issues.apache.org/jira/browse/JCLOUDS-1594). However, this may not work for PUT requests for certain S3 providers (e.g. https://github.com/gaul/s3proxy/issues/783). + ### Swift (non-Keystone) outdated?!