Install on AWS
Launch the eode stack from one CloudFormation form, point your DNS, and sign in.
What you'll do: fill one form in the AWS console, wait while the stack builds, then create two DNS records.
Open the Launch Stack link
Sign in to the AWS console in your invited account and region, then open the Launch Stack link from the eode portal. CloudFormation opens the stack form with the release already filled in.
Fill in the form
The form is grouped. Fill in these fields:
| Group | Field on the form | What to enter |
|---|---|---|
| Your hostnames | Web app hostname, MCP endpoint hostname | Your two hostnames. Leave the MCP one blank if you don't use MCP |
| Your hostnames | Certificates | Leave LetsEncrypt and fill Email for Let's Encrypt notices, or pick AcmCertificate and fill ACM certificate ARN |
| Sign-in | Sign-in client ID, domain, API key, webhook secret | The four values River Logic gives you |
| LLM provider | Your Anthropic API key | Your key |
Everything else has a working default. To install into your own VPC, set Network to UseExisting, fill in
the VPC ID, its CIDR and one private subnet per availability zone, and set AzCount to the number of subnets.
Every field is described on Settings.
Create the stack
Tick the acknowledgements for IAM resources and nested stacks, then Submit. The stack builds the network, the cluster, the database, cache and file storage, stores your secrets in Secrets Manager, and installs eode. It takes about 40 minutes.
Point your DNS
When the stack shows CREATE_COMPLETE, open its Outputs tab and create a CNAME record for each hostname pointing at GatewayAddress. With automatic certificates, the first certificate is issued a few minutes after the records resolve.
Sign in
Open https://APP_HOST and sign in with your company login. The starter models are already in the library.
Check it worked
- The stack is CREATE_COMPLETE. The installer only reports success after eode answers its health check.
https://APP_HOSTshows the sign-in page with a valid certificate.- MCP: connect a client to
https://MCP_HOST/mcp. See Sign-in and access.
If something's wrong
- The stack rolled back: the failed resource's Status reason says why. Installer errors are in CloudWatch Logs,
log group
/aws/codebuild/<cluster>-installer. Fix the cause and launch again. - Certificate error: the DNS records don't resolve to GatewayAddress yet, or the hostnames aren't reachable from the internet (use your own ACM certificate instead).
- Sign-in fails: send the hostname you used to River Logic through the eode portal; it has to be registered for your sign-in connection.
Related
- Upgrades
- Operations: monitoring, backups, support, uninstall.