Status/Resolution/Reason: Closed/Fixed/Fixed
Reporter/Name(from Bugbase): Andrew Jackson / Andrew Jackson ()
Created: 03/15/2017
Components: Language, CF Component
Versions: 2016,2018
Failure Type: Non Functioning
Found In Build/Fixed In Build: All / 2018,0,0,312276
Priority/Frequency: Normal / All users will encounter
Locale/System: ALL / Win All
Vote Count: 2
Problem Description:
The CF built in AWS S3 functionality only works with version 2 of Amazons signature versions. There are a few regions that only support the newer version 4 (AWS4-HMAC-SHA256).
Steps to Reproduce:
Create an S3 bucket in one of the regions that only support v4 (AWS4-HMAC-SHA256). See https://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region for a breakdown of regions and supported signature versions.
Actual Result:
Depending on what one is trying to achieve, you could see either:
"The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256."
Or if doing something like a cfdirectory:
"The AWS Access Key Id you provided does not exist in our records.</Message><AWSAccessKeyId>null</AWSAccessKeyId>"
where the signature doesn't work and hence returns "null" as the "AWSAccessKeyId" value.
Expected Result:
The same working behaviour as seen when using the currently support CF Amazon S3 functionality with S3 buckets in regions that support version 2 signatures
Any Workarounds:Attachments:
Comments: