Sign with AWS Signature v4#
Supply credentials, a region, and a service, and the app signs the whole request.
AWS Signature v4 signs the whole request the way Amazon Web Services expects. When you send, the app computes a SigV4 signature from your credentials and the request itself. The app then attaches the signature. Use this method for API Gateway, S3, Lambda, and any endpoint protected by SigV4.
Fill in the credential fields#
You supply your credentials. You also tell the signer which service and region to sign for.
- Access key ID and Secret access key are your AWS credentials. The app masks the secret. Either field accepts a
{{variable}}, so you can keep the credentials in an environment. - Region is the AWS region, for example
us-east-1. - Service is the target service's signing name, for example
execute-apifor API Gateway,s3, orlambda. - Session token is optional. Fill it in only when you use temporary credentials from AWS STS.
The signature covers the request, so the app computes it at send time. If you change the URL, headers, or body, the app signs the next send again to match.