How do I install the Iotanalytics Diagnostics skill?

Run npx skillmds@latest add aws-samples/iotanalytics-diagnostics in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Iotanalytics Diagnostics safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Iotanalytics Diagnostics?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Iotanalytics Diagnostics free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Iotanalytics Diagnostics?

aws-samples (@aws-samples) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Iotanalytics Diagnostics by aws-samples

Name: Iotanalytics Diagnostics
Author: aws-samples

Iotanalytics Diagnostics

Use this skill to investigate and troubleshoot AWS IoT Analytics problems by analyzing channels, pipelines, data stores, datasets, SQL queries, container activities, and data retention using structured runbooks. Activate when: channel ingestion failures, pipeline processing errors, data store query issues, dataset computation failures, SQL errors, container activity problems, or the user says something is wrong with IoT Analytics.

aws-samples 19ce80d 17 files · 64.1 KB Updated Sep 17, 2026

File contents

AWS IoT Analytics Diagnostics

When to use

Any AWS IoT Analytics investigation — channels, pipelines, data stores, datasets, SQL queries, container activities, or data retention troubleshooting.

Investigation workflow

Step 1 — Collect and triage

aws iotanalytics list-channels
aws iotanalytics describe-channel --channel-name <name>
aws iotanalytics list-pipelines
aws iotanalytics describe-pipeline --pipeline-name <name>

Step 2 — Domain deep dive

aws iotanalytics list-datastores
aws iotanalytics describe-datastore --datastore-name <name>
aws iotanalytics list-datasets
aws iotanalytics describe-dataset --dataset-name <name>
aws iotanalytics get-dataset-content --dataset-name <name>

Step 3 — Detailed investigation

aws iotanalytics sample-channel-data --channel-name <name>
aws iotanalytics run-pipeline-activity --pipeline-activities '[<activity>]' --payloads '<base64>'
aws cloudwatch get-metric-statistics --namespace AWS/IoTAnalytics --metric-name IncomingMessages --start-time <start> --end-time <end> --period 300 --statistics Sum

Read references/guardrails.md before concluding on any IoT Analytics issue.

Tool quick reference

Tool / API	When to use
`describe-channel`	Check channel configuration and status
`describe-pipeline`	Check pipeline activities and errors
`describe-datastore`	Check data store configuration
`describe-dataset`	Check dataset queries and schedule
`sample-channel-data`	Get sample messages from channel
`run-pipeline-activity`	Test pipeline activity with sample data
CloudWatch Metrics	Check ingestion and processing rates

Anti-hallucination rules

Always cite specific channel, pipeline, or dataset names as evidence.
Pipelines process data sequentially through activities. Never assume parallel processing.
Datasets are computed results, not raw data stores. Never confuse them.
SQL datasets use a specific SQL dialect. Never assume standard SQL compatibility.
Container datasets run custom Docker containers. Never assume Lambda execution.
Spend no more than 2 minutes on any single hypothesis. Pivot if inconclusive.

14 runbooks

Category	IDs	Covers
A — Channels	A1-A2	Ingestion failures, channel configuration
B — Pipelines	B1-B3	Processing errors, activity failures, transforms
C — Data Stores	C1-C2	Storage issues, partitioning
D — Datasets	D1-D3	SQL queries, container activities, scheduling
E — Retention	E1-E2	Data retention, cleanup
Z — Catch-All	Z1	General troubleshooting

---name: iotanalytics-diagnosticsdescription: Use this skill to investigate and troubleshoot AWS IoT Analytics problems by analyzing channels, pipelines, data stores, datasets, SQL queries, container activities, and data retention using structured runbooks. Activate when: channel ingestion failures, pipeline processing errors, data store query issues, dataset computation failures, SQL errors, container activity problems, or the user says something is wrong with IoT Analytics.---# AWS IoT Analytics Diagnostics## When to useAny AWS IoT Analytics investigation — channels, pipelines, data stores, datasets, SQL queries, container activities, or data retention troubleshooting.## Investigation workflow### Step 1 — Collect and triage```aws iotanalytics list-channelsaws iotanalytics describe-channel --channel-name <name>aws iotanalytics list-pipelinesaws iotanalytics describe-pipeline --pipeline-name <name>```### Step 2 — Domain deep dive```aws iotanalytics list-datastoresaws iotanalytics describe-datastore --datastore-name <name>aws iotanalytics list-datasetsaws iotanalytics describe-dataset --dataset-name <name>aws iotanalytics get-dataset-content --dataset-name <name>```### Step 3 — Detailed investigation```aws iotanalytics sample-channel-data --channel-name <name>aws iotanalytics run-pipeline-activity --pipeline-activities '[<activity>]' --payloads '<base64>'aws cloudwatch get-metric-statistics --namespace AWS/IoTAnalytics --metric-name IncomingMessages --start-time <start> --end-time <end> --period 300 --statistics Sum```Read `references/guardrails.md` before concluding on any IoT Analytics issue.## Tool quick reference| Tool / API | When to use ||------------|-------------|| `describe-channel` | Check channel configuration and status || `describe-pipeline` | Check pipeline activities and errors || `describe-datastore` | Check data store configuration || `describe-dataset` | Check dataset queries and schedule || `sample-channel-data` | Get sample messages from channel || `run-pipeline-activity` | Test pipeline activity with sample data || CloudWatch Metrics | Check ingestion and processing rates |## Anti-hallucination rules1. Always cite specific channel, pipeline, or dataset names as evidence.2. Pipelines process data sequentially through activities. Never assume parallel processing.3. Datasets are computed results, not raw data stores. Never confuse them.4. SQL datasets use a specific SQL dialect. Never assume standard SQL compatibility.5. Container datasets run custom Docker containers. Never assume Lambda execution.6. Spend no more than 2 minutes on any single hypothesis. Pivot if inconclusive.## 14 runbooks| Category | IDs | Covers ||----------|-----|--------|| A — Channels | A1-A2 | Ingestion failures, channel configuration || B — Pipelines | B1-B3 | Processing errors, activity failures, transforms || C — Data Stores | C1-C2 | Storage issues, partitioning || D — Datasets | D1-D3 | SQL queries, container activities, scheduling || E — Retention | E1-E2 | Data retention, cleanup || Z — Catch-All | Z1 | General troubleshooting |

Frequently asked questions