2 個答案
- 最新
- 最多得票
- 最多評論
0
Hi,
I am assuming that if you're following the documentation to sign the requests you're using the AWS SDK, if so, then you don't need to worry about sigv4a as the SDK will automatically convert to this new version of the sigv4 format. You can find the information on the documentation here: https://docs.aws.amazon.com/AmazonS3/latest/userguide/MultiRegionAccessPointRequests.html, specifically with this paragraph:
- Requests must be signed using Signature Version 4A (SigV4A). When you use the AWS SDK, the SDK automatically converts a SigV4 signature to SigV4A. For more information about SigV4A, see Signing AWS API requests in the AWS General Reference.
Hope this helps.
Best,
已回答 2 年前
0
You can find code samples for the implementation of SigV4A in this repo https://github.com/aws-samples/sigv4a-signing-examples
相關內容
- 已提問 14 小時前
- AWS 官方已更新 2 年前
The issue with the SDK is that it does not allow use of the access points using the hostname (as mentioned in a previous question that I had asked: https://repost.aws/questions/QUe6vKotBZQEKZsqPn8f6AxQ/how-to-use-the-multi-region-access-point-in-aws-s-3-using-the-hostname). So using the bare REST API seems to be the only way here but that I cannot do unless the SigV4A signing process is publicly documented.