Learn it in 5 minutes
HTMLAbout five minutes of reading
You cannot debug a contact center if you treat AWS as a logo on the invoice.
Amazon Connect, called Amazon Connect Customer in the admin guide after the 28 April 2026 family announcement, is a multi-tenant contact center in a Region you choose. The instance does not contain IAM, S3, Lambda, Kinesis, or CloudWatch. It calls them.
This campus starts here because every later fault lands in one of those services: a key policy, a log group, a stream shard, a Regional endpoint, or a firewall.
- The family name Amazon Connect now covers Customer, Health, Decisions, and Talent. This campus teaches the contact center.
- IAM prefixes you will meet include connect, profile, cases, wisdom, and voiceid. voiceid is historical after 20 May 2026.
- The data plane for agents is the browser, not a PBX firmware image.
- Shared responsibility: AWS runs the platform. You run flows, identity, keys, numbers, quotas, and the agent network.
Number on this page: Family 4. Customer, Health, Decisions, Talent
Confirm before relying. Prices, quotas, and exam names change. Use the source linked on this page.
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
Starting in the flow designer before you can name the Region and the account.
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
CloudFormation study snippet
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.