-
Hi, eoAPI$ docker compose up -d |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
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 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! |
Beta Was this translation helpful? Give feedback.
-
Hi @hrodmn thanks alot for the detailed response, updating the stac browser configuration setting resolved the issue. I will ensure the environment variable is set too. Thanks. |
Beta Was this translation helpful? Give feedback.
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…