Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

The Kinesis mock documentation at https://docs.localstack.cloud/aws/services/kinesis/#performance-tuning suggests that the scala engine will be the future default and already is superior regarding performance.

We recently encountered issues using this option in CI builds, as it causes the container to reach out to the GitHub API (source) to determine which kinesis-mock.jar needs to be downloaded.

By default (for anonymous requests), this traffic is rate limited after a budget of 60 requests per hour (source).

We are aware that it is possible to get a more generous budget by setting GITHUB_API_TOKEN, which is not an option in this case.

We are also aware that these outgoing requests can be prevented by mounting a persistent volume as /var/lib/localstack, which is also not an option for us.

Note that the requests towards GitHub are not required when using the node engine.

This problem is surprising, feels like other teams should have encountered it too but I could not find an issue about it.
Feels like we might be missing something.

Expected Behavior

A localstack image variant with a baked-in scala kinesis mock jar is published by default, which does not require connectivity to Github to run.

Traffic towards Github may be impacted by rate limits or firewall settings, especially when running in a CI build.

How are you starting LocalStack?

With a docker-compose file

Steps To Reproduce

• Configure localstack to run kinesis
• Do not mount a persistent volume for /var/lib/localstack
• Use KINESIS_MOCK_PROVIDER_ENGINE=scala
• Observe required request towards Github API

Environment

- LocalStack version: 4.13.1

Anything else?

No response