River Logiceode docs

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

FieldDefaultWhat it does
AppHostrequiredThe web app's hostname
McpHostemptyThe MCP endpoint's hostname. Empty means no MCP endpoint
TlsModeLetsEncryptLetsEncrypt for automatic certificates, or AcmCertificate for your own. One ACM certificate must cover both hostnames
AcmeEmail / AcmCertificateArnemptyWhichever TlsMode needs

Sign-in and LLM

FieldWhat it does
SignInClientId, SignInDomain, SignInApiKey, SignInWebhookSecretYour sign-in connection, from your River Logic contact (Sign-in and access)
LlmApiKeyYour Anthropic API key. To rotate it, change it here and change RestartToken in the same update

Network

FieldDefaultWhat it does
VpcModeCreateNewUseExisting installs into your VPC (ExistingVpcId, ExistingVpcCidr, ExistingPrivateSubnetIds)
VpcCidr, AzCount, NatGateways10.40.0.0/16, 2, SingleThe shape of a new VPC. With an existing VPC, AzCount must equal the number of subnets
ClusterPublicEndpoint, ClusterPublicEndpointCidrsfalse, 0.0.0.0/0Whether the cluster's API is reachable from outside the VPC, and from where. If you turn it on, narrow the ranges
DataConnectionDenyCidrsthe VPCInternal ranges a user's data connection may never reach

Capacity

FieldDefaultWhat it does
GeneralInstanceType × GeneralNodeCountm6i.xlarge × 2Nodes for the web app and MCP endpoint
EngineInstanceType, EngineNodeCountr6i.2xlarge, 1Nodes 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)
EngineMemoryClasses12Gi,24Gi,48GiThe engine sizes eode may use. Each must fit on EngineInstanceType
AppReplicas2Copies of the web app
DbInstanceClass, DbStorageGiB, DbMultiAz, DbBackupDaysdb.r6g.large, 100, true, 14The PostgreSQL database
RedisNodeTypecache.r6g.largeThe Redis cache
KubernetesVersion1.34The EKS version, set at install. Changing it later moves the control plane only, so ask us before you change it

Security and operations

FieldDefaultWhat it does
KmsKeyArnemptyYour KMS key for the cluster's secrets, the database, cache, file storage and Secrets Manager
AdminPrincipalArnemptyAn IAM role or user to make a cluster administrator. Set it: without it, nobody in your account can use kubectl on the cluster
TelemetryEndpointemptyReserved for a later release. Leave it empty
RestartTokenemptyChange 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.

On this page