AWS CodeDeploy Management Skill
Analyze and manage AWS CodeDeploy applications, deployment groups, and deployment history.
MANDATORY: Discovery-First Pattern
Always list applications before querying specific resources.
Phase 1: Discovery
#!/bin/bash
export AWS_PAGER=""
echo "=== CodeDeploy Applications ==="
aws deploy list-applications --output text --query 'applications[]'
echo ""
echo "=== Application Details ==="
for app in $(aws deploy list-applications --output text --query 'applications[]'); do
aws deploy get-application --application-name "$app" --output text \
--query 'application.[applicationName,computePlatform,createTime]' &
done
wait
echo ""
echo "=== Deployment Groups ==="
for app in $(aws deploy list-applications --output text --query 'applications[]'); do
for dg in $(aws deploy list-deployment-groups --application-name "$app" --output text --query 'deploymentGroups[]'); do
aws deploy get-deployment-group --application-name "$app" --deployment-group-name "$dg" --output text \
--query "deploymentGroupInfo.[\"$app\",deploymentGroupName,deploymentConfigName,computePlatform]" &
done
done
wait
echo ""
echo "=== Deployment Configurations ==="
aws deploy list-deployment-configs --output text --query 'deploymentConfigsList[]'
Phase 2: Analysis
#!/bin/bash
export AWS_PAGER=""
echo "=== Recent Deployments ==="
for app in $(aws deploy list-applications --output text --query 'applications[]'); do
deploy_ids=$(aws deploy list-deployments --application-name "$app" --max-items 5 --output text --query 'deployments[]')
if [ -n "$deploy_ids" ]; then
for dep_id in $deploy_ids; do
aws deploy get-deployment --deployment-id "$dep_id" --output text \
--query "deploymentInfo.[deploymentId,applicationName,deploymentGroupName,status,createTime]" &
done
fi
done
wait | head -25
echo ""
echo "=== Failed Deployments ==="
for app in $(aws deploy list-applications --output text --query 'applications[]'); do
failed=$(aws deploy list-deployments --application-name "$app" \
--include-only-statuses Failed --max-items 3 --output text --query 'deployments[]')
for dep_id in $failed; do
aws deploy get-deployment --deployment-id "$dep_id" --output text \
--query "deploymentInfo.[deploymentId,applicationName,status,errorInformation.code,errorInformation.message]" &
done
done
wait | head -15
echo ""
echo "=== Deployment Group Health ==="
for app in $(aws deploy list-applications --output text --query 'applications[]'); do
for dg in $(aws deploy list-deployment-groups --application-name "$app" --output text --query 'deploymentGroups[]'); do
aws deploy get-deployment-group --application-name "$app" --deployment-group-name "$dg" --output text \
--query "deploymentGroupInfo.[applicationName,deploymentGroupName,lastSuccessfulDeployment.deploymentId,lastSuccessfulDeployment.status,lastSuccessfulDeployment.createTime]" &
done
done
wait
Output Format
- Target ≤50 lines per output
- Use
--output text --query for all commands
- Tab-delimited fields: AppName, DeploymentGroup, DeploymentId, Status
- Aggregate deployment counts by status for busy applications
- Never dump full revision details -- show deployment metadata only
Anti-Hallucination Rules
- NEVER assume resource names — always discover via CLI/API in Phase 1 before referencing in Phase 2.
- NEVER fabricate metric names or dimensions — verify against the service documentation or
--help output.
- NEVER mix CLI commands between service versions — confirm which version/API you are targeting.
- ALWAYS use the discovery → verify → analyze chain — every resource referenced must have been discovered first.
- ALWAYS handle empty results gracefully — an empty response is valid data, not an error to retry.
Counter-Rationalizations
| Shortcut |
Counter |
Why |
| "I'll skip discovery and check known resources" |
Always run Phase 1 discovery first |
Resource names change, new resources appear — assumed names cause errors |
| "The user only asked for a quick check" |
Follow the full discovery → analysis flow |
Quick checks miss critical issues; structured analysis catches silent failures |
| "Default configuration is probably fine" |
Audit configuration explicitly |
Defaults often leave logging, security, and optimization features disabled |
| "Metrics aren't needed for this" |
Always check relevant metrics when available |
API/CLI responses show current state; metrics reveal trends and intermittent issues |
| "I don't have access to that" |
Try the command and report the actual error |
Assumed permission failures prevent useful investigation; actual errors are informative |
Common Pitfalls
- Deployment status values: Created, Queued, InProgress, Baking, Succeeded, Failed, Stopped, Ready
- Compute platforms: Server (EC2/On-prem), Lambda, ECS -- each has different deployment group config
- Deployment configs: CodeDeployDefault.OneAtATime, HalfAtATime, AllAtOnce, and custom configs
- Rollback config: Check
autoRollbackConfiguration -- can trigger on DEPLOYMENT_FAILURE or DEPLOYMENT_STOP_ON_ALARM
- Blue/Green vs In-Place: Check
deploymentStyle -- Blue/Green requires load balancer config
- Target revision: Verify
targetRevision in deployment group points to correct S3/GitHub location
- Instance health: For EC2, check
instanceSummary with deployment ID for per-instance status
1---2name: managing-aws-codedeploy3description: |4 Use when working with Aws Codedeploy — aWS CodeDeploy application and5 deployment management. Covers applications, deployment groups, deployment6 history, deployment configurations, instance health, target revisions, and7 rollback settings. Use when inspecting deployments, debugging failed8 deployments, reviewing deployment strategies, or auditing deployment group9 configurations.10connection_type: aws11preload: false12metadata:13 source: https://skillmd.com/skills/cloudthinker-ai/managing-aws-codedeploy14---1516# AWS CodeDeploy Management Skill1718Analyze and manage AWS CodeDeploy applications, deployment groups, and deployment history.1920## MANDATORY: Discovery-First Pattern2122**Always list applications before querying specific resources.**2324### Phase 1: Discovery2526```bash27#!/bin/bash28export AWS_PAGER=""2930echo "=== CodeDeploy Applications ==="31aws deploy list-applications --output text --query 'applications[]'3233echo ""34echo "=== Application Details ==="35for app in $(aws deploy list-applications --output text --query 'applications[]'); do36 aws deploy get-application --application-name "$app" --output text \37 --query 'application.[applicationName,computePlatform,createTime]' &38done39wait4041echo ""42echo "=== Deployment Groups ==="43for app in $(aws deploy list-applications --output text --query 'applications[]'); do44 for dg in $(aws deploy list-deployment-groups --application-name "$app" --output text --query 'deploymentGroups[]'); do45 aws deploy get-deployment-group --application-name "$app" --deployment-group-name "$dg" --output text \46 --query "deploymentGroupInfo.[\"$app\",deploymentGroupName,deploymentConfigName,computePlatform]" &47 done48done49wait5051echo ""52echo "=== Deployment Configurations ==="53aws deploy list-deployment-configs --output text --query 'deploymentConfigsList[]'54```5556### Phase 2: Analysis5758```bash59#!/bin/bash60export AWS_PAGER=""6162echo "=== Recent Deployments ==="63for app in $(aws deploy list-applications --output text --query 'applications[]'); do64 deploy_ids=$(aws deploy list-deployments --application-name "$app" --max-items 5 --output text --query 'deployments[]')65 if [ -n "$deploy_ids" ]; then66 for dep_id in $deploy_ids; do67 aws deploy get-deployment --deployment-id "$dep_id" --output text \68 --query "deploymentInfo.[deploymentId,applicationName,deploymentGroupName,status,createTime]" &69 done70 fi71done72wait | head -257374echo ""75echo "=== Failed Deployments ==="76for app in $(aws deploy list-applications --output text --query 'applications[]'); do77 failed=$(aws deploy list-deployments --application-name "$app" \78 --include-only-statuses Failed --max-items 3 --output text --query 'deployments[]')79 for dep_id in $failed; do80 aws deploy get-deployment --deployment-id "$dep_id" --output text \81 --query "deploymentInfo.[deploymentId,applicationName,status,errorInformation.code,errorInformation.message]" &82 done83done84wait | head -158586echo ""87echo "=== Deployment Group Health ==="88for app in $(aws deploy list-applications --output text --query 'applications[]'); do89 for dg in $(aws deploy list-deployment-groups --application-name "$app" --output text --query 'deploymentGroups[]'); do90 aws deploy get-deployment-group --application-name "$app" --deployment-group-name "$dg" --output text \91 --query "deploymentGroupInfo.[applicationName,deploymentGroupName,lastSuccessfulDeployment.deploymentId,lastSuccessfulDeployment.status,lastSuccessfulDeployment.createTime]" &92 done93done94wait95```9697## Output Format9899- Target ≤50 lines per output100- Use `--output text --query` for all commands101- Tab-delimited fields: AppName, DeploymentGroup, DeploymentId, Status102- Aggregate deployment counts by status for busy applications103- Never dump full revision details -- show deployment metadata only104105## Anti-Hallucination Rules1061071. **NEVER assume resource names** — always discover via CLI/API in Phase 1 before referencing in Phase 2.1082. **NEVER fabricate metric names or dimensions** — verify against the service documentation or `--help` output.1093. **NEVER mix CLI commands between service versions** — confirm which version/API you are targeting.1104. **ALWAYS use the discovery → verify → analyze chain** — every resource referenced must have been discovered first.1115. **ALWAYS handle empty results gracefully** — an empty response is valid data, not an error to retry.112113## Counter-Rationalizations114115| Shortcut | Counter | Why |116|----------|---------|-----|117| "I'll skip discovery and check known resources" | Always run Phase 1 discovery first | Resource names change, new resources appear — assumed names cause errors |118| "The user only asked for a quick check" | Follow the full discovery → analysis flow | Quick checks miss critical issues; structured analysis catches silent failures |119| "Default configuration is probably fine" | Audit configuration explicitly | Defaults often leave logging, security, and optimization features disabled |120| "Metrics aren't needed for this" | Always check relevant metrics when available | API/CLI responses show current state; metrics reveal trends and intermittent issues |121| "I don't have access to that" | Try the command and report the actual error | Assumed permission failures prevent useful investigation; actual errors are informative |122123## Common Pitfalls124125- **Deployment status values**: Created, Queued, InProgress, Baking, Succeeded, Failed, Stopped, Ready126- **Compute platforms**: Server (EC2/On-prem), Lambda, ECS -- each has different deployment group config127- **Deployment configs**: CodeDeployDefault.OneAtATime, HalfAtATime, AllAtOnce, and custom configs128- **Rollback config**: Check `autoRollbackConfiguration` -- can trigger on DEPLOYMENT_FAILURE or DEPLOYMENT_STOP_ON_ALARM129- **Blue/Green vs In-Place**: Check `deploymentStyle` -- Blue/Green requires load balancer config130- **Target revision**: Verify `targetRevision` in deployment group points to correct S3/GitHub location131- **Instance health**: For EC2, check `instanceSummary` with deployment ID for per-instance status