Settings
Every field on the stack form, and how to change one after install.
Every setting is a field on the stack. This page uses each field's name, as shown on the stack's Parameters tab; the form shows a plain label beside it. To change one, select the stack in CloudFormation, choose Update, keep Use current template, change the field and submit.
Changing Release, a hostname, a sign-in ID, a certificate field, TelemetryEndpoint, DataConnectionDenyCidrs, AppReplicas, EngineMemoryClasses or RestartToken reruns the installer: it snapshots the database, then restarts the web app and the MCP endpoint. Plan those changes for a quiet time. Other fields change the AWS resource directly, without a snapshot or a restart.
Hostnames and certificates
| Field | Default | What it does |
|---|---|---|
| AppHost | required | The web app's hostname |
| McpHost | empty | The MCP endpoint's hostname. Empty means no MCP endpoint |
| TlsMode | LetsEncrypt | LetsEncrypt for automatic certificates, or AcmCertificate for your own. One ACM certificate must cover both hostnames |
| AcmeEmail / AcmCertificateArn | empty | Whichever TlsMode needs |
Sign-in and LLM
| Field | What it does |
|---|---|
| SignInClientId, SignInDomain, SignInApiKey, SignInWebhookSecret | Your sign-in connection, from your River Logic contact (Sign-in and access) |
| LlmApiKey | Your Anthropic API key. To rotate it, change it here and change RestartToken in the same update |
Network
| Field | Default | What it does |
|---|---|---|
| VpcMode | CreateNew | UseExisting installs into your VPC (ExistingVpcId, ExistingVpcCidr, ExistingPrivateSubnetIds) |
| VpcCidr, AzCount, NatGateways | 10.40.0.0/16, 2, Single | The shape of a new VPC. With an existing VPC, AzCount must equal the number of subnets |
| ClusterPublicEndpoint, ClusterPublicEndpointCidrs | false, 0.0.0.0/0 | Whether the cluster's API is reachable from outside the VPC, and from where. If you turn it on, narrow the ranges |
| DataConnectionDenyCidrs | the VPC | Internal ranges a user's data connection may never reach |
Capacity
| Field | Default | What it does |
|---|---|---|
| GeneralInstanceType × GeneralNodeCount | m6i.xlarge × 2 | Nodes for the web app and MCP endpoint |
| EngineInstanceType, EngineNodeCount | r6i.2xlarge, 1 | Nodes for the optimization engines. Each active user's engine needs about half a CPU. The engine node group stays at EngineNodeCount; it doesn't scale by itself. (EngineNodeMax is reserved for that) |
| EngineMemoryClasses | 12Gi,24Gi,48Gi | The engine sizes eode may use. Each must fit on EngineInstanceType |
| AppReplicas | 2 | Copies of the web app |
| DbInstanceClass, DbStorageGiB, DbMultiAz, DbBackupDays | db.r6g.large, 100, true, 14 | The PostgreSQL database |
| RedisNodeType | cache.r6g.large | The Redis cache |
| KubernetesVersion | 1.34 | The EKS version, set at install. Changing it later moves the control plane only, so ask us before you change it |
Security and operations
| Field | Default | What it does |
|---|---|---|
| KmsKeyArn | empty | Your KMS key for the cluster's secrets, the database, cache, file storage and Secrets Manager |
| AdminPrincipalArn | empty | An IAM role or user to make a cluster administrator. Set it: without it, nobody in your account can use kubectl on the cluster |
| TelemetryEndpoint | empty | Reserved for a later release. Leave it empty |
| RestartToken | empty | Change it to any new value to restart eode, for example after rotating a secret |
Release, ArtifactAccount, ArtifactRegion and TemplateBaseUrl are set by the release. Change Release only to upgrade (Upgrades), and leave the other three as they are.
Secrets
The stack keeps every secret in AWS Secrets Manager under eode/, generates the ones nobody needs to know (database
and cache passwords, encryption keys), and never puts a secret in a template or a log. To rotate the LLM key or the
sign-in fields, change them on the stack together with RestartToken. To rotate a database or cache login, ask us:
those are tied to the database and cache themselves. Don't rotate eode/data-connections: saved data-connection
credentials can't be read after it changes.
Every secret, its format and who can read it: Reference: Secrets.