LocalStack "service not yet implemented" in CI

LocalStack emulates a subset of AWS. When a test calls an operation the running edition does not implement, LocalStack returns an "not yet implemented" error. Either use a supported operation or an edition that covers it.

What this error means

An AWS call against LocalStack fails with "not yet implemented" or "API for service ... not yet implemented or pro feature", not a connection or credential error.

LocalStack

An error occurred (InternalError) when calling the X operation:
API for service 'X' not yet implemented or pro feature - please check the documentation

Common causes

The operation is not emulated by this edition

The community edition covers common operations; a less common API or service may not be implemented.

The feature is Pro-only

Some services and operations are only available in LocalStack Pro, which needs an auth token.

How to fix it

Use a supported operation or service

Check the LocalStack coverage docs for the operation you call.
Adjust the test to a supported operation where possible.
If the feature is essential, move to an edition that supports it.

Enable the Pro edition for Pro-only features

If the operation is Pro-only, provide the LocalStack auth token so the Pro service starts.

.github/workflows/ci.yml

env:
  LOCALSTACK_AUTH_TOKEN: ${{ secrets.LOCALSTACK_AUTH_TOKEN }}

How to prevent it

Check service and operation coverage before writing the test.
Prefer emulated operations in the community edition where possible.
Provide a Pro token when a test genuinely needs a Pro-only feature.