- Newest
- Most votes
- Most comments
Hi,
the outbound contact flow should not be relevant for email campaigns. First thing I would check is whether you have followed all the steps in the Enable email for your instance section of the admin guide (including requesting production access for SES and setting up email and attachment storage).
To trouble shoot further, you could enable the the Analytics data lake. The Outbound campaign events table contains details about each delivery attempt.
Based on the information you've provided, it seems that you've set up an outbound campaign for email using Amazon Connect and Amazon SES. However, you're experiencing issues with email delivery and lack of logs in CloudWatch. Let's address this step by step:
-
SES Configuration: You've mentioned that you can send emails manually through SES, which suggests that your SES setup is correct.
-
Campaign Setup: You've followed the steps to create an outbound campaign as per the AWS documentation, which is a good start.
-
Email Domain: You've added an email domain and attached it to your Connect instance, which is necessary for outbound email campaigns.
-
Campaign Analytics: Your campaign shows attempts to send, but no deliveries are appearing in the analytics metrics tab.
-
Contact Flow: The contact flow you've shared seems to be set up, but it's not clear if it's being invoked.
-
CloudWatch Logs: You're not seeing any logs in CloudWatch, which suggests the flow isn't being triggered.
Given these points, here are some potential areas to investigate:
-
Email Message Template: Ensure you've selected a valid email message template when setting up your campaign. The template should be properly configured and approved.
-
Outgoing Email Address: Verify that the outgoing email address you've selected for the campaign is correctly set up and verified in SES.
-
Customer Segment: Check if the customer segment you're targeting in your campaign has valid email addresses.
-
Campaign Limits: Review if you've hit any campaign limits or if there are any throttling issues.
-
Contact Flow: Although you've set up a contact flow, ensure it's correctly associated with your campaign and includes the necessary blocks for email sending.
-
Permissions: Verify that your Amazon Connect instance has the necessary permissions to send emails through SES and write logs to CloudWatch.
-
CloudWatch Log Group: Make sure you're looking at the correct log group in CloudWatch. The naming convention for Connect log groups is typically "/aws/connect/{InstanceId}".
-
Error Handling: Add error handling blocks in your contact flow to catch and log any issues that might be occurring during the email sending process.
If after checking these areas you're still experiencing issues, you may need to contact AWS Support for further assistance. They can help you dive deeper into the specifics of your setup and identify any configuration issues that might be preventing your outbound email campaign from functioning correctly.
Sources
Create an Outbound Campaign - Amazon Connect
Enable email for your Amazon Connect instance - Amazon Connect
Set up Amazon Connect outbound campaigns - Amazon Connect
I have done all of the above , my customer profiles have valid email addresses and are verified in SES , my contact flow us attached with the email.Email template is also setup
When using Amazon Connect in the SES (Simple Email Service) Sandbox environment, you need to follow these steps to send outbound emails:
-
Email Verification: The email address you plan to use for sending outbound emails must be verified in Amazon SES. This is a requirement for the Sandbox environment.
-
Authorization Policy: After verifying the email, you need to add an authorization policy to allow Amazon Connect to send emails through SES. This is done by navigating to: Identities -> Your verified email address -> Authorization
Then, add the following policy:
{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Resource": "<SES identity ARN>", "Action": [ "ses:SendRawEmail", "ses:GetEmailIdentity" ], "Principal": { "AWS": [ "<SLR arn>" ] } } ] }
This policy grants the necessary permissions for Amazon Connect to use SES for sending emails.
-
Service-Linked Role (SLR) ARN: To obtain the SLR ARN:
- Go to the Amazon Connect Distribution settings section on the overview screen
- Click on the Service-linked role
- In the Summary section of the role screen, copy the Service-linked role ARN
-
SES Identity ARN: To obtain the SES Identity ARN:
- Open the Amazon SES console at https://console.aws.amazon.com/ses/
- In the navigation pane, under Configuration, choose Identities
- In the Identities container, select your email address identity
- Copy the ARN
By following these steps and applying the provided policy, you enable Amazon Connect to send emails through SES while in the Sandbox environment.
Hey there, thanks for responding , I added this policy but still i m stuck there . Still my campaign ends up completed with failed attempts . how can i check for any logs or errors to troubleshoot where the things are going wrong as there are no cloudwatch logs and the logs in glue are not being shown
Relevant content
- asked 8 months ago
- asked 5 months ago
- AWS OFFICIALUpdated 4 days ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 24 days ago
I have followed all the steps however ,I am in sandbox in SES , but i am well within sandbox limits to send mails,does that still need to be done ? also i have enabled email services ,i also have attached the s3 bucket for attachment storage , I have enabled analytics data lake in my instance and chosen the correct services for which i need the data for but data from that is not being stored in any s3 bucket or Aws Glue
In my experience, you need to get out of SES sandbox to enable the email channel in Connect. I would try that.