s3 extension can no longer access newly created buckets (requires sig v4)

Description

Lucee's built in s3 support only supports the older signature which cannot be used to access any newly created buckets, but it seems to depend on region according to the updated https://aws.amazon.com/blogs/aws/amazon-s3-update-sigv2-deprecation-period-extended-modified/

??
The Europe (Frankfurt), US East (Ohio), Canada (Central), Europe (London), Asia Pacific (Seoul), Asia Pacific (Mumbai), Europe (Paris), China (Ningxia), Europe (Stockholm), Asia Pacific (Osaka Local), AWS GovCloud (US-East), and Asia Pacific (Hong Kong) Regions were launched after 2013, and support SigV4 but not SigV2. If you have code that accesses S3 buckets in that region, it is already making exclusive use of SigV4.
??

https://dev.lucee.org/t/deprecation-of-s3-storage-access-june-2019/5751

https://brianklaas.net/aws/coldfusion/2019/06/20/End-Of-V2-Signature-Requests-For-S3.html

Environment

None

Assignee

Unassigned

Reporter

Zac Spitzer

Priority

Blocker

Labels

None

Fix versions

None

Sprint

None
Configure