Network and security
What reaches your eode install, what it calls out to, and what stays in your account.
What stays in your account
Your models, data, results, conversation history and uploaded files are in your database and file storage. Your secrets are in your Secrets Manager. River Logic has no credentials or role in your AWS account.
Two things involve River Logic:
- Sign-in runs through River Logic's hosted sign-in service (WorkOS) today. It holds your users' identities and organization memberships, and your company login connects to it. See Sign-in and access.
- Images and the install template come from River Logic's registry and storage. The installer runs that template in your account with the permissions it needs to create the stack, and the pulls are visible to River Logic.
Feedback filing, support handoff and usage telemetry to River Logic are switched off in a self-hosted install, and so is telemetry from the LLM client inside the app.
What RIA sends your LLM provider
RIA, eode's assistant, sends each conversation to your LLM provider with your API key. A request can contain:
- your question and the conversation so far;
- eode's own instructions and reference knowledge about modeling;
- the text of any document you attach to the conversation;
- a profile and a few sample rows of each sheet RIA reads, and the data it looks up while working;
- the query and solve results it uses in its answer.
RIA's web searches also run at your LLM provider. Anything RIA reads while it answers is sent to your LLM provider.
Inbound
| Hostname | Port | Who calls it |
|---|---|---|
APP_HOST | 443 | Your users' browsers, and the sign-in service's webhooks |
MCP_HOST | 443 | Your MCP clients. A hosted assistant (for example a custom connector in Claude) calls from its vendor's cloud |
| Both | 80 | Redirects to HTTPS, and the Let's Encrypt challenge with automatic certificates |
Both are served by one internet-facing load balancer that the stack creates. The optimization engines are never reachable from outside the cluster.
Outbound
| Endpoint | Needed for |
|---|---|
api.anthropic.com | Every conversation with RIA, with your own key. RIA's web search also runs at Anthropic |
api.workos.com and your sign-in domain | Sign-in. Your users' browsers reach the sign-in domain too |
River Logic's image registry and template storage (Amazon ECR and S3 in us-east-1) | eode's images: at install, at upgrade, and whenever a new engine starts on a node that doesn't have the image yet. The installer also reads the release's templates and starter models from there |
fonts.googleapis.com, fonts.gstatic.com, api.fontshare.com and its font CDN | Your users' browsers, for the web app's typefaces |
| AWS APIs in your region (STS, Secrets Manager, ECR, EKS, S3, CloudWatch Logs, RDS, KMS) | The cluster, its secrets, images and logs |
Public download sites: dl.k8s.io, get.helm.sh, charts.jetstack.io, kubernetes-sigs.github.io, aws.github.io, Docker Hub, and the Amazon Linux package mirrors | The installer, each time it runs |
Public image registries: Docker Hub, quay.io, registry.k8s.io, public.ecr.aws | The add-ons the installer sets up (gateway, certificates, secrets driver), whenever their pods start on a new node |
Let's Encrypt (acme-v02.api.letsencrypt.org) | Only with automatic certificates |
| A data source a user connects | Only when a user adds a data connection. Only TCP 443 outside your VPC is allowed |
There is no offline mode: eode needs your LLM provider and the sign-in service. The sign-in service must also reach
APP_HOST from the internet for its webhooks. Outbound traffic through an HTTP proxy isn't supported yet.
Inside the cluster
- Network policies allow only the web app and the MCP endpoint to reach the engines, and keep the engines off the internet.
- The web app and the MCP endpoint share one AWS role for reading secrets; the database migration job has its own.
- A user's data connections can't reach the internal ranges in DataConnectionDenyCidrs.
The full lists, the network policies and the ranges are in Reference: Network. The software inside each image is on Reference: Images.