You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »

Overview

Currently, the way Docker containers are deployed on AWS is basically having them run on an EC2 instance (with public IP 3.232.82.82). This means that each service occupies a unique port on the machine. Below is a list of running services and the ports they are using.

ServicePort
Backend offline5000

Procedure

First, download the key pair file DIAPER-test-key.pem and run

chmod 400 /path/to/DIAPER-test-key.pem

Then, you can ssh into the EC2 instance using

ssh -i /path/to/DIAPER-test-key.pem ec2-user@3.232.82.82

 

Then, pull your Docker image and other relevant file from GitHub. Once pulled, navigate to your project folder and run the Docker as you would do locally. To keep your service from blocking the console, you should run your Docker in detached mode. Alternatively, you can first enter ctrl-z to suspend the service and then run the following commands

bg
disown -h

Doing this also makes your service run in background.

 

Now you can log out and the service will continue running on the EC2 instance.

  • No labels