- Newest
- Most votes
- Most comments
Hi MageshRaja! 👋
I understand how frustrating it can be when emails aren’t reaching your agents as expected. Let’s troubleshoot this together and get things running smoothly.
Clarifying the Issue
From your description, it seems that:
- SES is enabled and configured properly with verified domains and email addresses.
- S3 CORS policy has been updated.
- Email flow mapping and routing profiles are set.
- Yet, incoming emails are not being received or visible in search tools like Amazon Connect Contact Search or CloudWatch.
Additionally, you’re encountering the "You have created too many email drafts" error when trying to create outbound email tasks.
Key Terms
Here are two important terms to clarify the situation:
- Amazon SES (Simple Email Service): A scalable service for sending and receiving emails in AWS.
- Amazon Connect: AWS’s contact center solution that integrates with SES for handling customer communications.
The Solution (Our Recipe)
1. Check SES Inbound Rule Configuration
- Ensure your Inbound Rules are set to process emails and route them to the desired destination, such as Amazon S3 or Lambda.
- Double-check that the email domain or address you’ve verified in SES matches the one receiving the inbound emails. Misconfigured domains often cause silent failures.
2. Confirm Amazon Connect Routing Rules
- Go to Amazon Connect Contact Flows and ensure emails are mapped properly through:
- Routing Profiles
- Queues
- Flows (Inbound email tasks trigger the correct flow with the agent assignment).
3. Validate Drafts Queue Cleanup
- Since you're receiving the "too many email drafts" error:
- Open the Amazon Connect Contact Control Panel (CCP), and delete unnecessary drafts.
- Ensure the agent’s workspace is refreshed after cleanup. If drafts persist, log the agent out and back in.
4. SES Quotas and Metrics
- Sometimes, SES reaches its daily inbound email limit or runs into restrictions (based on your AWS region or SES sandbox status).
- Go to the SES Dashboard → Sending Statistics to check:
- Delivery Failures
- Quota Usage
- If in sandbox mode, move your SES setup to production to lift sandbox restrictions.
5. Debug with CloudWatch and Event History
- Use Amazon CloudWatch to monitor inbound SES email events. Look for:
- Errors in email delivery.
- Any rejections or message drop issues.
- CloudTrail can help identify if permissions (like SES receive permissions) are causing the problem.
Closing Thoughts
By reviewing SES rules, Connect mappings, and email quotas, you can usually identify and fix silent delivery issues. If SES sandbox restrictions are in play, promoting your domain to production is a quick win. For the draft queue error, cleaning up and refreshing the agent interface should do the trick.
Let us know how it goes! I’m confident these steps will help you get SES emails flowing to your agents seamlessly. 🚀
Wishing you smooth troubleshooting and success ahead!
Cheers, Aaron 😊
answered 2 years ago
@MageshRaja , did you ever find out how to get this set up? My org wants to get this set up and I followed this video: https://www.youtube.com/watch?v=MXuJTHR_-zE&t=850s and then ran into the same exact issues as you. Our domain is verified.
answered a year ago
Relevant content
asked 2 years ago
asked 2 years ago
asked 3 years ago
- AWS OFFICIALUpdated 2 years ago
