Accidentally enabled SES Global Deliverability and the charges are still increasing

I understand your concern about the unexpected SES Global Deliverability charges that continue to accumulate even after you disabled the feature. For billing-related issues like this, the best course of action is to add this information as correspondence to your existing support case through the AWS Support Center at https://console.aws.amazon.com/support/. This ensures your case is properly tracked and routed to the billing team who can investigate the charges and assist with your specific situation. When adding correspondence, include details about when you disabled the feature and the timeline of the charges. If you haven't already, you may also want to verify in the SES console that Global Deliverability is fully disabled across all regions where you use SES. Depending on your AWS Support plan, you may have access to faster response times - you can review your support plan options to see if a different tier would better meet your needs for time-sensitive issues like billing concerns.

Hello,

Sorry to hear about the trouble regarding these unexpected charges. I've shared your concerns internally with our Billing team on your behalf.

While I don't have a time frame, I'd recommend keeping an eye on your case for further updates.

- Doug S.

The part of the automatic Production Access discussion that concerns me most is the effect on shared IP reputation.

Even if only a small number of poorly reviewed accounts start sending low-quality or unwanted email, complaints and bounces can affect the same infrastructure used by legitimate SES customers.

That creates a frustrating situation. A business can authenticate its domain correctly, maintain a clean mailing list, follow AWS recommendations and still depend on the reputation of shared IPs used by many other senders.

If automatic approvals are happening at scale, AWS should make sure the quality of those approvals is not creating a wider deliverability problem.

Suspending a bad account later is important, but protecting the shared IP pool before the damage happens is even more important.

Some customers go through a detailed review, provide information about their website and sending plans, and still get rejected. Other accounts seem to receive access automatically with very little delay. I understand that AWS uses internal checks that customers cannot see, and there may be valid reasons for different outcomes. But when the difference is this noticeable, people naturally start questioning how consistent the process really is. The bigger issue is that Production Access affects more than one account. Poor sending can create complaints, bounces, and reputation problems that may also affect customers using shared SES infrastructure. I am not against automatic approvals. I just think the process should be reliable, consistent, and careful enough to protect legitimate senders.