Provisioning Infrastructure on AWS

We will create 3 accounts on AWS

1. Application account: our Rails app will be initialised in this account. Docker images will be pushed to this account (Elastic Container Registry)
2. Staging account: for Rails staging environment
3. Production account: for Rails production environment

Create Application Account

After application account is created, create an IAM user with Administrator Access. Console access can be disabled.

Create Staging Account

After staging account is created, create an IAM user with Administrator Access. Console access can be disabled.

Create Production Account

After production account is created, create an IAM user with Administrator Access. Console access can be disabled.

An exmaple of IAM user

Warning

It is not a good practise to give IAM user administrator access; we should give it the least priviledge. But for now we will let Copilot do its thing, for example creating Docker repository and IAM roles. Once everything has setup, we can delete the IAM users in staging and production. As for the IAM user in application account, we can use Access Analyzer to give it the least priviledge.

Create AWS Named Profiles

Now you've created 3 IAM users. Add their credentials to ~/.aws/credentials and ~/.aws/config on your local

~/.aws/credentials

[copilot.application]
aws_access_key_id=AKIUJFHFJDFKFUBHUE88
aws_secret_access_key=+Wv3oDIUJSDHCNVBOLQKDIFUDIIIUDIKBK+vUmqc

[copilot.staging]
aws_access_key_id=AKLKMDJCHUUDHIDIUE67
aws_secret_access_key=eUdT8KIMDJFIOUJSHEHWEJQAZSDSEJFJFMFbyUrl

[copilot.prod]
aws_access_key_id=AKIJUYHNBGTRFVBVC904
aws_secret_access_key=oWzVIUEURHFDKDJFKUHXBCNVJFJIIFKDFIUxxfqj

Info

These are not real credentials

~/.aws/config

[profile copilot.application]
region=us-west-2

[profile copilot.staging]
region=us-west-2

[profile copilot.prod]
region=us-west-2

Create Copilot App

Earlier this page, we mentioned that our app will be initialized in application account. Let's initialize the app now.

Export the application profile

export AWS_PROFILE=copilot.application

Initialize the app. We will name our app rails70

copilot app init rails70

After initialisation, run

copilot app ls

It should output

rails70

Create Environments

Staging Environment

Export the staging profile, and create the staging env

export AWS_PROFILE=copilot.staging
copilot env init
copilot env deploy --name staging

Production Environment

Export the production profile, and create the production env

export AWS_PROFILE=copilot.prod
copilot env init
copilot env deploy --name prod

After creating staging and production, run

copilot env ls

it should return

prod
staging

Create ECS Services

Now we have created production and staging environments. We're going to create webserver and worker services, so they can run in ECS cluster.

Webserver Service

export AWS_PROFILE=copilot.application
copilot svc init
Which service type best represents your service's architecture? Load Balanced Web Service
What do you want to name this service? webserver

A manifest file will be generated under copilot/webserver/manifest.yml