- Newest
- Most votes
- Most comments
To use Amazon SES as an email sending service for your CRM product, allowing customers to send emails from their own verified domains, you can follow these steps:
-
Domain Verification: Each of your customers will need to verify their domain with Amazon SES. This involves adding specific DNS records (typically CNAME records) to prove domain ownership.
-
MAIL FROM Domain: Configure a custom MAIL FROM domain for each customer. This allows emails to be signed by the customer's domain rather than amazonses.com, improving deliverability and brand recognition.
-
SMTP or API Integration: You can integrate Amazon SES into your CRM using either the SMTP interface or the API. The SMTP interface is easier to implement if you're using standard email libraries, while the API offers more control and features.
-
Sending Authorization: Use Amazon SES sending authorization to allow your application to send emails on behalf of your customers' verified domains. This involves setting up cross-account access or using the Amazon SES API.
-
Monitoring and Reporting: Implement a system to track email deliverability, bounces, and complaints. You can use Amazon SNS in conjunction with SES to receive real-time notifications about email events.
-
Compliance: Ensure your system adheres to anti-spam laws and Amazon SES's acceptable use policy. Implement proper opt-out mechanisms and maintain clean mailing lists.
-
Scalability: Design your system to handle varying email volumes across different customers. Amazon SES has sending quotas that you may need to manage across your customer base.
-
Security: Implement proper authentication and authorization in your CRM to ensure customers can only send emails from their own verified domains.
To achieve this, you'll primarily use Amazon SES for email sending, potentially combined with Amazon SNS for notifications and event tracking. You may also want to consider using AWS SDKs to simplify integration with these services.
Regarding compliance, you'll need to ensure your system complies with regulations like CAN-SPAM, GDPR, and others depending on your target markets. Amazon SES helps with technical compliance (like properly formatted emails and authentication), but you're responsible for content compliance and maintaining good sending practices.
This approach allows you to build a robust email sending service within your CRM, similar to services like MailChimp or ActiveCampaign, while leveraging Amazon's reliable infrastructure.
Sources
Sending email with Amazon SES - Amazon Simple Email Service
Set up email sending with Amazon SES - Amazon Simple Email Service
AWS SES domain identity verification and MAIL FROM configuration | AWS re:Post
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 6 months ago

I got this part but my question is: How can I build something like resend.com did. So they verify each domain with amazon DNS details. Do I have to create individual amazon sub account under organizations? In that case, the compliance (bounce and compliant) and the sending limit will be applied to that account only or not?
If we use organizations - sub-account structure, Can I programmatically create the API credentials for each account from my root account details?