Task 2/2:
The DevOps team is working on automating the deployment of a containerized Flask application using AWS services like ECR, CodePipeline, ECS and a Load Balancer. The goal of this task is to set up a continuous delivery pipeline that builds a Docker image, pushes it to ECR, and deploys the application to an ECS cluster.
Create an ECR repository named devops-ecr-repo-t2q3 for storing Docker images.
Create a private S3 bucket named devops-app-5977-t2q3 with versioning enabled, to store the Python Flask application’s source code, the source code is available on AWS client host under /root/pyapp.zip. Upload /root/pyapp.zip file to the bucket.
Create an ECS cluster named devops-ecs-cluster-t2q3, a service named devops-ecs-service-t2q3 and a task definition named devops-ecs-task-t2q3. Also configure it to use an application load balancer named devops-ecs-alb-t2q3 along with a target group named devops-ecs-tg-t2q3 so that the application can be accessible via the Load Balancer’s DNS URL.
Set up a CodeBuild named devops-build-project-t2q3 and a CodePipeline named devops-pipeline-t2q3 with three stages: Source, Build, and Deploy. The Source stage must pull the source code from s3 bucket, the Build stage must build the Docker image and push it to the ECR repo, and the Deploy stage must deploy the newly built image to the ECS cluster.
i checked everything worked, but validation failed with:
ECS service ‘devops-ecs-service’ is not active or does not exist.
so it seams it tried to validate on wrong service name
