cdk-deployment-rules

Enforces CDK-only governance rules for AWS production deployments and drift remediation workflows.

2|Updated May 10, 2026
One-click install
npx skills add https://github.com/freedomw1987/tree_monstor --skill cdk-deployment-rules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cdk-deployment-rules
Source: https://github.com/freedomw1987/tree_monstor/tree/main/skills/devops/cdk-deployment-rules
Command: npx skills add https://github.com/freedomw1987/tree_monstor --skill cdk-deployment-rules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual CLI modifications to AWS production resources cause untracked infrastructure drift, leading to failed CDK deployments, unreproducible environments, and difficulty auditing change history. This Skill eliminates that risk by enforcing strict CDK-only governance for all production infrastructure changes.

Core Features & Use Cases

  • CDK-Only Enforcement: Clear rules and forbidden CLI commands to prevent accidental manual resource creation or modification in production AWS environments.
  • Deployment Troubleshooting: Step-by-step guidance for resolving common CDK, CloudFormation, ECS Fargate, and CodeBuild deployment failures, including stack deletion issues, security group dependency errors, and ECS service startup failures.
  • CI/CD Optimization: Best practices for CodeBuild pipeline configuration, conditional CDK deploys, Docker layer caching, and CloudFront cache invalidation to speed up and stabilize deployment workflows.
  • Drift Remediation: Processes for identifying and cleaning up orphaned CLI-created resources that are not managed by CDK stacks.

Quick Start

Use this skill to review your planned AWS infrastructure changes and confirm they comply with CDK-only deployment rules to avoid production drift and deployment failures.

Frequently Asked Questions about cdk-deployment-rules

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent AWS infrastructure drift from manual CLI modifications in production?

To prevent AWS infrastructure drift, enforce CDK-only deployment governance rules that forbid unauthorized manual CLI resource modifications, ensuring all production infrastructure changes remain trackable and reproducible through CDK stacks.

How do I troubleshoot ECS Fargate deployment failures caused by CloudFormation stack issues?

To troubleshoot ECS Fargate deployment failures, follow step-by-step guidance for resolving CloudFormation stack deletion issues, security group dependency errors, and ECS service startup failures that commonly block your CDK deployment workflows.

What is the best way to clean up orphaned AWS resources created manually outside of CDK?

The best way to clean up orphaned AWS resources is to follow a structured drift remediation process that identifies and removes untracked CLI-created resources not managed by your CDK stacks, restoring environment synchronization.

How can I optimize AWS CodeBuild CI/CD pipelines for faster CDK deployments?

To optimize AWS CodeBuild CI/CD pipelines for CDK deployments, apply best practices for pipeline configuration, conditional deploys, Docker layer caching, and CloudFront cache invalidation to stabilize and accelerate your workflows.

Why do my CDK deployments fail after unauthorized manual updates to production AWS resources?

CDK deployments fail after manual updates because unauthorized CLI modifications cause infrastructure drift, creating state conflicts between the actual AWS resources and your CDK-defined infrastructure-as-code templates.