AWS Amplify Management Skill
Analyze and manage AWS Amplify applications, deployments, and hosting configurations.
MANDATORY: Discovery-First Pattern
Always list apps and branches before querying specific resources.
Phase 1: Discovery
#!/bin/bash
export AWS_PAGER=""
echo "=== Amplify Apps ==="
aws amplify list-apps --output text \
--query 'apps[].[appId,name,defaultDomain,platform,repository]'
echo ""
echo "=== App Branches ==="
for app_id in $(aws amplify list-apps --output text --query 'apps[].appId'); do
aws amplify list-branches --app-id "$app_id" --output text \
--query "branchSummaries[].[\"$app_id\",branchName,stage,activeJobId,lastDeployTime]" &
done
wait
echo ""
echo "=== Domain Associations ==="
for app_id in $(aws amplify list-apps --output text --query 'apps[].appId'); do
aws amplify list-domain-associations --app-id "$app_id" --output text \
--query "domainAssociations[].[\"$app_id\",domainName,domainStatus,certificateVerificationDNSRecord]" &
done
wait
Phase 2: Analysis
#!/bin/bash
export AWS_PAGER=""
echo "=== Recent Build Jobs ==="
for app_id in $(aws amplify list-apps --output text --query 'apps[].appId'); do
for branch in $(aws amplify list-branches --app-id "$app_id" --output text --query 'branchSummaries[].branchName'); do
aws amplify list-jobs --app-id "$app_id" --branch-name "$branch" --max-items 3 --output text \
--query "jobSummaries[].[\"$app_id\",\"$branch\",jobId,status,startTime,endTime]" &
done
done
wait
echo ""
echo "=== Backend Environments ==="
for app_id in $(aws amplify list-apps --output text --query 'apps[].appId'); do
aws amplify list-backend-environments --app-id "$app_id" --output text \
--query "backendEnvironments[].[\"$app_id\",environmentName,stackName,deploymentArtifacts]" 2>/dev/null &
done
wait
echo ""
echo "=== Webhooks ==="
for app_id in $(aws amplify list-apps --output text --query 'apps[].appId'); do
aws amplify list-webhooks --app-id "$app_id" --output text \
--query "webhooks[].[\"$app_id\",webhookId,branchName,webhookUrl]" 2>/dev/null &
done
wait
Output Format
- Target ≤50 lines per output
- Use
--output text --query for all commands
- Tab-delimited fields: AppId, Name, Branch, Status
- Aggregate build results by status when listing many jobs
- Never dump full build logs -- extract key error lines 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
- Build logs: Use
get-job to retrieve build steps, not CloudWatch Logs
- Branch auto-detection: Amplify may auto-detect branches from repo -- check
enableAutoBranchCreation
- Custom domains: Domain verification can take time -- check
domainStatus before assuming failure
- Webhooks: Each branch can have its own webhook -- list per branch, not per app
- Platform field: Values are
WEB (static) or WEB_DYNAMIC (SSR) -- affects build behavior
1---2name: managing-aws-amplify3description: Use when working with Aws Amplify — aWS Amplify application management and deployment analysis. Covers Amplify apps, branches, backend environments, build status, domain associations, and webhook configurations. Use when inspecting Amplify deployments, debugging build failures, reviewing hosting configurations, or auditing Amplify app settings.4---56# AWS Amplify Management Skill78Analyze and manage AWS Amplify applications, deployments, and hosting configurations.910## MANDATORY: Discovery-First Pattern1112**Always list apps and branches before querying specific resources.**1314### Phase 1: Discovery1516```bash17#!/bin/bash18export AWS_PAGER=""1920echo "=== Amplify Apps ==="21aws amplify list-apps --output text \22 --query 'apps[].[appId,name,defaultDomain,platform,repository]'2324echo ""25echo "=== App Branches ==="26for app_id in $(aws amplify list-apps --output text --query 'apps[].appId'); do27 aws amplify list-branches --app-id "$app_id" --output text \28 --query "branchSummaries[].[\"$app_id\",branchName,stage,activeJobId,lastDeployTime]" &29done30wait3132echo ""33echo "=== Domain Associations ==="34for app_id in $(aws amplify list-apps --output text --query 'apps[].appId'); do35 aws amplify list-domain-associations --app-id "$app_id" --output text \36 --query "domainAssociations[].[\"$app_id\",domainName,domainStatus,certificateVerificationDNSRecord]" &37done38wait39```4041### Phase 2: Analysis4243```bash44#!/bin/bash45export AWS_PAGER=""4647echo "=== Recent Build Jobs ==="48for app_id in $(aws amplify list-apps --output text --query 'apps[].appId'); do49 for branch in $(aws amplify list-branches --app-id "$app_id" --output text --query 'branchSummaries[].branchName'); do50 aws amplify list-jobs --app-id "$app_id" --branch-name "$branch" --max-items 3 --output text \51 --query "jobSummaries[].[\"$app_id\",\"$branch\",jobId,status,startTime,endTime]" &52 done53done54wait5556echo ""57echo "=== Backend Environments ==="58for app_id in $(aws amplify list-apps --output text --query 'apps[].appId'); do59 aws amplify list-backend-environments --app-id "$app_id" --output text \60 --query "backendEnvironments[].[\"$app_id\",environmentName,stackName,deploymentArtifacts]" 2>/dev/null &61done62wait6364echo ""65echo "=== Webhooks ==="66for app_id in $(aws amplify list-apps --output text --query 'apps[].appId'); do67 aws amplify list-webhooks --app-id "$app_id" --output text \68 --query "webhooks[].[\"$app_id\",webhookId,branchName,webhookUrl]" 2>/dev/null &69done70wait71```7273## Output Format7475- Target ≤50 lines per output76- Use `--output text --query` for all commands77- Tab-delimited fields: AppId, Name, Branch, Status78- Aggregate build results by status when listing many jobs79- Never dump full build logs -- extract key error lines only8081## Anti-Hallucination Rules82831. **NEVER assume resource names** — always discover via CLI/API in Phase 1 before referencing in Phase 2.842. **NEVER fabricate metric names or dimensions** — verify against the service documentation or `--help` output.853. **NEVER mix CLI commands between service versions** — confirm which version/API you are targeting.864. **ALWAYS use the discovery → verify → analyze chain** — every resource referenced must have been discovered first.875. **ALWAYS handle empty results gracefully** — an empty response is valid data, not an error to retry.8889## Counter-Rationalizations9091| Shortcut | Counter | Why |92|----------|---------|-----|93| "I'll skip discovery and check known resources" | Always run Phase 1 discovery first | Resource names change, new resources appear — assumed names cause errors |94| "The user only asked for a quick check" | Follow the full discovery → analysis flow | Quick checks miss critical issues; structured analysis catches silent failures |95| "Default configuration is probably fine" | Audit configuration explicitly | Defaults often leave logging, security, and optimization features disabled |96| "Metrics aren't needed for this" | Always check relevant metrics when available | API/CLI responses show current state; metrics reveal trends and intermittent issues |97| "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 |9899## Common Pitfalls100101- **Build logs**: Use `get-job` to retrieve build steps, not CloudWatch Logs102- **Branch auto-detection**: Amplify may auto-detect branches from repo -- check `enableAutoBranchCreation`103- **Custom domains**: Domain verification can take time -- check `domainStatus` before assuming failure104- **Webhooks**: Each branch can have its own webhook -- list per branch, not per app105- **Platform field**: Values are `WEB` (static) or `WEB_DYNAMIC` (SSR) -- affects build behavior
cloudthinker-ai