managing-aws-config-deep

name	managing-aws-config-deep
description	Use when working with Aws Config Deep — aWS Config deep rule and compliance management. Covers Config rules, conformance packs, aggregators, advanced queries, remediation actions, configuration history, and multi-account compliance dashboards. Use when auditing AWS resource compliance, managing Config rules, reviewing conformance pack results, or querying resource configurations across accounts.
connection_type	aws-config
preload	false

AWS Config Deep Management Skill

Deep management of AWS Config rules, conformance packs, aggregators, and compliance queries.

MANDATORY: Discovery-First Pattern

Always inspect Config recorder status and rule compliance before changes.

Phase 1: Discovery

#!/bin/bash
echo "=== Config Recorder Status ==="
aws configservice describe-configuration-recorder-status --query 'ConfigurationRecordersStatus[*].{Name:name,Recording:recording,LastStatus:lastStatus}' --output table 2>/dev/null

echo ""
echo "=== Delivery Channel ==="
aws configservice describe-delivery-channels --query 'DeliveryChannels[*].{Name:name,S3Bucket:s3BucketName,SNSTopic:snsTopicARN}' --output table 2>/dev/null

echo ""
echo "=== Config Rules Summary ==="
aws configservice describe-compliance-by-config-rule --query 'ComplianceByConfigRules[*].{Rule:ConfigRuleName,Compliance:Compliance.ComplianceType}' --output table 2>/dev/null | head -20

echo ""
echo "=== Conformance Packs ==="
aws configservice describe-conformance-packs --query 'ConformancePackDetails[*].{Name:ConformancePackName,Status:ConformancePackState}' --output table 2>/dev/null | head -10

echo ""
echo "=== Aggregators ==="
aws configservice describe-configuration-aggregators --query 'ConfigurationAggregators[*].{Name:ConfigurationAggregatorName,Type:AccountAggregationSources[0].AllAwsRegions}' --output table 2>/dev/null | head -10

Phase 2: Analysis

#!/bin/bash
RULE="${1:-}"

echo "=== Non-Compliant Resources ==="
if [ -n "$RULE" ]; then
  aws configservice get-compliance-details-by-config-rule --config-rule-name "$RULE" --compliance-types NON_COMPLIANT --query 'EvaluationResults[*].{Resource:EvaluationResultIdentifier.EvaluationResultQualifier.ResourceId,Type:EvaluationResultIdentifier.EvaluationResultQualifier.ResourceType,Time:ResultRecordedTime}' --output table 2>/dev/null | head -15
else
  aws configservice describe-compliance-by-resource --compliance-types NON_COMPLIANT --query 'ComplianceByResources[*].{Type:ResourceType,Id:ResourceId,Compliance:Compliance.ComplianceType}' --output table 2>/dev/null | head -15
fi

echo ""
echo "=== Advanced Query ==="
aws configservice select-resource-config --expression "SELECT resourceId, resourceType, configuration.instanceType WHERE resourceType = 'AWS::EC2::Instance'" --query 'Results' --output text 2>/dev/null | head -10

echo ""
echo "=== Remediation Status ==="
aws configservice describe-remediation-execution-status --config-rule-name "${RULE:-*}" --query 'RemediationExecutionStatuses[*].{Resource:ResourceKey.resourceId,State:State,StepDetails:StepDetails[0].Name}' --output table 2>/dev/null | head -10

echo ""
echo "=== Conformance Pack Compliance ==="
aws configservice get-conformance-pack-compliance-summary --query 'ConformancePackComplianceSummaryList[*].{Pack:ConformancePackName,Compliant:ConformancePackComplianceStatus}' --output table 2>/dev/null |  -10

Output Rules

• TOKEN EFFICIENCY: Target <=50 lines per output
• Show compliance summaries, not individual evaluation details
• Use advanced queries for targeted resource inspection
• Highlight non-compliant resources with remediation status

Safety Rules

• NEVER auto-remediate without reviewing the remediation action
• Test custom rules in evaluation-only mode first
• Review advanced query results before bulk operations
• Check aggregator coverage spans all required accounts/regions
• Validate conformance pack parameters before deployment

Output Format

Present results as a structured report:

Managing Aws Config Deep Report
═══════════════════════════════
Resources discovered: [count]

Resource       Status    Key Metric    Issues
──────────────────────────────────────────────
[name]         [ok/warn] [value]       [findings]

Summary: [total] resources | [ok] healthy | [warn] warnings | [crit] critical
Action Items: [list of prioritized findings]

Target ≤50 lines of output. Use tables for multi-resource comparisons.

Anti-Hallucination Rules

1. NEVER assume resource names — always discover via CLI/API in Phase 1 before referencing in Phase 2.
2. NEVER fabricate metric names or dimensions — verify against the service documentation or --help output.
3. NEVER mix CLI commands between service versions — confirm which version/API you are targeting.
4. ALWAYS use the discovery → verify → analyze chain — every resource referenced must have been discovered first.
5. 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