WinterbäumeStateful AWS mocking for aws-sdk-rust

Intercept SDK calls in-process. No network I/O. Real state semantics.

In-Process

Implements the aws-smithy-runtime-api HttpClient/HttpConnector traits directly. No mock server to spin up, no ports to allocate, no network latency in tests.

Stateful

State persists across requests, isolated per account ID and region — matching real AWS isolation semantics. Build and tear down resources across multiple SDK calls.

48% API Coverage

4758 of 9966 operations across 154 AWS services, surpassing moto's 32.0%. Fully implemented services include S3, DynamoDB, SQS, Lambda, KMS, ECS, EKS, IAM, and many more.

Smithy-Backed

Per-service model.rs and wire.rs files are generated from AWS Smithy models, giving type-safe request parsing and response serialization across all implemented protocols.

Pluggable Backends

Swap the default in-memory store for Redis or DuckDB. Opt-in, dependency-free from the core service crates, injected through with_backend().

aws-smithy-mocks Compatible

Combine winterbaume's stateful backends with per-operation aws_smithy_mocks rule overrides. Winterbaume handles state; rules override specific calls.