The immediate fallout sent developers searching for replacements. Three tools have emerged as the leading contenders, each operating at a different layer of the testing stack.

Moto, a Python library, mocks AWS calls directly in-process with no Docker dependency. It patches boto3 calls through an in-memory mock, making tests fast but limiting it to Python-first teams. Floci, a Go-based service running as a Docker container, offers broader language support without requiring authentication. LocalStack Community edition remains available but now requires a free non-commercial token.

The choice between them depends on testing philosophy. Moto excels at unit-level AWS mocking with zero infrastructure overhead. Floci suits integration testing where real HTTP endpoints matter. LocalStack Community still offers the most complete AWS emulation but introduces the authentication friction that drove the migration in the first place.

For teams that relied on LocalStack's free tier in CI, the path forward likely involves Moto for Python projects and Floci or Testcontainers for polyglot stacks.