How do I mock the Amazon SQS API locally?

Install stunt, add a one-service block to stunt.yaml (adapter: embedded:sqs-style), and run stunt up. You get a local, stateful stand-in for Amazon SQS API 2012-11-05 — 2 routes over rest — with no remote account, no network, and no bills.

Is the Amazon SQS API mock data synthetic?

Yes — entirely. The adapter returns generated data only; stunt's adapter lint rejects real-looking secrets and PII at build time. It simulates the shape and behavior of Amazon SQS API (routes, status codes, pagination, webhooks), never real records.

← all adapters

sqs-style

simulates Amazon SQS API 2012-11-05

restadapter v0.1.02 routes

use it

# add to stunt.yaml
services:
  sqs:
    adapter: embedded:sqs-style

# then
$ stunt up

The embedded: source extracts this adapter from the binary — no git clone, fully offline.

how to mock the Amazon SQS API locally

Install stunt, paste the service block above into stunt.yaml, run stunt up — then point your client at localhost instead of Amazon SQS API. It works offline, keeps state across requests and restarts, and every response is synthetic: the route shapes, status codes, pagination, and webhook delivery follow the real Amazon SQS API 2012-11-05 surface — the data is fake, the behavior is real.

backing stores

queuesmessages

routes (2)

POST/

POST/{queueName}

want more of the Amazon SQS API surface? adapters are YAML + Starlark — the authoring guide covers adding routes, fixtures, and state machines. Open an issue for anything big first, or just file a PR — merged routes ship in the next release.