Skip to content

Amazon SES Static IP not being used when sending marketing emails out of Pinpoint? Configurations are all set properly.

0

This is a new static IP that was at 100% about 3 months ago. I have all the configurations set to use this IP and the correct IP pool in it. My Verified identity is also setup under the AWS Pinpoint project these are being sent out of also. There is no email configuration set being used only the subdomain.

However, when sending emails out they are being sent using the ses-default-dedicated-pool of static ips.

I have created the configuration sets 2 times and added the static IP again from the pool to see if it would fix it. The emails lists I have been using are cleaned from hard bounces and verified. These lists are put into 7 different email journey streams as I'm trying to build our sending reputation up for 3-4 different domains.

I have seen the ses-default-dedicated-pool of static ips being used in my Gloackapps testing and my DMARC tests.

The issues still is not resolved. please advise.

1 Answer
0

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.

answered a year 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.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.