What problem does it solve? Rolling out a new AMI or CIS hardening fix across an EC2-backed ECS cluster risks breaking the main workload if the new image is untested. This Skill plans and validates a canary lane inside one ECS cluster so a new AMI can be calibrated on isolated capacity before any wider rollout. ## Core Features & Use Cases - Lane Validation: Confirms the canary ASG joins the same cluster and that the canary node is EC2-healthy, SSM-online, Docker-healthy, and ECS-agent-healthy. - Placement Isolation: Verifies the canary service is pinned to the canary lane via capacity providers and placement constraints so the main service never lands on the new AMI by default. - Evidence Capture: The check-lane.sh script collects cluster, service, container-instance, EC2, AMI, and ASG data into a timestamped evidence directory with rollback notes. - Use Case: Before a production window, run the lane check to confirm stable and canary services are isolated, capture before/after service counts, and freeze rollback steps (stop scheduling, drain tasks, scale canary ASG to zero). ## Quick Start Ask the agent to validate the mixed-AMI canary lane for your ECS cluster by providing the cluster name, AWS profile, region, and the stable and canary service names.
