Overview
In this workshop, you'll deploy a complete, production-ready Amazon Connect contact center infrastructure using elevai-connect. By the end of this tutorial, you'll have:
Prerequisites
Before you begin, ensure you have the following:
Installed on your machine
python --versionInstalled and configured
Installation guide →Configured with appropriate credentials
aws configureWith permissions for Amazon Connect, IAM, S3, DynamoDB, Lambda, CloudWatch, and related services
Clone the Repository
First, clone the elevai-connect repository to your local machine:
git clone https://github.com/DanBloy/elevai-connect.git
cd elevai-connectSet Up Python Environment
Create and activate a Python virtual environment, then install the required dependencies:
# Create virtual environment
python3 -m venv venv
# Activate virtual environment
# On macOS/Linux:
source venv/bin/activate
# On Windows:
venv\Scripts\activate
# Install dependencies
pip install -r requirements.txt(venv) indicating the virtual environment is active.Configure Pulumi
Initialize Pulumi and create your configuration file:
# Login to Pulumi (use Pulumi Cloud or local backend)
pulumi login
# Copy the example configuration
cp Pulumi.dev.yaml.example Pulumi.dev.yaml
# Initialize your stack
pulumi stack init devpulumi login --localConfigure Your Instance
Edit Pulumi.dev.yaml to customize your deployment. Here are the critical settings you must configure:
# 1. Your AWS region
aws:region: eu-west-2 # Change to your preferred region
# 2. Email addresses for alerts
alerting:
error_email: "your-email@example.com"
billing:
notificationEmail: "your-email@example.com"
# 3. Unique Amazon Connect instance alias
# WARNING: This CANNOT be changed after deployment!
connect:
instanceAlias: your-unique-alias # Must be globally unique
# 4. Identity management type
# WARNING: This CANNOT be changed after deployment!
connect:
identityManagementType: SAML # Options: SAML or CONNECT_MANAGED
# 5. SAML Metadata file (OPTIONAL - can be updated post deployment)
connect:
samlMetadataFile: "./path/to/saml/metadata.xml"
# 6. Monthly budget limit (for email alerts)
billing:
monthlyBudgetLimit: "50" # USDinstanceAlias and identityManagementType are permanent and cannot be changed after the Connect instance is created. Choose carefully!Preview Your Deployment
Before deploying, preview what infrastructure will be created:
pulumi previewThis will show you all the AWS resources that will be created, including:
- •Amazon Connect instance and related resources
- •S3 buckets for recordings, transcripts, and reports
- •DynamoDB tables for Amazon Q knowledge base
- •CloudWatch alarms and SNS topics
- •Lambda functions and IAM roles
- •Kinesis Data Streams for data streaming
- •AWS Budget for cost monitoring
Deploy to AWS
When you're ready, deploy your infrastructure:
pulumi upPulumi will ask you to confirm the deployment. Type yes to proceed.
Verify Your Deployment
After deployment completes, verify your resources:
# View all stack outputs
pulumi stack output
# View specific output
pulumi stack output connect_instance_arnYou can also verify in the AWS Console:
- 1.Open the AWS Console and navigate to Amazon Connect
- 2.You should see your new instance with the alias you specified
- 3.Navigate to CloudWatch → Alarms to see your monitoring setup
- 4.Check S3 to see the created storage buckets
Post-Deployment Manual Steps
Due to AWS API limitations, complete these steps manually in the AWS Console:
Enable Automated Interaction Logs
Navigate to AWS Console → Amazon Connect → Your instance → Flows
View documentation →Enable Lex Bot Management & Analytics
In the same Flows section, enable Lex bot capabilities
View documentation →Verify Next Generation Amazon Connect
Ensure this is enabled (default for new instances)
Configure SAML Authentication (if applicable)
Follow the comprehensive SAML setup guide
View documentation →Congratulations!
You've successfully deployed a production-ready Amazon Connect contact center! Here's what you can do next:
Explore the Documentation
Learn about advanced features, customization options, and best practices
Set Up Amazon Q
Configure AI-powered agent assistance with knowledge base management
Customize Your Deployment
Add custom resources using the /custom folder or Parameter Store
Monitor Your Instance
Understand your CloudWatch alarms and set up alerting workflows
Video Walkthrough
Video tutorial coming soon!
A comprehensive video walkthrough of this workshop will be available here
Need Help?
If you encounter any issues or have questions: