Example REST Requests

This section shows the steps to sign a request, using sample AWS access identifiers.

If you follow these steps using these identifiers, you will generate the same signature strings in the examples. Although this can help verify your request generation code, you cannot make actual requests with these example requests.

URL encode the request's comma (,) and colon (:) characters, so that they don't get misinterpreted. For more information about converting to RFC 3986 specifications, see documentation and code samples for your programming language.

Calculate an RFC 2104-compliant HMAC with the SHA256 hash algorithm using the string above
with our "dummy" Secret Access Key: 1234567890. For more information about this step, see documentation and code samples for your programming language.

M/y0+EAFFGaUAp4bWv/WEuXYah99pVsxvqtAuC8YN7I=

URL encode the plus (+) and equal (=) characters in the signature:

M%2Fy0%2BEAFFGaUAp4bWv%2FWEuXYah99pVsxvqtAuC8YN7I%3D

Add the URL encoded signature to your request, and the result is a properly-formatted signed request:

Examples of Other Signed Requests

The previous section went through a detailed process for signing an ItemLookup request. This section presents examples of unsigned requests, the string to sign generated from them, and the final signed request. These examples can make excellent test cases for your software. All examples use the "dummy" AWS access identifiers used earlier in the Steps to Sign the Example Request.

ItemSearch Examples

The following examples show the ItemSearch
request without a signature, with the string to sign, and the signed request.