How aws-samples/amazon-connect-workshop works
Project Type and Purpose
• This is a “serverless telephony” workshop repository demonstrating how to build a modern contact center using AWS services (Amazon Connect, Amazon Lex, AWS Lambda, DynamoDB, SQS).
• It provides CloudFormation templates (full-template.yml), contact-flow definitions, a pre-built Lex bot (ConnectBot.zip), and instructions to wire up an end-to-end IVR and callback system.
a. Amazon Connect Instance
• Telephony front-end (Contact Control Panel / CCP)
• Hosts Contact Flows imported from the contact-flows/ folders
b. Amazon Lex Bot (“ConnectBot”)
• Conversational router for voice intent (WaitOnHold, CallBack, Emergency)
c. AWS Lambda Functions (deployed via CloudFormation)
• GetHotMessageLambda
• ContactLookupLambda
• ContactRouterLambda
• PutContactInQueueLambda
• InitiateOutboundDialLambda
d. DynamoDB Tables
• ContactHistoryTable (tracks caller status)
• HotMessageTable (stores dynamic messages)
e. SQS Queue
• OutboundDialQueue (triggers outbound survey calls)
f. IAM Roles & Policies
• Permissions linking Connect → Lambda, Lex, SQS, DynamoDB
g. CloudFormation Stack
• Orchestrates the creation of the above resources
Relationships and Data Flows
• Inbound call arrives at Amazon Connect
→ EntryPoint Contact Flow
→ Invoke GetHotMessageLambda
→ Invoke ContactLookupLambda
→ Ask user via Amazon Lex
→ Branch to one of:
• InboundCallRouter
• InboundLexRouter
• TransferToQueue or TransferToCallbackQueue
• OnCallFlow (Invoke ContactRouterLambda)
• When a caller opts for callback:
→ PutContactInQueueLambda posts to OutboundDialQueue
→ SQS triggers InitiateOutboundDialLambda
→ InitiateOutboundDialLambda calls Connect outbound survey flow (CallerSurvey)
• Lambdas interact with DynamoDB tables to read/write caller state or hot messages.
Architectural Patterns and Principles
• Serverless microservices: each Lambda handles a single responsibility
• Event-driven: SQS queue triggers asynchronous outbound calls
• Configuration-as-code: CloudFormation defines infra
• Clear separation of concerns:
• Telephony (Connect) vs. Conversational AI (Lex) vs. Business logic (Lambda) vs. Data (DynamoDB / SQS)