...
Expand | ||
---|---|---|
| ||
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:
Once the task has been created, it can be linked to a Docker step in the pipeline. |
Expand | ||
---|---|---|
| ||
To set up an ECS Service Pipeline pipeline, create 3 pipeline steps: Build, Docker ECR Push and AWS ECS Deploy
|
AWS ECS Service Creation Help Documentation
Service Creation workflow requires setup in both Task and Pipeline. The reason for this is that Service Creation and deployment requires the latest image URL in order to deploy and that 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. The following step refers to the setup in Task.
AWS ECS Service Creation Setup - Tasks
Similar to ECS Cluster Creation, ECS Service creation templates can also be created via the Tasks tab.
...
Once this Task template is created, a pipeline can now be setup using this Task. Deployment requires the latest image URL in order to deploy and that is generated during pipeline runtime.
AWS ECS Service Creation Setup - Pipeline
To set up an ECS Service Pipeline pipeline, create 3 pipeline steps: Build, Docker ECR Push and AWS ECS Deploy.
...
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 AWS does not allow users to have 2 services with the same name, so the prefix entered in Dynamic Name Prefix field below will be used in the deploy with the run count as the name so that the name changes with every new run.
Dynamic Name Prefix - Select a unique name to be used for each service run.
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.
...