Encrypt Online
Theme

AWS SigV4 Calculator

Build an AWS canonical request and calculate its SigV4 signature

Calculations run in your browser without sending a request to AWS.

Build a request signatureHave an S3 signed link? Check the presigned URL

Use the signing service and region expected by the endpoint.

Request body, headers, and signing time

One name: value per line. Host and x-amz-date are added for you. For a failing request, use the headers listed in its SignedHeaders value.

Leave empty to sign all included headers. Paste the original list to reproduce a failing signature exactly.

For an existing request, use its original YYYYMMDDTHHMMSSZ value.

Sign with credentials (optional)

Use test credentials when debugging signing code. AWS checks IAM and KMS permissions when it receives a request.

Signing result

Canonical request

Enter the URL, method, service, and region. Add the headers and body to reproduce an existing request.

A secret key is only needed to calculate the signature. The AWS example includes public test credentials.

SignatureDoesNotMatch

Recreate the exact method, URL, body, headers, region, service, and timestamp from the failing request. Compare the canonical request first, then its SHA-256 hash and string to sign.

Keep the original S3 object path, including repeated slashes. S3 signs paths differently from other AWS services. A plus sign and a space also produce different signatures.

AWS canonical request format

Authorization headers and presigned URLs

This calculator puts the signature in an Authorization header. For a signature in an S3 URL's query string, use the S3 Presigned URL Debugger and follow the S3 signature mismatch guide.

Use an AWS SDK for production requests and credential refresh. SigV4a, streaming signatures, and presigned POST forms use different signing formats from the one shown here.

AWS signature troubleshooting reference

AWS signature reference values

Download examples (JSON)

Reproduce three published AWS S3 signatures and compare the canonical request, its SHA-256 hash, and the string to sign.

AWS GET Object reference

Reproduce AWS's published GET Object signature with an empty body and a signed Range header.

The canonical request hash and signature match AWS's published GET example. Keep the blank query line and the blank line after canonical headers.

Inputs and expected values
  1. Select Load AWS example in the calculator. It fills this request and the public example credentials.
  2. Keep the signing time at 20130524T000000Z, the body empty, and Payload signing set to SHA-256 of this body.
  3. Select Calculate signature, then compare the canonical request, hash in the string to sign, and signature below.
Request URL
https://examplebucket.s3.amazonaws.com/test.txt
Signed request header
Range: bytes=0-9
Signing time
20130524T000000Z
Canonical request
GET
/test.txt

host:examplebucket.s3.amazonaws.com
range:bytes=0-9
x-amz-content-sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
x-amz-date:20130524T000000Z

host;range;x-amz-content-sha256;x-amz-date
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Canonical request SHA-256
7344ae5b7ee6c3e7e6b0fe0640412a37625d1fbfff95c48bbb2dc43964946972
String to sign
AWS4-HMAC-SHA256
20130524T000000Z
20130524/us-east-1/s3/aws4_request
7344ae5b7ee6c3e7e6b0fe0640412a37625d1fbfff95c48bbb2dc43964946972
Expected signature
f0e8bdb87c964420e857bd35b5d6ed310bd44f0170aba48dd91039c6036bdb41

PUT with a dollar sign in the path

Reproduce AWS's PUT Object signature for a dollar sign in the object path and a nonempty request body.

The dollar sign becomes %24 in the canonical URI, and the exact body produces the published payload hash and PUT signature.

Inputs and expected values
  1. Paste the request URL below, choose PUT, and set Service to s3 and Region to us-east-1.
  2. Open Request body, headers, and signing time. Paste the header lines and exact body without a final newline, choose SHA-256 of this body, and set Signing time to 20130524T000000Z.
  3. Open Sign with credentials. Enter access key ID AKIAIOSFODNN7EXAMPLE and the public example secret below. Leave Session token and Signature to compare empty.
  4. Select Calculate signature and compare the canonical path, body hash, and signature.
Request URL
https://examplebucket.s3.amazonaws.com/test$file.text
Headers included in the signature
Date: Fri, 24 May 2013 00:00:00 GMT
x-amz-storage-class: REDUCED_REDUNDANCY
Exact request body
Welcome to Amazon S3.
Public AWS example secret
wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
Canonical request
PUT
/test%24file.text

date:Fri, 24 May 2013 00:00:00 GMT
host:examplebucket.s3.amazonaws.com
x-amz-content-sha256:44ce7dd67c959e0d3524ffac1771dfbba87d2b6b4b4e99e42034a8b803f8b072
x-amz-date:20130524T000000Z
x-amz-storage-class:REDUCED_REDUNDANCY

date;host;x-amz-content-sha256;x-amz-date;x-amz-storage-class
44ce7dd67c959e0d3524ffac1771dfbba87d2b6b4b4e99e42034a8b803f8b072
Canonical request SHA-256
9e0e90d9c76de8fa5b200d8c849cd5b8dc7a3be3951ddb7f6a76b4158342019d
String to sign
AWS4-HMAC-SHA256
20130524T000000Z
20130524/us-east-1/s3/aws4_request
9e0e90d9c76de8fa5b200d8c849cd5b8dc7a3be3951ddb7f6a76b4158342019d
Expected signature
98ad721746da40c64f1a55b78f14c238d841ea1380cd77a1b5971af0ece108bd

Query parameter order

Query parameters supplied in reverse order still reproduce AWS's published List Objects signature.

The canonical query sorts max-keys before prefix. Reordering the same query values preserves the published signature.

Inputs and expected values
  1. Paste the request URL below, choose GET, and set Service to s3 and Region to us-east-1.
  2. Open Request body, headers, and signing time. Leave headers and body empty, choose SHA-256 of this body, and set Signing time to 20130524T000000Z.
  3. Open Sign with credentials. Enter access key ID AKIAIOSFODNN7EXAMPLE and the public example secret below. Leave Session token and Signature to compare empty.
  4. Select Calculate signature. The canonical query sorts the parameters and reproduces AWS's published List Objects signature.
Request URL with reversed query order
https://examplebucket.s3.amazonaws.com/?prefix=J&max-keys=2
Public AWS example secret
wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
Canonical query
max-keys=2&prefix=J
Canonical request
GET
/
max-keys=2&prefix=J
host:examplebucket.s3.amazonaws.com
x-amz-content-sha256:e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
x-amz-date:20130524T000000Z

host;x-amz-content-sha256;x-amz-date
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Canonical request SHA-256
df57d21db20da04d7fa30298dd4488ba3a2b47ca3a489c74750e0f1e7df1b9b7
String to sign
AWS4-HMAC-SHA256
20130524T000000Z
20130524/us-east-1/s3/aws4_request
df57d21db20da04d7fa30298dd4488ba3a2b47ca3a489c74750e0f1e7df1b9b7
Expected signature
34b48302e7b5fa45bde8084f4b7868a86f0a534bc59db6670ed5711ef69dc6f7

These historical examples use AWS's public sample credentials. They check signature calculation locally; AWS separately checks credential validity, request time, and permissions.

Checked 2026-10-20. From the site's webapp3 directory, run npm run check:citation-evidence to compare the tool results with the saved expectations. The JSON includes every input, expected output, and source hash.

Inputs are not saved. The site may load analytics and advertising. Privacy details.