AWS SES Not Delivering to the right S3 Bucket

1. Verify Rule Set Activation:

Ensure that the new SES rule set containing the updated rule to deliver emails to Bucket B is active. SES only processes emails according to the active rule set.

You can check the active rule set in the AWS SES console under Email Receiving > Rule Sets. Ensure that the correct rule set is marked as "Active."

2. Check for Conflicting Rules:

Ensure there are no other active rules or rule sets that might still be directing emails to Bucket A. If there are any other rules targeting the same email address, they might be causing the conflict.

SES processes rules in the order they are listed. Make sure that the rule for Bucket B is higher in the order than any conflicting rules (if applicable).

3. Review Rule Set Configuration:

Double-check the configuration of the new rule set to ensure that the correct email address (X email) is associated with the rule directing emails to Bucket B. Ensure that the "S3 Action" in the rule is correctly configured to point to Bucket B. The configuration should include the correct bucket name, object key prefix (if any), and access permissions.

4. Check for Caching Issues:

Occasionally, changes might take a bit of time to propagate, especially if SES caches configurations. Wait a few minutes after making changes and then test the delivery again.

5. Test the Configuration:

Send a test email to the X email address and monitor both Bucket A and Bucket B.

Confirm whether the email is still being delivered to Bucket A or if it is now correctly being delivered to Bucket B.

6. Log Analysis:

Enable logging for the SES rule set if not already done. This will provide detailed information on why the emails are being routed to Bucket A.

You can also check CloudTrail logs for SES to see the sequence of events and confirm that the rule set was correctly applied.

7. Permissions Check:

Ensure that Bucket B has the correct IAM policies allowing SES to write to it. Misconfigured permissions could cause SES to fall back to the previous configuration or fail silently.

8. Disabling Other Rules:

To isolate the issue, try disabling all other rules and keep only the rule that directs emails to Bucket B. This can help determine if a conflicting rule is the problem.

9. Update SES Permissions:

Verify the IAM role or policy associated with SES to ensure it has the correct permissions to write to Bucket B.

Example IAM Policy for SES to S3:

If you need to update the permissions, here’s an example policy:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "s3:PutObject"
      ],
      "Resource": "arn:aws:s3:::bucket-B-name/*",
      "Condition": {
        "StringEquals": {
          "aws:Referer": "your-ses-identity"
        }
      }
    }
  ]
}

Final Steps:

After making these checks and adjustments, try sending another test email to confirm that the emails are now being correctly delivered to Bucket B. If the issue persists, consider reaching out to AWS Support with detailed logs and configurations to get more targeted assistance.

I have checked all the above and everything is set as per. The other set rules are inactive and the rules within those are disabled. There is permission within the bucket destination set as per above and the email is still being received in bucket A, even though there is no AWS SES rule active that send received emails to bucket A.