Regarding the error itself, it seems to be some sort of permission issue - can you please show the Response details for the two auth.create_credentials calls shown in the list?
Also, are you using HTTP or HTTPS?

SquareFish25 I'm not sure from your last message if you're still experiencing any issues... 🤔

Hi SuccessfulKoala55 ,
Thank you for your help. It is working now after I removed the ports for ElasticSearch, Redis, and MongoDB. I am using HTTP at the moment because HTTPS doesn't work, how should I change the rules? How can I restart the Trains Server on EC2?

Sure. BTW, I also put the screenshot of the config for the security group (I understand it should not be open to the whole world, I'm just setting up first, and someone else will help me to update the rules later).

Hi SquareFish25 ,

I am using HTTP at the moment because HTTPS doesn't work, how should I change the rules?

You can setup the AWS ELB to handle that, if you'd like. See https://allegro.ai/docs/deploying_trains/trains_server_config/#sub-domain-configuration

How can I restart the Trains Server on EC2?

For what purpose? If you want to reload configuration etc., you can simply do docker-compose down and than docker-compose up from the folder containing the docker-compose.yml .
You can also restart the EC2 instance while the docker-compose is running, but it takes longer and has the same effect 😄

Hi SquareFish25 ,
Can you share a screenshot of your browser's developer tools panel, in the Network section?

Hi SquareFish25 , regarding the security group configuration:
The ports for ElasticSearch, Redis and MongoDB should not be exposed to the whole world. In fact, you can actually even configure docker-compose so they won't be exposed outside of the docker network (see https://allegro.ai/docs/deploying_trains/trains_server_config/#network-and-security )
Also, note that port 8008 is for API and 8081 is for the fileserver (just so your descriptions there will be correct)

It is working now, thank you very much for your help.