- Newest
- Most votes
- Most comments
Great! You're on the right track by referencing the AWS CloudFormation documentation for Amazon Connect Campaigns v2 and Customer Profiles segment definitions. To help you get started, here’s a basic outline of what a CloudFormation template for an agentless outbound campaign (v2) might look like. This will include: AWS::ConnectCampaigns::Campaign Required IAM roles and resources Optional: AWS::CustomerProfiles::SegmentDefinition if you're targeting customer profiles AWSTemplateFormatVersion: '2010-09-09' Description: Agentless Outbound Campaign v2
Resources: CampaignRole: Type: AWS::IAM::Role Properties: RoleName: ConnectCampaignExecutionRole AssumeRolePolicyDocument: Version: '2012-10-17' Statement: - Effect: Allow Principal: Service: connect-campaigns.amazonaws.com Action: sts:AssumeRole Policies: - PolicyName: CampaignPolicy PolicyDocument: Version: '2012-10-17' Statement: - Effect: Allow Action: - connect:StartOutboundVoiceContact - connect:DescribeCampaign Resource: "*" MyCampaign: Type: AWS::ConnectCampaigns::Campaign Properties: ConnectInstanceArn: !Sub "arn:aws:connect:${AWS::Region}:${AWS::AccountId}:instance/your-instance-id" DialerConfig: AgentlessDialerConfig: DialingCapacity: 10 OutboundCallConfig: ConnectContactFlowArn: !Sub "arn:aws:connect:${AWS::Region}:${AWS::AccountId}:instance/your-instance-id/contact-flow/contact-flow-id" ConnectQueueArn: !Sub "arn:aws:connect:${AWS::Region}:${AWS::AccountId}:instance/your-instance-id/queue/queue-id" AnswerMachineDetectionConfig: EnableAnswerMachineDetection: false Name: AgentlessCampaignV2 Tags: - Key: Project Value: CampaignDemo ConnectCampaignExecutionRoleArn: !GetAtt CampaignRole.Arn
Before You Deploy: Replace: your-instance-id contact-flow-id queue-id Make sure the IAM role and permissions match your campaign scope. Ensure the region supports Amazon Connect Campaigns v2.
Relevant content
- asked 6 months ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago