Getting AWS SES Access Denied Again: What Should I Do?

0
0
Asked By TechWiz123 On

I'm in a bit of a bind as we're launching our employee management system next week, but I've been denied access to AWS SES for the third time in a row. We're mainly using AWS for various services like EC2, Amplify, Route 53, and RDS, and our emails are just transactional ones, including account activations and report generation. Despite having set up successful access for other clients in the past, this time AWS hasn't given me specific reasons for the rejection. Can anyone shed some light on what I might be doing wrong or how I can finally get access to SES?

4 Answers

Answered By CloudSavvy77 On

Yeah, the process can be frustrating and often lacks transparency. When we faced similar issues, our test environment got access quickly, but it took ages for the production one. Just be gentle in your communication with AWS and ask for clarification on the reasons for the denials. Sometimes, being polite goes a long way!

Answered By EmailGuru88 On

It sounds like you're doing great things, but maybe there are a few details you're missing. Have you provided specific examples of the emails you'll be sending? Also, setting up bounce back and complaint automation is key—you should be adding emails to a suppression list if necessary. It's crucial to ensure that users confirm their email addresses too. Adding unsubscribe links to your transactional emails (except for password resets) is also a must. Sending a screenshot or even the email templates might help! Good luck!

Answered By AlternativeScribe On

Have you thought about trying other services, like SendGrid or Mailgun? Sometimes it's worth exploring backup options in case AWS continues to give you the runaround. It’s always a good idea to have alternatives lined up!

Answered By KraigE_AWS On

I get your frustration! I've found that specific industries can face more scrutiny from AWS. Check out this FAQ for insights on common reasons requests are rejected: https://go.aws/3EKhkGG. Also, I recommend this blog post for guidance on what to include in your use case description: https://go.aws/42NfFIl. If you're still stuck after that, feel free to PM me your case ID, and I can look into it further!

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.