Skip to main content
The Sidecar keeps serving entitlements when the Stigg API is unreachable. When it encounters startup errors (such as an invalid API key) or network errors, it continues to run and serves entitlements from:
  1. The persistent cache, if configured
  2. The global fallback strategy
In the examples below, replace <tag> with the latest version in the ECR Public Gallery.

​
Persistent cache

For cached data to survive service restarts, or to be shared across multiple instances of the Sidecar service, use Redis as the cache layer by providing the REDIS_* environment variables:
When Redis is configured, you must also run the Persistent Cache Service in a separate process to keep entitlements and usage data in Redis up to date. If you don’t configure Redis, you can simply run the Sidecar by itself with in-memory caching only.

​
Global fallback strategy

A global fallback strategy can be set by providing the Sidecar service with the ENTITLEMENTS_FALLBACK environment variable. It expects a JSON object in string format. For example, the following global fallback configuration:
Can be formatted using JSON.stringify and then set as the value of ENTITLEMENTS_FALLBACK when running the container:
Entitlement check responses that were resolved from fallback values contain isFallback: true.

​
Offline mode

During local development or testing, you might want to avoid making network requests to the Stigg API. To do this, run the Sidecar service in offline mode by setting OFFLINE=TRUE. When enabled, API key validation always succeeds, regardless of the key provided:
In offline mode, the Sidecar respects the global fallback strategy, and entitlement evaluations are limited to the values defined as fallback entitlements. All other Sidecar service methods effectively become no-ops. For example: