After several hours of research and unsuccessful attempts to receive SES email without using an MX record (an additional route was configured via gSuite / Google Apps), here is my best suggestion on how to do this.
Short version
Create a subdomain and specify its MX record on SES after inserting the TXT verification record.
After creating the necessary set of rules for receiving and saving emails with any@sub.domain.com now you can receive the SES email address from any email address that you (even if it is not verified using SES), simply sending your letters to subdomain authorized by SES.
Long version
Unfortunately, it still requires an MX record, but check it out ...
You can create your own subdomain in your main domain and call it anything. In my case, I named it ses.mydomain.com Then I added my newly created subdomain to SES via the Domains link.
Immediately after adding it as a domain for SES, a pop-up window appears displaying the required TXT verification record and MX mail record .
Shortly after assigning these two DNS records to my subdomain, the subdomain is checked and can receive email after setting a few quick rules using rule sets !
Here's the cool part - you can still get SES from the email address of anyone you have access to.
How could you ask?
Just configure the forwarding to the email address you want to send to SES, redirecting it to the SES-enabled subdomain.
Value. If SES can receive email from someone@ses.example.com , but you want it to really receive email from someone-else@example.com , then all you have to do is forward someone-else@example.com to someone@ses.example.com !
Remember that you still need to create the necessary rules for receiving letters. See this AWS blog post for more information .
source share