Deployment of Admin Backend to Fargate/ECS

Feature(s) impacted

Attempting to Deploy Docker Container to ECS/Fargate

Observed behavior

We couldnt find any step by step HowTo’s

Expected behavior

Can you please point us in the direction of any documentation as we are struggling :slight_smile:

Failure Logs



  • Project name: On Air Details
  • Team name: Operations
  • Environment name: development
  • Agent (forest package) name & version: Latest
  • Database type: MSSQL 15.0
  • Recent changes made on your end if any: None

Hello @David_Martin,

Do you have any problems related to Forest Admin regarding this deployment?

What’s specific to Forest Admin regarding your deployment, that is not covered by the documentation of ECS/Fargate?

We found documentation regarding EC2, but could not find any documentation around EC2. The Admin console returns “agent unreachable” even though we can see in ECS that it has started.

We uploaded the docker image to ECS, created a task definition and ran up the service.

We got that mounted successfully as a standalone server.

Should we have instead done the “deploy to production” steps instead of just copying the initial image we created?


You can easily test if your server is correctly running by reaching [yourAgentUrl]/forest in your browser. If you get a generic JSON response, then the agent is running and everything is correctly configured.

If you get an error or a response from your reverse proxy, then it means that something is not correctly configured between the proxy and the agent, or that the agent did not start, or it crashed because of an error.

1 Like

I get this

{“error”:null,“message”:“Agent is running”}

Ok, your agent seems to be running.

Can you explain where you get the error “Agent unreachable”? Do you have more info about the error? Some console and network logs could help.