---
title: "Mock AWS Services | Speedscale Docs"
description: "Mock AWS services with Speedscale to easily record and replay traffic, utilizing pre-made mocks and detailed guides for seamless API testing."
canonical: "https://docs.speedscale.com/proxymock/aws/"
---

[Documentation index](https://docs.speedscale.com/proxymock/llms.txt) | [Markdown](https://docs.speedscale.com/proxymock/aws/index.md) | [Canonical page](https://docs.speedscale.com/proxymock/aws/)

# Mock AWS Services

Speedscale can be used with most AWS services simply by running your app and recording traffic. As a convenience, we also provide some pre-made mocks for easy of use purposes. Making a new mock is very easy and you can learn more about it in the [create your own mocks](https://docs.speedscale.com/proxymock/agent-tutorial/) section.

A list of known supported technologies can be found [here](https://docs.speedscale.com/reference/technology-support/). However, your API or Database may just work so you should try it out.

<a id="available-aws-service-guides"></a>

## Available AWS Service Guides

*   [AWS SES (Simple Email Service)](https://docs.speedscale.com/proxymock/aws/ses/) - Record and mock email sending with detailed step-by-step instructions
*   [DynamoDB](https://docs.speedscale.com/proxymock/aws/dynamodb/) - Pre-made mock for common DynamoDB operations

<a id="general-api-information"></a>

## General API Information

AWS Services use a variety of different API formats and protocols. Speedscale will automatically detect the API format and use the correct one. Here are some general purpose insights for the AWS APIs that utilize HTTP.

<a id="headers"></a>

### Headers

*   X-Amz-Target: If present, this header contains the API version and the command. For example, `DynamoDB_20120810.GetItem` tells the API the service is DynamoDB and the command is GetItem.
*   Authorization: This header typically contains a proprietary token that is used to authenticate the request. Usually this comes in a format starting with `AWS4-HMAC-SHA256` or something similar.
*   X-Amz-Date: This header contains the date and time of the request in ISO 8601 format.
*   X-Amz-Security-Token: This header contains a temporary security token that is used to authenticate the request.

Generally speaking, changing the values of these headers is not necessary to use the mock. The hostname of the service is typically enough to deduce most of the necessary target information.

<a id="body"></a>

### Body

The body of the request and response is typically a JSON object. The structure of the body is specific to the API and command.