- Newest
- Most votes
- Most comments
The issue you are facing with the AWS SES static IP configuration appears to be a problem with the way the static IP is being utilized. Despite having the static IP configured and reported as 100% utilized, the emails are still being sent through the default SES pool. This suggests an issue with the configuration set-up, as you've created the configuration sets multiple times and added the static IP to the pool. To resolve this, you should verify the configuration set to ensure the static IP is properly associated with it and that the configuration set is being used for all your email journeys. Additionally, you should check the SES sending limits to rule out any restrictions that could be causing the emails to fall back to the default pool. If the issue persists, you may need to reach out to AWS Support for further investigation, or consider using dedicated IP pools instead of a single static IP to provide more flexibility and better control over your email sending reputation.
Relevant content
- asked a year ago
- asked a year ago
- asked 6 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 9 months ago

I have all the configurations set properly and verified. These were already set to use a static IP and dedicated IP pool. I also don't have any SES sending restrictions. Thanks for the respons. I'm reaching out to AWS Support to resolve.
AWS Support responded and did in fact identify and mitigate the issue to prevent this from occurring moving forward. Everything on my side was setup properly. Escalation to support was in fact needed.