Skip to content

cloudthinker-ai/CloudSkills / skills/connections/managing-aws-iot-core

managing-aws-iot-core

Verified

Use when working with Aws Iot Core — aWS IoT Core management including things, thing groups, certificates, policies, rules, topic monitoring, device shadows, and fleet indexing. Covers device connectivity health, message throughput, rule action errors, certificate expiration, and shadow drift analysis.

AWS IoT Core Management Skill

Monitor and manage AWS IoT Core device fleet and messaging infrastructure.

MANDATORY: Discovery-First Pattern

Always discover things, certificates, and rules before querying metrics or shadows.

Phase 1: Discovery

#!/bin/bash
REGION="${AWS_REGION:-us-east-1}"

echo "=== IoT Endpoint ==="
aws iot describe-endpoint --endpoint-type iot:Data-ATS --region "$REGION" \
  --query 'endpointAddress' --output text

echo ""
echo "=== Thing Summary ==="
aws iot list-things --region "$REGION" --max-items 20 \
  --query 'things[].{Name:thingName,Type:thingTypeName,Version:version}' \
  --output table

echo ""
echo "=== Thing Groups ==="
aws iot list-thing-groups --region "$REGION" \
  --query 'thingGroups[].{Name:groupName,ARN:groupArn}' \
  --output table

echo ""
echo "=== Thing Types ==="
aws iot list-thing-types --region "$REGION" \
  --query 'thingTypes[].{Name:thingTypeName,Deprecated:thingTypeProperties.deprecated}' \
  --output table

echo ""
echo "=== Certificates ==="
aws iot list-certificates --region "$REGION" \
  --query 'certificates[].{ID:certificateId,Status:status,Created:creationDate}' \
  --output table | head -15

echo ""
echo "=== IoT Rules ==="
aws iot list-topic-rules --region "$REGION" \
  --query 'rules[].{Name:ruleName,Created:createdAt,Disabled:ruleDisabled}' \
  --output table

Phase 1 outputs: Endpoint, things, groups, types, certificates, rules

Phase 2: Analysis

#!/bin/bash
echo "=== Fleet Connectivity (via indexing) ==="
aws iot search-index --region "$REGION" \
  --query-string "connectivity.connected:true" \
  --query 'things | length(@)' --output text 2>/dev/null | \
  xargs -I{} echo "Connected things: {}" || echo "Fleet indexing not enabled"

echo ""
echo "=== Certificate Expiration Check ==="
for cert_id in $(aws iot list-certificates --region "$REGION" --query 'certificates[].certificateId' --output text | head -10); do
  aws iot describe-certificate --certificate-id "$cert_id" --region "$REGION" \
    --query '{ID:certificateDescription.certificateId,Status:certificateDescription.status,Expiry:certificateDescription.validity.notAfter}' \
    --output json | jq -r '"\(.ID[:12]) | Status: \(.Status) | Expires: \(.Expiry)"'
done

echo ""
echo "=== Rule Action Errors (24h) ==="
aws cloudwatch get-metric-statistics --namespace AWS/IoT \
  --metric-name RuleActionFailure --period 86400 \
  --start-time "$(date -u -v-1d +%Y-%m-%dT%H:%M:%SZ 2>/dev/null || date -u -d '1 day ago' +%Y-%m-%dT%H:%M:%SZ)" \
  --end-time "$(date -u +%Y-%m-%dT%H:%M:%SZ)" \
  --statistics Sum --region "$REGION" \
  --query 'Datapoints[0].Sum' --output text

echo ""
echo "=== Message Broker Metrics (24h) ==="
for metric in PublishIn.Success Subscribe.Success Connect.Success; do
  val=$(aws cloudwatch get-metric-statistics --namespace AWS/IoT \
    --metric-name "$metric" --period 86400 \
    --start-time "$(date -u -v-1d +%Y-%m-%dT%H:%M:%SZ 2>/dev/null || date -u -d '1 day ago' +%Y-%m-%dT%H:%M:%SZ)" \
    --end-time "$(date -u +%Y-%m-%dT%H:%M:%SZ)" \
    --statistics Sum --region "$REGION" \
    --query 'Datapoints[0].Sum' --output text 2>/dev/null)
  echo "$metric: ${val:-0}"
done

Output Format

AWS IOT CORE STATUS
===================
Region: {region} | Endpoint: {endpoint}
Things: {count} | Connected: {count}
Thing Groups: {count} | Types: {count}
Certificates: {active}/{total} (expiring soon: {count})
Rules: {enabled}/{total}
24h Messages: {publish} published, {subscribe} subscribed
Rule Failures (24h): {count}
Issues: {list_of_warnings}

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

ShortcutCounterWhy
"I'll skip discovery and check known resources"Always run Phase 1 discovery firstResource names change, new resources appear — assumed names cause errors
"The user only asked for a quick check"Follow the full discovery → analysis flowQuick checks miss critical issues; structured analysis catches silent failures
"Default configuration is probably fine"Audit configuration explicitlyDefaults often leave logging, security, and optimization features disabled
"Metrics aren't needed for this"Always check relevant metrics when availableAPI/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 errorAssumed permission failures prevent useful investigation; actual errors are informative

Common Pitfalls

  • Fleet indexing: Must be enabled separately — required for connectivity queries
  • Certificate rotation: Certificates expire — set up automated rotation
  • Rule SQL versioning: IoT SQL has versions (2015-10-08, 2016-03-23) — check rule SQL version
  • Topic depth: Max 8 topic levels — design topic hierarchy carefully
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 319kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall