Cloud Sync Task to AWS GovCloud fails authorization
Description
Problem/Justification
Impact
Activity
Caleb October 27, 2023 at 4:58 PM
this is an issue with our documentation not being very clear. We’ve opened up a ticket to have the docs improved so I’m going to close this one since there is nothing to “fix”.
Jim Dishaw October 26, 2023 at 4:29 PM
If I ignore both the hints provided by the UI and also deselect the “Disable endpoint Region” everything appears to work. I thought I tested all permutations, but obviously not.
Perhaps the hints need to be reworded because it definitely led me astray.
Jim Dishaw October 26, 2023 at 4:12 PM
The option was selected (the hint says to select the option when using a custom endpoint).
I did attempt with and without v2 signatures. When the v2 signatures is not selected, the following error occurs:
2023/10/26 12:06:07 Failed to sync: AuthorizationHeaderMalformed: The authorization header is malformed; the region 'us-east-1' is wrong; expecting 'us-gov-east-1'
Without the v2 signatures option, it appears that the custom endpoint is being ignored.
Vladimir Vinogradenko October 26, 2023 at 8:50 AM
is “Use v2 signatures” option enabled? (it should not be)
Automation for Jira October 23, 2023 at 4:51 AM
Thank you for submitting this TrueNAS Bug Report! So that we can quickly investigate your issue, please attach a Debug file and any other information related to this issue through our secure and private upload service below. Debug files can be generated in the UI by navigating to System -> Advanced -> Save Debug.
https://ixsystems.atlassian.net/servicedesk/customer/portal/15/group/37/create/153
When a cloud sync task to AWS GovCloud is attempted, the following error is reported
Failed to sync: InvalidRequest: The authorization mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.status code: 400The credentials appear to work when tested with the “Verify Credential” in “Cloud Credentials”
The Cloud Sync task works with the non-GovCloud AWS (e.g. us-east-1).