Standardize AWS CDK workflows with stack design, construct selection, and pre-deploy diff review.
npx skills add https://github.com/eric-sabe/engsys --skill iac-cdk
Please help me install this Agent Skill. Skill: iac-cdk Source: https://github.com/eric-sabe/engsys/tree/main/stacks/iac/cdk/skills/iac-cdk Command: npx skills add https://github.com/eric-sabe/engsys --skill iac-cdk
This Skill eliminates the common, costly pitfalls of unmanaged AWS CDK workflows, including inconsistent stack design, skipped deployment reviews, and unsafe infrastructure-as-code practices that lead to failed deployments, permanent data loss, or critical security misconfigurations.
Invoke this Skill when working on CDK code to validate your stack structure, construct choices, and pre-deploy diff before applying changes to AWS.
High-intent search queries and answers about installing and using this skill.
To prevent data loss, AWS CDK stack structure should separate stateful database resources from compute stacks by lifecycle. This isolation limits blast radius so routine application redeploys cannot trigger CloudFormation deletion of production data.
The recommended AWS CDK deployment workflow is the synth → diff → deploy flow with mandatory security delta review. This enforces pre-deploy validation checks and destructive change detection before applying infrastructure-as-code changes to AWS.
AWS CDK construct selection between L1, L2, and L3 depends on abstraction needs and least-privilege IAM grant requirements. Using higher-level constructs enforces best practices, while L1 constructs provide direct CloudFormation mapping.
AWS CDK deployments fail with ROLLBACK_COMPLETE status when CloudFormation stack updates encounter errors during resource creation. Troubleshooting requires actionable steps to resolve configuration drift, cross-stack reference deadlocks, or resource dependency issues.
Yes, AWS CDK supports multi-tier applications by enforcing lifecycle-aligned stack separation across network, data, and compute layers. This standardized bin/ and lib/ layout limits blast radius and avoids hitting CloudFormation's 500-resource limit.
The best way to review IAM changes is enforcing strict adherence to the CDK synth → diff → deploy flow with mandatory security delta review. This pre-deploy validation catches least-privilege violations before any production deployment.
david-2814Automate AWS CDK project initialization, synthesis, and deployment.
jay6697117Automate infrastructure provisioning and deployment workflows across AWS, GCP, or Azure.
pantheon-orgCompares deployed CloudFormation templates with local CDK-synthesized ones to detect drift.
jeremylongshoreGenerate production-ready Infrastructure as Code configurations for Terraform, CloudFormation, Pulumi, ARM, and CDK.
