Docker compose deployment on public server

[oware]

Hi,
Running the eoAPI docker-compose locally works seamlessly while a bit troublesome if one switches to a public cloud server.
Is there a recommended way to configure the public IP on the eoAPI docker-compose file ?
Replacing 127.0.0.1 with the IP doesn’t seem to work.

eoAPI$ docker compose up -d
WARN[0000] The "AWS_ACCESS_KEY_ID" variable is not set. Defaulting to a blank string.
WARN[0000] The "AWS_SECRET_ACCESS_KEY" variable is not set. Defaulting to a blank string.
[+] Running 4/5
✔ Container eoapi-database-1 Started 0.5s
✔ Container eoapi-tipg-1 Started 1.6s
✔ Container eoapi-stac-fastapi-1 Started 1.6s
✔ Container eoapi-titiler-pgstac-1 Started 1.5s
⠙ Container eoapi-stac-browser-1 Starting 0.1s
Error response from daemon: driver failed programming external connectivity on endpoint eoapi-stac-browser-1 (01f592a2dd5578f556496ab0c262c16183c7a3f7ee624958db3ed81875b2ca9d): failed to bind port 34.x.x.x:8085/tcp: Error starting userland proxy: listen tcp4 34.x.x.x:8085: bind: cannot assign requested address

[hrodmn]

Hi @oware - thanks for opening this discussion! Running eoAPI using this docker-compose.yml on an EC2 instance was the first way I ever deployed eoAPI. I haven't done this in a while but here is where I would start.

Set this environment variable before you start the docker network:

export MY_DOCKER_IP=0.0.0.0

You will also need to be sure your EC2 Instance's security group allows inbound traffic for TCP on ports 8081, 8082, 8083, and 8085.

You may also need to update some of the STAC browser configuration settings with the public IP address instead of the default 0.0.0.0.

Deploying this docker network is a great place to start for a POC deployment but if you ever want something a bit more reliable you can deploy the mostly serverless eoAPI stack following the eoapi-template repo. If you deploy a small RDS instance (e.g. t3.micro) it should cost less than $30USD/month to run.

I hope that helps, let us know what you wind up doing!