AWS Setup

regularizer
2 min readNov 19, 2018

Create an AWS instance.

Save the .pem file, cd to the folder, and do ‘ssh -i xxx.pem ubuntu@xxxx.com’. The ssh information can be found when click “connect” on the instance.

Set up Docker

sudo dpkg — configure -a
sudo apt install docker.io
sudo usermod -a -G docker $USER (https://techoverflow.net/2017/03/01/solving-docker-permission-denied-while-trying-to-connect-to-the-docker-daemon-socket/)
find $USER using whoami
log out and log in again
test using “docker run hello-world”

Change the Security Group to open a port

After set up Docker, Anaconda and Clipper on AWS. Run the Clipper deployment. Because the port for the Clipper application is 1337, create a Security Group with a Custom TCP Rule for port 1337.

Set up S3 storage

Follow Getting Started Guide to create a S3 bucket. Default configurations are fine. Upload files to the bucket.

Copy files in S3 to E2: aws s3 cp s3://bucket_name/file_path ./

But before that, need to install AWS CLI and finish configurations.

Install AWS CLI:

sudo apt-get update

sudo apt-get install awscli

Configurations:

aws config

Need to configure AWS Access Key ID, Secret Access Key, Default region name, Default output format. Follow this link to find out the information, The information can be found in IAM console.

US EAST (Ohio) is us-east-2. These location codes can be found online.

Set up clipper

conda create -n pcp_clipper pip python=3.6 #install pip and python3.6 in this environment.

conda activate pcp_clipper

pip install clipper_admin==0.3.0 (The linux instance may not install gcc. `sudo apt install -y build-essential` if `Failed building wheel for psutil`)

pip install -U cloudpickle==0.5.3 (make sure cloudpickle is the right version)

References:

Amazon EC2 not working when accessing through public IP

Configuring the AWS CLI

S3 getting started guild

--

--