River Logiceode docs
Reference

Secrets

Every secret eode uses: its name in Secrets Manager, its format, and who creates it.

Every secret lives in AWS Secrets Manager under eode/, as a JSON object. The secrets driver syncs them into the cluster. The secret fields on the stack form (Sign-in API key, Sign-in webhook secret, Your Anthropic API key) are hidden on the stack's Parameters tab and go straight to Secrets Manager; no secret is written to a template or a log. With Install with Helm, you create these secrets yourself.

SecretHoldsSet by
eode/dbApp database login (url)The stack
eode/db-ownerOwner database login (url), migration job onlyThe stack
eode/cacheRedis login (url)The stack
eode/llmLLM API key (apiKey)You: LlmApiKey
eode/signinapiKey, webhookSecretYou: sign-in fields, from River Logic
eode/signin-cookieSession cookie key (cookieSecret)The stack, once
eode/data-connectionsData-connection encryption key (key)The stack, once
eode/probeHealth-probe token (token)The stack
eode/db-owner-credentialsDatabase owner user name and password, the source of eode/db-ownerThe stack
eode/cache-authRedis AUTH token, the source of eode/cacheThe stack

The url values look like this:

eode/db, eode/db-owner   postgresql+psycopg://USER:PASSWORD@HOST:5432/DB?sslmode=require
eode/cache               rediss://:PASSWORD@HOST:6379/0

The two keys marked "once" are 44-character Fernet keys.

Rotate a secret

SecretHow to rotate it
eode/llm, eode/signinChange LlmApiKey or the sign-in fields on the stack, and change RestartToken in the same update (Settings). Then revoke the old value where it came from
eode/signin-cookie, eode/probePut a new value in Secrets Manager, then change RestartToken
eode/db, eode/db-owner, eode/cache and their sourcesAsk us. They're tied to the database's and cache's own logins

Don't rotate eode/data-connections: saved data-connection credentials are encrypted with it and can't be read after it changes. Rotating eode/signin-cookie signs everyone out.

Who can read what

WorkloadReads
eode-app, eode-mcpeode/db, eode/cache, eode/llm, eode/signin, eode/signin-cookie, eode/data-connections, eode/probe
eode-migrateeode/db and eode/db-owner

eode-app and eode-mcp share one IAM role through EKS Pod Identity; eode-migrate has its own. Nothing else reads eode/db-owner-credentials or eode/cache-auth. With KmsKeyArn set, the secrets are encrypted with your key.

On this page