Analytics Skills

Skill 55 of 130

Managing Amazon Kinesis Data Streams

Operates Amazon Kinesis Data Streams (KDS).

2 minutes · 377 words · 6 sections

Install

$ npx skills add aws/agent-toolkit-for-aws --skill managing-amazon-kinesis-data-streams

$ npx skills add aws/agent-toolkit-for-aws

» /plugin marketplace add aws/agent-toolkit-for-aws

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

Domain expertise for Amazon Kinesis Data Streams. This skill covers streaming tables and Amazon S3 delivery, which provide serverless, fully managed delivery from a KDS stream directly to Apache Iceberg tables on S3 Tables or to general-purpose S3 buckets — no consumers, no Firehose, no Flink required for append-only delivery.

Delivery is configured as a channel on a stream via CreateChannel. Channels consume no shard capacity and no enhanced fan-out slots, so they do not compete with existing consumers.

The AWS MCP server is recommended for executing AWS operations. When the MCP server is not available, use the AWS CLI or shell commands instead.

Which Workflow Do You Need?

Customer Intent	Reference
Deliver stream data to Apache Iceberg tables on S3 Tables — setup, IAM, Glue schema, type mapping, partitioning, channel lifecycle	references/streaming-tables.md (opens in a new tab)
Deliver stream data to a general-purpose S3 bucket as objects — setup, IAM, compression, storage class, output key templates, channel lifecycle	references/general-purpose-delivery-to-s3.md (opens in a new tab)
Build a lakehouse / data lake from Kinesis; make streaming data queryable in Athena	references/streaming-tables.md (opens in a new tab)
Zero-ops, serverless alternative to Firehose or Kinesis consumers for KDS → S3 delivery	references/general-purpose-delivery-to-s3.md (opens in a new tab)
CloudWatch metrics and alarms, delivery logging, CloudTrail, encryption, channel states, quotas, naming rules, what can be updated	references/monitoring-security-and-limits.md (opens in a new tab)
Channel is ACTIVE but no data arrives; records landing in the DLQ; rising data freshness	Start with references/monitoring-security-and-limits.md (opens in a new tab), then the destination-specific troubleshooting table
Deliver to both S3 and S3 Tables from one stream	Supported — create one channel per destination

Prerequisites

Both destinations require an ON_DEMAND stream — provisioned-mode streams are not supported. Each channel also needs an IAM service execution role trusted by kinesis.amazonaws.com, and a destination in the same Region as the stream.

Hard Limits to Check First

These rule out the feature entirely, so confirm them before designing a solution:

Append-only — no CDC, upserts, or deletes
No schema evolution — a schema change means deleting and recreating the channel
No backfill — only records produced after the channel is ACTIVE are delivered
No transformations — records are delivered as-is
New table per channel — cannot deliver into an existing Iceberg table
Data freshness is 300–900 seconds — not sub-minute
Same Region only — cross-account is supported, cross-Region is not

If any of these block the customer, recommend Managed Service for Apache Flink instead.

Additional Resources

About this skill

Trigger

Operates Amazon Kinesis Data Streams (KDS). Covers streaming tables and Amazon S3 delivery - serverless, fully managed delivery from a KDS stream to Apache Iceberg tables on S3 Tables or to general-purpose S3 buckets. Includes channel setup, IAM, schemas, output key templates, CloudWatch metrics and alarms, DLQ handling, quotas, and troubleshooting. For all other KDS topics and questions, search AWS documentation and blogs instead. Triggers: Kinesis Data Streams, KDS, streaming tables, stream to S3, stream to Iceberg, stream to S3 Tables, KDS delivery, KDS channel, CreateChannel, data channel, data freshness, dead-letter queue, KDS lakehouse, serverless Kinesis delivery, Firehose alternative for KDS, zero-ops Kinesis to S3. DO NOT USE for Kinesis Data Firehose, Kinesis Video Streams, or Managed Service for Apache Flink — use dedicated skills or search documentation instead.

The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.

Colophon for this issue

Colophon

How this issue was made

Source

github.com/aws/agent-toolkit-for-aws, branch main, last pushed 24 September 2026.

Licence

Apache-2.0 — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

