1 Answer
- Newest
- Most votes
- Most comments
0
Our problem is solved with including the 'X-SES-CONFIGURATION-SET' custom header parameter in the call to SES. But so, the default configuration set seems not to get used when making the call via IAM user
answered 3 years ago
Relevant content
- Accepted Answerasked 4 months ago
- Accepted Answerasked a month ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago