AWS ECS Service Creation workflow requires setup in both Tasks and Pipeline. Service Creation and deployment require the latest image URL in order to deploy. This is generated during pipeline runtime. The workflow is separated into two parts where the user enters certain static information in the Tasks page and then links the task to the respective Docker step in the pipeline.

Task Setup Instructions:

1. Select Create AWS ECS Service from the Type drop down. Once this has been selected, the following values will be fetched for selection:

   • AWS Tool - Select an established AWS tool from the Tool Registry.

   • Required Compatibility - Select Fargate or EC2.

   • Cluster Name - Select a Cluster Name fetched from the AWS portal.

   • Existing VPC - Select an existing VPC from the list of values fetched from the AWS portal.

   • Desired Count - Select the amount of deployments desired.

   • Load Balancer ARN - Select a Load Balancer ARN from the list of values fetched from the AWS portal.

   • Execution Role ARN - Select a Load Balancer ARN from the list of values fetched from the AWS portal.

   • Subnets - Select 2 subnets from list of values fetched from the AWS portal.

2. Select Save to create a template.

Once the task has been created, it can be linked to a Docker step in the pipeline.

To set up an ECS Service Pipeline pipeline, create 3 pipeline steps: Build, Docker ECR Push and AWS ECS Deploy

• Build

• Docker ECR Push - Create a new pipeline step

  • Initial Setup: Create new pipeline step using Docker ECR Push as Tool and Save

  • Step Configuration:

    • Jenkins Tool - Select a Jenkins tool from the Tool Registry.

    • Jenkins Job - DOCKER PUSH (must be created in selected Jenkins Tool)

    • AWS Credentials - Select an AWS account configured in Opsera Tool Registry

    • Build Step Info - Build

    • ECR Repository - Use an existing Repository or create a new one.

• AWS ECS Deploy - Create new pipeline step using AWS ECS Deploy as Tool.

  • Docker Step - Create a name.

  • Service Task - Fetched from AWS ECS Service Tasks

  • Generate Dynamic Service Name toggle - currently not working, when it works the port name will not have to be changed for every pipeline run.

  • Dynamic Name Prefix

  • Service Name Example - User has option to dynamically generate service names on runtime as AWS does not allow two services to have the same name. The user can give a prefix to the service and the pipeline will generate a unique service name with the prefix and the run count when the pipeline runs.

  • Service Container Port - This is the location where service will be deployed. _{*currently, service port must be changed for every pipeline run.}