Kinesis is how the ecosystem listens

About five minutes of reading

Anything that must react to agents or to finished contacts needs a stream, not a person refreshing a report.

Agent events and contact trace records can go to Kinesis Data Streams or Firehose. Streams let several consumers read. Firehose is the buffered path to S3. One quiet five-minute stretch is the documented moment to look at delivery errors.

A single shard is a common starting size for agent events and a common cause of lag once WFM and a custom dashboard both read it.

• CTRs are near real time, not instant, and consumers must tolerate duplicates.
• Only one Firehose is the default CTR delivery. Fan out by consuming a stream.
• Join on ContactId. There is no other honest key.
• Agent events are the adherence feed. Historical reports are not.

Number on this page: Worry at 5 min. No CTR delivery

Confirm before relying. Prices, quotas, and exam names change. Use the source linked on this page.

Picture from this room.

1. Enable. Data streaming on the instance.
2. Size. Shards for consumers.
3. Consume. Idempotent reader.
4. Join. ContactId.

What usually goes wrong: Pointing two WFM products at one shard and discovering lag during a Monday peak.

Integrate Amazon Connect with Amazon Kinesis | AWS re:Post community. last checked 2026-10

The prose is a study paraphrase. The link is the source of the facts.

Glossary

• Contact One interaction: a call, chat, task, or email. A transfer usually creates another contact linked by PreviousContactId and NextContactId.
• Connect Customer The name used from 28 Apr 2026 for the contact center product previously called Amazon Connect.
• CloudWatch Metrics and flow logs. Alarm at 80 percent of a quota, which is the operations guidance in the email quota note.
• Kinesis Data Streams The durable stream for CTRs and agent events when more than one consumer must read them.

Mind map

Open the Foundations mind map

Sister technologies

A flow fails in IAM, a Region, a log group, or a network rule long before it fails as a 'Connect bug'.

Config and troubleshooting

Pointing two WFM products at one shard and discovering lag during a Monday peak.

IAM, Lambda, S3, Kinesis, and CloudWatch are not inside the instance. This stack creates the instance and turns on flow logs and Contact Lens.

CfnInstance AWS::Connect::Instance

AWSTemplateFormatVersion: "2010-09-09"
Description: Connect instance with flow logs and Contact Lens
Resources:
  CampusInstance:
    Type: AWS::Connect::Instance
    Properties:
      IdentityManagementType: SAML
      InstanceAlias: campus-demo
      Attributes:
        InboundCalls: true
        OutboundCalls: true
        ContactflowLogs: true
        ContactLens: true

Integration map

Join records on ContactId. The integration map room lists the seams.

Cross-platform bridges

A CUCM calling search space is not a routing profile, but the profile is the closest idea of 'who can receive what'. A partition is not a Connect object. A UCCX CSQ and a UCCE skill group map to a queue. Precision steps map to routing criteria. A script, an Architect flow, and an Avaya vector map to a contact flow.

Open the mapping room

Future hooks

Hooks you can adopt later: EventBridge contact events, the CTR stream, agent events, Kinesis Video, Customer Profiles events, Cases, Show view, data tables, External Tool, and the flow language JSON in your pipeline. Live Sync and Agentic CX are the 2026 hooks for guided and agentic experiences.