130 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 19 distinct layouts observed: plugins/aws-agents-for-devsecops/skills/*/SKILL.md, plugins/aws-agents/skills/*/SKILL.md, plugins/aws-core/skills/*/SKILL.md, skills/core-skills/*/SKILL.md, skills/specialized-skills/analytics-skills/*/SKILL.md, skills/specialized-skills/database-skills/*/SKILL.md, skills/specialized-skills/ec2-skills/*/SKILL.md, skills/specialized-skills/end-user-computing-skills/*/SKILL.md, skills/specialized-skills/messaging-and-streaming-skills/*/SKILL.md, skills/specialized-skills/migration-and-modernization-skills/*/SKILL.md, skills/specialized-skills/networking-and-content-delivery-skills/*/SKILL.md, skills/specialized-skills/operations-skills/*/SKILL.md, skills/specialized-skills/quantum-computing-skills/*/SKILL.md, skills/specialized-skills/resilience-skills/*/SKILL.md, skills/specialized-skills/security-and-identity-skills/*/SKILL.md, skills/specialized-skills/serverless-skills/*/SKILL.md, skills/specialized-skills/storage-skills/*/SKILL.md, skills/specialized-skills/system-table-skills/*/SKILL.md, skills/specialized-skills/web-and-mobile-development/*/SKILL.md.

Duplicates collapsed

34 mirror copies folded into their canonical skill — republished for Alternate. Copies match on content hash and on position once a leading per-agent prefix is stripped, because the same skill is routinely shipped under a dozen agent directories with a dozen different hashes.

Issue colours

Resolved from a curated brand profile — hue 65°, chroma 0.174. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Shifted “6 headings” from h1 to h2 so the skill title is the only h1.

Spec compliance

Every skill satisfies the Agent Skills specification’s frontmatter rules.

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Marketplace

A plugin manifest is published at .claude-plugin/marketplace.json by Amazon Web Services, declaring 4 plugins. It is read for editorial metadata only — never as the skill index, which is always the repository tree.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /aws/agent-toolkit-for-aws.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

Customer Intent	Reference
Deliver stream data to Apache Iceberg tables on S3 Tables — setup, IAM, Glue schema, type mapping, partitioning, channel lifecycle	references/streaming-tables.md (opens in a new tab)
Deliver stream data to a general-purpose S3 bucket as objects — setup, IAM, compression, storage class, output key templates, channel lifecycle	references/general-purpose-delivery-to-s3.md (opens in a new tab)
Build a lakehouse / data lake from Kinesis; make streaming data queryable in Athena	references/streaming-tables.md (opens in a new tab)
Zero-ops, serverless alternative to Firehose or Kinesis consumers for KDS → S3 delivery	references/general-purpose-delivery-to-s3.md (opens in a new tab)
CloudWatch metrics and alarms, delivery logging, CloudTrail, encryption, channel states, quotas, naming rules, what can be updated	references/monitoring-security-and-limits.md (opens in a new tab)
Channel is ACTIVE but no data arrives; records landing in the DLQ; rising data freshness	Start with references/monitoring-security-and-limits.md (opens in a new tab), then the destination-specific troubleshooting table
Deliver to both S3 and S3 Tables from one stream	Supported — create one channel per destination

Prerequisites

Hard Limits to Check First

These rule out the feature entirely, so confirm them before designing a solution:

Append-only — no CDC, upserts, or deletes
No schema evolution — a schema change means deleting and recreating the channel
No backfill — only records produced after the channel is ACTIVE are delivered
No transformations — records are delivered as-is
New table per channel — cannot deliver into an existing Iceberg table
Data freshness is 300–900 seconds — not sub-minute
Same Region only — cross-account is supported, cross-Region is not

If any of these block the customer, recommend Managed Service for Apache Flink instead.

Managing Amazon Kinesis Data Streams

Amazon Kinesis Data Streams

Overview

Which Workflow Do You Need?

Prerequisites

Hard Limits to Check First

Additional Resources

About this skill

Trigger

Colophon

Managing Amazon Kinesis Data Streams

Amazon Kinesis Data Streams

Overview

Which Workflow Do You Need?

Prerequisites

Hard Limits to Check First

Additional Resources

Appendix 55.1–55.3

ReferencesMarkdown · 3 files

About this skill

Trigger

Colophon

Appendix 55.1–55.3

ReferencesMarkdown · 3 files