LocalStack Pro service without a token / auth token required in CI

By Kaveh Alemi·Latchkey

LocalStack Pro services require a valid auth token to activate. When a Pro feature is enabled but LOCALSTACK_AUTH_TOKEN is missing or invalid, activation fails and the Pro service never comes up.

What this error means

LocalStack logs an activation or license error, or a Pro-only service is unavailable, because the auth token was not provided or was rejected.

localstack activation failed: LOCALSTACK_AUTH_TOKEN is missing or invalid;
pro services will not be available

Common causes

The auth token is not set in CI

A Pro service was requested but LOCALSTACK_AUTH_TOKEN was never injected, so activation cannot proceed.

The token is invalid or expired

A wrong or expired token is rejected, leaving Pro services inactive.

How to fix it

Provide the auth token from a secret

Set LOCALSTACK_AUTH_TOKEN from a CI secret so Pro activation succeeds before tests run.

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

Stay on community features when no token exists

If you cannot supply a Pro token, restrict tests to community-supported services and operations.

How to prevent it

• Store the LocalStack auth token in CI secrets and reference it in the job.
• Keep the token current so Pro activation does not fail mid-run.
• Restrict tests to community features when no Pro token is available.

Frequently asked questions

Related guides

References

• GitHub Actions documentation