I’ve done the following steps to configure SES, S3, and IAM users for SES.
Via SES in the us-east-1 region, verified sampledomain.com and added CNAME, MX, and TXT records in Route 53. (Making sure that MX (10 inbound-smtp.us-east-1.amazonaws.com) applies for sampledomain.com
Set email receiving rule, set noreply@sampledomain.com as a recipient email and the action is set to “Deliver to Amazon S3 bucket” (created S3 bucket upon adding the rule and it’s in the same region – us-east-1)
Added noreply@sampledomain.com in the verified entities list
Created email credentials for SES with default rights
Requested AWS to grant the production access and now it’s already in production mode
Tried to send the email from noreply@sampledomain.com to xxx@gmail.com and vice versa. It’s okay to send without any errors in the AWS console and well-received via xxx@gmail.com
The only issue is that there’s no incoming email in the S3 bucket (except the two emails - AMAZON_SES_SETUP_NOTIFICATION and another email to verify the email address- noreply@sampledomain.com)
Please let me know if there’s a step that is missing or how I should troubleshoot this issue.