SES Dedicated IP not in used but instead the Shared IP

Question

Hello,

We purchased a one Dedicated IP for our AWS SES service for our ticketing system.

But upon checking with our email service, the AWS SES still uses the Shared IP and not the Dedicated IP provisioned to us.
To add information, we are still in 10% warm up automatically and encountering issues like some recipient not receiving some of the emails/alerts. We are still not in full production, we are doing gradual migration of system that will use this service.

Does the warm up have to do with this? Should we turn to manual warm up and gradually increase the systems that will be using this service? Can you please give me some recommendations and insights for this.

Accepted Answer

Two aspects in your question. Warm-Up applies only to standard dedicated IPs and not managed dedicated IPs. When you purchase a standard dedicated IP for SES, AWS will automatically warm them up on a pre-defined plan. Typically, over 45 days, AWS will increase sending via the dedicated IP until you reach 50,000 messages a day.

Warm up balances sending your messages via the new dedicated IP and existing shared SES IPs, slowly increasing the number of messages that use your dedicated IP over the warm-up period.

This is why you are seeing that the shared IPs are still being used - as you are early in the warm-up plan (10%).

Users not receiving messages in their inbox is a different issue. Here you need to make sure that you are authenticating your outbound e-mails. Use DKIM, SPF and DMARC so that the receiving MTA does not consider the message reputation low - and put it into a SPAM folder, or worse just discard it.

Read how to configure and use e-mail authentication with SES here: https://docs.aws.amazon.com/ses/latest/dg/email-authentication-methods.html

SES Dedicated IP not in used but instead the Shared IP

Relevant content