Deploy to Amazon ECS

How to deploy to ECS using Pipes (Recommended)

This option provides you with a simplified way of deploying to ECS. This approach requires less maintenance since the pipeline is maintained on your behalf. However, this option restricts the amount of control you have over the deployment.

Prerequisites

You'll need to have:

• An existing image registry such as Docker Hub or ECR. Alternatively, you can also use your own Docker registry.

• An existing AWS Elastic Container Service cluster running a service, which will be updated with the task definition in the repo.

• An AWS IAM user with programmatic access, with sufficient permissions to execute the RegisterTaskDefinition and UpdateService actions.

Steps

1. Clone AWS ECS deployment example repo

2. Configure your registry variables by going to Pipelines > Settings > Repository variables, and clicking Add.

Example:

This example uses Docker Hub variables:

• DOCKERHUB_USERNAME

• DOCKERHUB_PASSWORD

3. Add your AWS credentials by going to In Pipelines Settings > Repository variables, and clicking Add.

Example:

Amazon variables:

• AWS_ACCESS_KEY_ID

• AWS_SECRET_ACCESS_KEY

• AWS_DEFAULT_REGION

Outcome: You can now reference these variables from within the bitbucket-pipelines.yml

4. Go to your bitbucket-pipelines.yml and edit the cluster and service name to match your existing ECS cluster and service.

Example:

Outcome: Once the changes have been pushed, Pipelines builds the app, packages it to a Docker container, push to Docker Hub, and deploys the container to ECS.

Deploy to ECS using AWS CLI

This option is recommended for advanced scenarios where you need more control over the customization.

Quick start guide (recommended)

Prerequisites

You'll need to have:

• An existing image registry such as Docker Hub or ECR. Alternatively, you can also use your own Docker registry.

• An existing AWS Elastic Container Service cluster running a service, which will be updated with the task definition in the repo.

• An AWS IAM user with programmatic access, with sufficient permissions to execute the RegisterTaskDefinition and UpdateService actions.

Steps

1. Clone https://bitbucket.org/bitbucketpipelines/example-aws-ecs-deploy-no-pipe/src

2. Configure your registry variables by going to Pipelines > Settings > Repository variables, and clicking add.

3. Ensure you tick the Secured checkbox for the password.

Example:

This example uses Docker Hub variables:

• DOCKERHUB_USERNAME

• DOCKERHUB_PASSWORD

3. Add your AWS credentials by going to In Pipelines Settings > Repository variables, and clicking add.

Example:

Amazon variables:

• AWS_ACCESS_KEY_ID

• AWS_SECRET_ACCESS_KEY

• AWS_DEFAULT_REGION

Outcome: You can now reference these variables from within the bitbucket-pipelines.yml

Step-by-step guide

Prerequisites

You'll need to have:

• An existing image registry such as Docker Hub or ECR. Alternatively, you can also use your own Docker registry.

• An existing AWS Elastic Container Service cluster running a service, which will be updated with the task definition in the repo.

• An AWS IAM user with programmatic access, with sufficient permissions to execute the RegisterTaskDefinition and UpdateService actions.

• Install the deploy tools. The deployment script requires the AWS CLI, and the jq library as part of your build. If you use a different Docker image or you've created your own, ensure these packages are installed.

Steps

1. Install the AWS CLI.

Example:

In the following example, you can see an image with the installed tools.

2. Register an ECS task definition that references the newly pushed Docker image. When we register the task definition with our ECS cluster, we get back the version. We'll store this in an environment variable so we can reference it later when we update the ECS service.

Example:

3. Update the ECS Service

Example: