What problem does it solve? Setting up AWS CI/CD pipelines involves coordinating five services with non-obvious failure modes: connections stuck in PENDING state, builds hanging silently in VPCs without NAT gateways, and cross-account deployments failing with cryptic Access Denied errors. This Skill provides the exact configurations, IAM policies, and troubleshooting steps to get pipelines working correctly. ## Core Features & Use Cases - Pipeline Orchestration: Create CodePipeline V2 pipelines with triggers, variables, execution modes (QUEUED, PARALLEL, SUPERSEDED), and manual approval gates. - Build & Deploy Configuration: Write buildspec.yml files with caching, VPC, and Docker support, plus CodeDeploy strategies including blue/green, canary, and linear for EC2, ECS, and Lambda. - Source & Package Management: Connect GitHub, GitLab, or Bitbucket via CodeConnections and set up CodeArtifact private package registries with auth tokens and cross-account access. - Use Case: You need a pipeline that builds a Docker image from a GitHub repo and deploys it to ECS with canary traffic shifting across two AWS accounts. This Skill walks you through the connection OAuth flow, the three-part cross-account setup (KMS key policy, S3 bucket policy, cross-account role), and the CodeDeploy ECS configuration. ## Quick Start Ask the assistant to create a CodePipeline V2 pipeline that builds from a GitHub repository and deploys to ECS using blue/green deployment.
