Combine CloudFormation, ECS, ECR, S3 and IAM skills to deliver and operate a container application. Three independent challenges ask you to prove actual application behavior, preserve permission boundaries and remove only the resources you own.
What You Will Learn
- Deliver an approved immutable release from a supplied infrastructure template
- Distinguish a completed stack update from a healthy current deployment
- Diagnose a release with task revisions, target health, metrics and application logs
- Restore the approved release while preserving the original stack and configuration
- Rebuild staging with its own configuration and task role while keeping development unchanged
- Confirm real HTTP responses, scoped access and bounded resource cleanup
Who This Course Is For
Complete AWS Containers for Beginners and AWS CloudFormation for Beginners first. You should already understand ECS services, task and execution roles, ECR images, ALB health checks, template parameters, stack updates and deletion. PC02 also uses the metric and log basics taught in AWS Monitoring and Auditing for Beginners. The three projects are independent; none requires resources created by another project.
Learning environment: Use Terminal for ordinary AWS CLI commands and AWS View to inspect stack resources, current tasks, target health and actual application requests. Application code, immutable images, network, ALB, role, secret and log fixtures are supplied. Each challenge starts in a fresh browser-based LabEx VM with prepared tools and a connection. No personal AWS account, access keys or screenshot submission is required.
Frequently Asked Questions
Do I need to build an application or a CI/CD pipeline?
The application and releases are supplied. Focus on deployment, recovery and environment boundaries using previously taught AWS commands.
Does a responding application prove recovery?
An older healthy task may still answer during an incomplete release. Inspect the current task definition, actual image, target health and logs; confirm that previous tasks no longer run.
What must remain after cleanup?
Remove only the application resources named by the challenge. Preserve supplied fixtures and reference resources. In the environment challenge, development must keep its original stack, task and configuration when staging is removed.
