A depends-on map you can defend

About five minutes of reading

Every later track names the foundation it needs. If that foundation is missing, the track's lab will show the same fault.

Telephony depends on the instance and on quotas. Flows depend on telephony only because a number has to enter somewhere. Lambda depends on IAM. The CCP depends on the network lesson. Analytics depends on Kinesis and S3. Global Resiliency depends on identity, numbers, and a supported Region pair.

The Ecosystem track depends on all of those, because WFM, quality, E911, and the CRM are consumers of ContactId, recordings, agent events, and profiles.

• Read the depends-on line on each track before you skip ahead.
• A migration bridge without flows and routing is a glossary, not a plan.
• E911 depends on Profiles, Lambda, and an outbound whisper flow.
• Price estimates depend on the rate card date, which this campus stamps as 14 October 2026.

Number on this page: Tracks 18. Foundations through Ecosystem

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

Picture from this room.

1. Name the dependency. Read the track map.
2. Close the gap. Do that lesson.
3. Then build. The flow or the integration.

What usually goes wrong: Treating tracks as independent products.

Security in Connect Customer - Amazon Connect Customer AWS docs. 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

Treating tracks as independent products.

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.