Before you start
What you need ready before you launch the eode stack.
AWS administrator in the target account
From River Logic
Ask your River Logic contact to invite your 12-digit AWS account ID. Once you're invited, the eode portal
(portal.eode.app) gives you:
- the Launch Stack link for the current release;
- your sign-in details (client ID, sign-in domain, API key, webhook secret), after your company login is connected. See Sign-in and access.
In your AWS account
| You need | Why |
|---|---|
| An administrator role that can create IAM roles, VPCs, EKS, RDS, ElastiCache and EFS | The stack creates all of them |
| On-demand vCPU quota of at least 32 in the region (the standard instance families) | New accounts start at 5; ask AWS Support to raise it before you launch |
Two hostnames you control, for example eode.example.com and eode-mcp.example.com | The web app and the MCP endpoint |
| An Anthropic API key from your own Anthropic account, with a spend limit set there | Every conversation with RIA uses it |
Decide before you launch
- New VPC or existing? The stack can create a VPC, or install into yours: two or three private subnets with outbound internet access.
- Certificates: automatic (Let's Encrypt, which needs your hostnames to reach the stack from the internet) or your own certificate in AWS Certificate Manager.
- Size: each active user's engine needs about half a CPU, so one default engine node serves about 14 users at once. Raise EngineNodeCount for more. See Settings.