I’m trying to configure AWS SES to receive emails and store them in an S3 bucket, but it’s not working as expected. Here’s what I’ve done so far:
Configuration Details
Domain verification: Successfully verified in SES.
Rule set created: The recipient pattern (*@sub.domain) is correctly specified.
S3 action configured: The correct bucket name is provided in the SES rule.
IAM Role Permissions: Granted SES permissions to write to the S3 bucket.
MX record setup: Confirmed via dig and nslookup:
sub.domain mail exchanger = 10 inbound-smtp.ap-southeast-2.amazonaws.
SES Notification Received: AMAZON_SES_SETUP_NOTIFICATION confirms the setup.
S3 Bucket Policy
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "AllowSESPuts",
"Effect": "Allow",
"Principal": {
"Service": "ses.amazonaws"
},
"Action": "s3:PutObject",
"Resource": "arn:aws:s3:::<S3-BUCKET-NAME>/*",
"Condition": {
"StringEquals": {
"AWS:SourceAccount": "<AWS-ACCOUNT>"
},
"StringLike": {
"AWS:SourceArn": "arn:aws:ses:region:<AWS-ACCOUNT>:receipt-rule-set/<RECEIPT-RULE-SET>:receipt-rule/<RECEIPT-RULE>"
}
}
}
]
}
Despite everything being set up correctly, emails sent to [email protected] are not appearing in the S3 bucket. There are no errors, and the SES rule set appears active.
Troubleshooting So Far
MX record verification: Confirmed via terminal that it resolves to AWS SES.
CloudTrail Logs: No s3:PutObject failures found.
Tried sending test emails via Gmail and Hotmail and in response I get mailbox not found and no S3 objects created.
What could be missing in my setup? Are there any additional debugging steps I should try?
Any help is greatly appreciated!
I’m trying to configure AWS SES to receive emails and store them in an S3 bucket, but it’s not working as expected. Here’s what I’ve done so far:
Configuration Details
Domain verification: Successfully verified in SES.
Rule set created: The recipient pattern (*@sub.domain.com) is correctly specified.
S3 action configured: The correct bucket name is provided in the SES rule.
IAM Role Permissions: Granted SES permissions to write to the S3 bucket.
MX record setup: Confirmed via dig and nslookup:
sub.domain.com mail exchanger = 10 inbound-smtp.ap-southeast-2.amazonaws.com.
SES Notification Received: AMAZON_SES_SETUP_NOTIFICATION confirms the setup.
S3 Bucket Policy
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "AllowSESPuts",
"Effect": "Allow",
"Principal": {
"Service": "ses.amazonaws.com"
},
"Action": "s3:PutObject",
"Resource": "arn:aws:s3:::<S3-BUCKET-NAME>/*",
"Condition": {
"StringEquals": {
"AWS:SourceAccount": "<AWS-ACCOUNT>"
},
"StringLike": {
"AWS:SourceArn": "arn:aws:ses:region:<AWS-ACCOUNT>:receipt-rule-set/<RECEIPT-RULE-SET>:receipt-rule/<RECEIPT-RULE>"
}
}
}
]
}
Despite everything being set up correctly, emails sent to [email protected] are not appearing in the S3 bucket. There are no errors, and the SES rule set appears active.
Troubleshooting So Far
MX record verification: Confirmed via terminal that it resolves to AWS SES.
CloudTrail Logs: No s3:PutObject failures found.
Tried sending test emails via Gmail and Hotmail and in response I get mailbox not found and no S3 objects created.
What could be missing in my setup? Are there any additional debugging steps I should try?
Any help is greatly appreciated!
Share Improve this question asked Feb 8 at 9:46 Shahryar FarajiShahryar Faraji 1681 gold badge2 silver badges12 bronze badges1 Answer
Reset to default 0The issue was that my SES recipient condition was set to *@sub.domain.com
, but I was sending emails to [email protected]
, which didn’t match exactly. The fix was simply setting sub.domain.com
as the recipient condition.