add documentation about S3 signature validation - #861
Conversation
Deploying localstack-docs with
|
| Latest commit: |
607442e
|
| Status: | ⚡️ Build in progress... |
|
I wrote this in the Linear ticket but might be worth sharing it here too: I think we're good on the engineering review side, if the writing looks good, I wrote the feature and we are in the middle of revisiting the ownership of services (Aiden is in another squad now and Anastasia on leave), so if it looks good to you Quetzalli, I think we can merge it 👍 I cannot remove their review request because they are still marked as codeowners. If you really want a second ENG review, maybe @viren-nadkarni can have a look, but I don't think it is necessary |
|
@quetzalliwrites anything else we need to merge this before the release tomorrow? |
Add "by default" per review feedback, since IAM policy enforcement can be enabled to add the authorization check this sentence otherwise reads as permanently absent.
|
@bentsku Pushed |
Co-authored-by: Quetzalli <alejandra.olvera.novack@gmail.com>
3 participants
In S3, we have special behavior for Signature Validation, something we don't do for other services.
We have supported pre-signed URLs signature validation for a long time now, but we didn't have a lot of documentation in how to best use it, which credentials to use and what are the limitations.
We recently also added signature validation for all requests, not only pre-signed for a prospect (Canva).
This felt like the right time to add documentation about both feature together as they are closely related and share some logic about which credentials you should use.
AWS Documentation on pre-signed URLs: https://docs.aws.amazon.com/AmazonS3/latest/userguide/using-presigned-url.html
For all and regular request signing: https://docs.aws.amazon.com/AmazonS3/latest/developerguide/sig-v4-authenticating-requests.html
Related
towards AWS-1256
closes DOC-401