Skip to main content
Lerian STA is the Lerian-owned rail that transmits and receives files with the BACEN STA hub. You set these variables at deploy time. A service restart makes them take effect. Every Lerian Go service shares a universal backbone — server, datastores, multi-tenancy, telemetry, plugin authentication, and licensing. BYOC configuration essentials documents that backbone once. This page covers only the variables distinctive to Lerian STA. In the tables below, the Default / Required column shows the default value. A bold qualifier marks a variable you must set, such as Required or Required in production. means no default. A variable flagged Sensitive carries credential or key material. Inject it from your secret manager at deploy time. Never commit a value.

Service and runtime

Lerian STA exposes /health (liveness) and /readyz (readiness) on the main port, plus /version and /metrics. When you enable multi-tenancy, it also exposes GET /readyz/tenant/{id}. See Health and readiness for the probe contract.

Object storage

Lerian STA persists transfer bytes and inbound downloads to an S3-compatible object store. Each subsystem configures its own connection through the AWS SDK, so the same wiring drives AWS S3, MinIO, or a local store.

Envelope encryption

Lerian STA protects operator credentials with AES-GCM envelope encryption. The manager process always needs the master-key material. A missing or malformed value aborts boot.

Trust store

Each tenant uploads the X.509 root certificates that Lerian STA uses to validate BACEN’s server TLS certificate. STA authenticates to BACEN with HTTP Basic operator credentials and attaches no client certificate. The trust-store module is always on. Lerian STA persists certificate PEM bodies to the object store, so it needs the trust-store bucket connection.
Lerian STA runs its audit pipeline in a dedicated worker. The publisher, consumer, and export generator support both single-tenant and multi-tenant modes; the export generator also needs its S3 bucket. The partition manager, cleanup, and verifier require multi-tenancy. Configure the enabled flags and required knobs explicitly through the AUDIT_PUBLISHER_*, AUDIT_CONSUMER_*, AUDIT_PARTITION_*, AUDIT_CLEANUP_*, AUDIT_VERIFIER_*, AUDIT_EXPORT_GENERATOR_*, and AUDIT_EXPORT_RATE_LIMIT_* families: envDefault tags are not generally materialized.