diff --git a/.github/workflows/aws-ecs-deploy-prod.yml b/.github/workflows/aws-ecs-deploy-prod.yml new file mode 100644 index 00000000..1ae75ae4 --- /dev/null +++ b/.github/workflows/aws-ecs-deploy-prod.yml @@ -0,0 +1,85 @@ +# This workflow will build and push a new container image to Amazon ECR, +# and then will deploy a new task definition to Amazon ECS, when there is a push to the "master" branch. +# +# To use this workflow, you will need to complete the following set-up steps: +# +# 1. Create an ECR repository to store your images. +# For example: `aws ecr create-repository --repository-name my-ecr-repo --region us-east-2`. +# Replace the value of the `ECR_REPOSITORY` environment variable in the workflow below with your repository's name. +# Replace the value of the `AWS_REGION` environment variable in the workflow below with your repository's region. +# +# 2. Create an ECS task definition, an ECS cluster, and an ECS service. +# For example, follow the Getting Started guide on the ECS console: +# https://us-east-2.console.aws.amazon.com/ecs/home?region=us-east-2#/firstRun +# Replace the value of the `ECS_SERVICE` environment variable in the workflow below with the name you set for the Amazon ECS service. +# Replace the value of the `ECS_CLUSTER` environment variable in the workflow below with the name you set for the cluster. +# +# 3. Store your ECS task definition as a JSON file in your repository. +# The format should follow the output of `aws ecs register-task-definition --generate-cli-skeleton`. +# Replace the value of the `ECS_TASK_DEFINITION` environment variable in the workflow below with the path to the JSON file. +# Replace the value of the `CONTAINER_NAME` environment variable in the workflow below with the name of the container +# in the `containerDefinitions` section of the task definition. +# Note: Use `latest` tag instead of overwriting the image id into task definition container name. This is better +# than updating multiple container definitions in a task definition. +# +# 4. Store an IAM user access key in GitHub Actions secrets named `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`. +# See the documentation for each action used below for the recommended IAM policies for this IAM user, +# and best practices on handling the access key credentials. + +name: Deploy to Amazon ECS + +on: + push: + branches: ["master"] + +env: + AWS_REGION: eu-central-1 # set this to your preferred AWS region, e.g. us-west-1 + ECR_REPOSITORY: chapter # set this to your Amazon ECR repository name + ECS_SERVICE: chapter-app-cluster-app-service-prod # set this to your Amazon ECS service name + ECS_CLUSTER: chapter-app-cluster-prod # set this to your Amazon ECS cluster name + ECS_TASK_DEFINITION: + deploy/aws/ecs-task-definition-prod.json # set this to the path to your Amazon ECS task definition + # file, e.g. .aws/task-definition.json + # containerDefinitions section of your task definition + DOCKERFILE: deploy/aws/Dockerfile.app # Container dockerfile + IMAGE_LATEST_TAG: latest # latest tag name + +permissions: + contents: read + +jobs: + deploy: + name: Deploy + runs-on: ubuntu-latest + environment: production + + steps: + - name: Checkout + uses: actions/checkout@v3 + + - name: Login to Amazon ECR + id: login-ecr + uses: aws-actions/amazon-ecr-login@v1 + + - name: Build, tag, and push image to Amazon ECR + id: build-image + env: + ECR_REGISTRY: ${{ steps.login-ecr.outputs.registry }} + IMAGE_TAG: ${{ github.sha }} + run: | + # Build a docker container and + # push it to ECR so that it can + # be deployed to ECS. + docker build -t $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG -t $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_LATEST_TAG -f $DOCKERFILE . + docker push $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG + echo "image=$ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG" >> $GITHUB_OUTPUT + docker push $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_LATEST_TAG + echo "image=$ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_LATEST_TAG" >> $GITHUB_OUTPUT + + - name: Deploy Amazon ECS task definition + uses: aws-actions/amazon-ecs-deploy-task-definition@v1 + with: + task-definition: ${{ env.ECS_TASK_DEFINITION }} + service: ${{ env.ECS_SERVICE }} + cluster: ${{ env.ECS_CLUSTER }} + wait-for-service-stability: true