[Feature]: Add support for AWS Emulator

Offen
#12,159 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
22/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
aws, docker, java
Bereich
testing

Rechercherichtung

Start with the existing LocalStack module, which the issue names as the model for a new AwsEmulatorContainer module, and with the GenericContainer usage it replaces. Decide how the official AWS Emulator Dockerfile and image are consumed, and how the /__admin/health check, endpoint URL, credentials, truststore helper and default 2 GiB memory limit are exposed. Done means a module with tests that start the container, pass the health check and point an AWS SDK client at it. The issue has no assignee and needs maintainer design input first.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

type/feature
Module

None

Problem

AWS Emulator (released 11 Nov 2026) is an official, free local emulator of AWS APIs. There is currently no Testcontainers module for it. Users must manually build a Docker image from AWS’s Dockerfile, write a custom GenericContainer, and handle the self-signed certificate/truststore required by the AWS SDK for Java. This creates friction for Java teams that already use Testcontainers for integration tests.

Solution

Add a first-class AwsEmulatorContainer module (similar to the existing LocalStack module) that:

  • Provides a ready-to-use container (or easy image builder based on the official Dockerfile)
  • Includes a health check on /__admin/health
  • Exposes helpers for the endpoint URL, credentials, and Java truststore configuration
  • Defaults to telemetry off and the recommended 2 GiB memory limit

Links::
GitHub: [github.com/aws/aws-emulator](https://github.com/aws/aws-emulator)
Docs: [docs.aws.amazon.com/emulator](https://docs.aws.amazon.com/emulator/)
Docker getting started: [docs.aws.amazon.com/emulator/latest/userguide/getting-started-docker.html](https://docs.aws.amazon.com/emulator/latest/userguide/getting-started-docker.html)
Announcement: [aws.amazon.com/blogs/aws/test-your-applications-against-aws-locally-with-aws-emulator](https://aws.amazon.com/blogs/aws/test-your-applications-against-aws-locally-with-aws-emulator/)

Benefit

Java teams can start an isolated AWS Emulator instance with a few lines of code, point the AWS SDK at it, and get clean per-test or per-class lifecycle management. This lowers the barrier to adopting the official emulator for local and CI testing, especially as an alternative to LocalStack.

Alternatives
  • Continue writing custom GenericContainer subclasses (current state).
  • Use the native Linux package + process management outside Testcontainers.
  • Use LocalStack (requires a token for many services and is not the official AWS emulator).
  • Wait for an embedded mode for Java (currently only available for Rust).
Would you like to help contributing this feature?

No

Vorherrschende Sprache
Java
Sterne
8.8k
Forks
2k
Ø Merge
5 T. 21 Std.
Gemergte PRs (30 T.)
15

Entwicklungsumgebung

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus testcontainers/testcontainers-java

Alle Issues in testcontainers/testcontainers-java

Ähnliche Issues

Weitere Issues zu Java

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.