- Newest
- Most votes
- Most comments
Please focus on SES configuration set settings and IAM permissions such as verify the ses:configuration-set tag in the event data, ensure that your IAM role has the necessary permissions to override suppression settings, you may require to explicitly grant SES permissions to bypass suppression.
https://docs.aws.amazon.com/ses/latest/dg/sending-email-suppression-list-config-level.html
As shown in my original post, the event data has the tag ("ses:configuration-set":["bypass-suppression"]), indicating that the configuration set I use is correct.
We also tried to add the following permissions to the email sender IAM permissions, but it still does not work.
ses:ListSuppressedDestinations
,ses:PutAccountSuppressionAttributes
,ses:PutConfigurationSetSuppressionOptions
.Furthermore, if I change the configuration set to: Override account level settings, with configuration set-level suppression enabled, and reason "complaints only"
It can bypass the account-level suppression list as expected. This suggests that the issue is not related to IAM permissions, and that the "disabled suppression list" setting is simply not functioning as intended. However, our use case requires bypassing both bounces and complaints.
Relevant content
- asked 6 months ago
- asked 10 months ago
- AWS OFFICIALUpdated 6 months ago
hi,
SES is region-specific. Can you double-check that the config set was created in the same region you're sending the email from?
@Malini Agrawal Yes, the config set is created in the same region as the email is sent from.