Skip to main content
Lerian CCS reads its configuration from the process environment at startup. You set these variables at deploy time. A service restart makes them take effect. A small set of operational knobs also accepts changes at runtime through Systemplane. BYOC configuration essentials documents the backbone every Lerian Go service shares. In the tables below, the Default / Required column shows the value the service applies when you leave the variable unset. A bold qualifier marks a variable you must set, such as Required or Required in production. means the service applies no default. A variable flagged Sensitive. carries credential or key material. Inject it from your secret manager at deploy time. Never commit a value. Where a value in the shipped example file differs from the value the code applies, this page publishes the code value.

Service and runtime

License

CORS, TLS, and proxies

Multi-tenancy

PostgreSQL

Redis

Messaging and circuit breaker

Outbox

Lerian CCS writes each outbound message to a transactional outbox in the same database transaction as the state change. The OUTBOX_ family below configures the dispatcher that the shared platform library runs.

CCS outbox overrides

Streaming

The Lerian streaming library reads the STREAMING_ family, not the service configuration. Lerian Streaming Hub delivers the published events.

STA integration

Lerian CCS sends every outbound file to BACEN through Lerian STA and receives the answers back from it.

Reporter integration

Lerian Reporter renders the daily ACCS001 file, so it is a mandatory upstream. The readiness probe treats it as a hard dependency. Start Lerian Reporter before you expect Lerian CCS to become ready.

Service discovery

The Lerian service-discovery library reads the SD_ family, not the service configuration. Lerian CCS resolves other services and does not register itself, so it needs no advertised address.

Authentication

Machine-to-machine credentials

Lerian CCS mints an outbound token per upstream through Lerian Access Manager. Each upstream carries its own credential pair. No upstream shares a credential, and the service has no fallback.

Encryption and idempotency

API documentation

Telemetry and metrics

Rate limits

Lerian CCS applies five rate-limit tiers to the /v1 routes. The export tier covers heavy reads such as audit and reconciliation queries. The dispatch tier covers heavy writes that call an upstream.

Readiness and shutdown

Lerian CCS exposes GET /health for liveness and GET /readyz for readiness on the main port, plus GET /version and GET /metrics. With multi-tenancy on it also exposes GET /readyz/tenant/{id}. See Health and readiness for the probe contract and Operating Lerian CCS for the probe list.

Object storage

Lerian CCS reads inbound files from one bucket and writes outbound files to another. Both accept any S3-compatible store. An empty bucket name marks the matching readiness check as skipped.

Retention and regulatory settings

Integrating with Lerian CCS covers the API surface, the error codes, and the published events.