The Odigos VM Agent is available as part of Odigos Pro. For access and licensing details,
contact us.
You need the
odigos-ecs-proxy image in addition to the agent image you
already run. Mirror it the same way as in
System Requirements.Switch
1
Deploy the proxy
Follow Install: Multi Node steps
3–5 (stable address, proxy task definition, proxy service). Prefer the
internal NLB; a pinned instance is test/dev only.Do not create a second agent service — keep the daemon you already have.
2
Re-point the agents
In the agent task definition, change
ODIGOS_DEFAULT_CONFIG’s endpoint to
the proxy’s host:4321 and add ODIGOS_ECS_BEHIND_PROXY=true. Register
the new revision.The endpoint alone cannot tell a proxy from Central. Without
ODIGOS_ECS_BEHIND_PROXY=true, every agent still registers under the
cluster name and the coverage check reports all instances as uncovered. See
platform naming.3
Roll the daemon
4
Verify
Use Install: Multi Node, Step 8:
agents connected to the proxy,
/healthz lists every node, and Central
shows one platform for the cluster.config.yaml
take precedence
over ODIGOS_DEFAULT_CONFIG. After the first boot behind the proxy, change the
endpoint through Central or odictl if a node still points at Central.
Switch back to single node
The same flow in reverse:- Point
ODIGOS_DEFAULT_CONFIG’s endpoint back at Central. - Remove
ODIGOS_ECS_BEHIND_PROXY(or set it tofalse). - Register a new revision and
update-service --force-new-deployment. - Delete the proxy service.
Next steps
Install: Multi Node
Full Agent + Proxy install if you are starting from scratch.
Configuration Reference
ODIGOS_ECS_BEHIND_PROXY and the proxy environment variables.