Contents:

• Why Clean Up?
• Delete ECS Services and Cluster
• Delete Load Balancer and Target Groups
• Delete ECR Repositories
• Delete VPC and Networking Components
• Delete CodePipeline, CodeBuild, and CodeCommit
• Delete IAM User and Permissions
• Check Remaining Costs

Why Clean Up?

This workshop has created several AWS resources that can continue to incur costs if not removed, such as ECS Clusters, ALBs, NAT Gateways, ECR Storage, and CloudWatch Logs.
Cleaning up ensures:

• Avoiding unexpected charges.
• Keeping your AWS environment tidy.
• Preventing resource exposure or misuse.

Delete ECS Services and Cluster

1. Open Amazon ECS Console → Select Cluster: fargate-workshop-cluster.
2. Stop all Services:
   • Select each service → Delete service → Confirm.
3. Wait for all Tasks to stop.
4. Delete the Cluster: Delete cluster.

Delete Load Balancer and Target Groups

1. Open EC2 Console → Load Balancers.
2. Select the ALB created (e.g., fargate-workshop-alb) → Delete.
3. Open Target Groups → Delete groups linked to the ALB.

Delete ECR Repositories

1. Open Amazon ECR Console → Repositories.
2. Select the repository (e.g., fargate-microservices) → Delete.
3. Select Force delete if images are present inside.

Delete VPC and Networking Components

Only delete if it was created specifically for this workshop. Do not delete the default VPC.

1. Open VPC Console → Your VPCs → Select the workshop VPC → Delete.
2. Remove related Subnets, Route Tables, Internet Gateway, NAT Gateway, and Security Groups.

Delete CodePipeline, CodeBuild, and CodeCommit

1. CodePipeline: Open the console → Select the pipeline → Delete.
2. CodeBuild: Remove unused build projects.
3. CodeCommit: Delete the workshop repository if code retention is not needed.

Delete IAM User and Permissions

1. Open IAM Console → Users → Select fargate-workshop-user.
2. Remove Access Keys.
3. Delete the user completely.

Check Remaining Costs

1. Open Billing & Cost Management.
2. Select Cost Explorer to review daily costs.
3. Ensure no services are running unexpectedly.

Expected Outcome:
All AWS resources created during the workshop are deleted, your AWS account is back to a clean state, and no further charges are incurred.