Display
Foundations
About five minutes of reading
Names moved. Features mostly stayed. Voice ID did not.
The timeline in this campus is a study map. Dates come from AWS What's New, the admin guide, the AWS News Blog, or a compiled timeline that cites those pages and was checked on 25 September 2026. Where the admin guide applies the 2026 product name to a 2017 row, the timeline keeps the name used on the day.
Read it before you use an old runbook. Contact Lens means conversational analytics. Amazon Q in Connect means agent assist. High-volume outbound means campaigns. Voice ID means ended.
Number on this page: Launch 2017. 28 March, Amazon Connect
Selected dates. Open the timeline view for the full set.
What usually goes wrong: Quoting a document-history row's 2026 wording as if that was the 2017 name.
Which term matches this description? After this date the feature is gone from the console, admin website, CCP, and Voice ID resources.
After this date the feature is gone from the console, admin website, CCP, and Voice ID resources. The term is Timeline 2026-05-20: Voice ID end of support.
Amazon Connect Customer Voice ID end of support - Amazon Connect Customer AWS docs. last checked 2026-10
Which term matches this description? Same routing and reporting tools cover voice and chat.
Same routing and reporting tools cover voice and chat. The term is Timeline 2019-11-21: Web and mobile chat.
AWS History and Timeline regarding Amazon Connect - Overview, Functions, Features, Summary of Updates, and Introduction to Amazon Connect Customer | hidekazu-ko community. last checked 2026-10
Which term matches this description? Live analytics, unified profiles, and a task channel. Wisdom and Voice ID enter preview the same day.
Live analytics, unified profiles, and a task channel. Wisdom and Voice ID enter preview the same day. The term is Timeline 2020-12-01: Real-time Contact Lens, Customer Profiles, Tasks.
Amazon Connect โ Now Smarter and More Integrated With Third-Party Tools | AWS News Blog AWS docs. last checked 2026-10
AWS History and Timeline regarding Amazon Connect - Overview, Functions, Features, Summary of Updates, and Introduction to Amazon Connect Customer | hidekazu-ko community. last checked 2026-10
The prose is a study paraphrase. The link is the source of the facts.
A flow fails in IAM, a Region, a log group, or a network rule long before it fails as a 'Connect bug'.
Quoting a document-history row's 2026 wording as if that was the 2017 name.
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
Join records on ContactId. The integration map room lists the seams.
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.
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.