Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

"AWS SES Production Access Denied Despite Legitimate Use Case - Need Human Review"

-1

"I'm a senior software engineer with 8+ years of experience. I've been using AWS for 2+ years and built an email campaign management platform over 3 years specifically for AWS ecosystem.

My SES production access request was rejected with generic automated responses despite providing:

  • Verified domain
  • LinkedIn profile
  • Stack Overflow Profile (Top 2% Spring Framework contributor)
  • Professional background at working with AWS daily
  • Detailed use case and compliance measures

My personal account is 3 years old on AWS, i am testing AWS SES for past 3 months in the sandbox, i have my domain registered as well as multiple gmails and hotmails for testing purposes. After 3 months of testing, I wanted to move to production, and I would be perfectly fine by being denied access due to "xyz", but denial without any explanation makes no sense to me. Is it because I do not have a website? I also asked for guidance on "what i need to do to meet the requirements"

REQUEST FOR SPECIFIC GUIDANCE:

Could you please provide specific guidance on what additional steps I can take?

For example:

  1. Do I need to provide business registration documentation?
  2. Should I create a business website at coon-solutions.com?
  3. Are there specific compliance certifications required?
  4. Should I start with an even lower limit (25 emails/day)?
  5. Is there a probationary monitoring program available?
  6. What documentation would demonstrate legitimacy?

WILLINGNESS TO ADAPT APPLICATION FOR AWS REQUIREMENTS:

I want to emphasize that my entire application was designed specifically to run on the AWS ecosystem from the ground up. If there are any aspects of my application, use case, or implementation that need to be changed or modified to meet AWS SES requirements, I am more than willing to make those changes.

This includes:

  • Modifying my application architecture or workflow
  • Implementing additional monitoring or reporting features
  • Adding extra compliance or safety measures
  • Changing my sending patterns or volume approach
  • Adjusting my user onboarding or verification processes
  • Any other modifications AWS recommends or requires

But this part of my question was completely ignored I just got a generic "We made this decision because we believe that your use case would impact the deliverability of our service and would affect your reputation as a sender. We also want to ensure that other Amazon SES users can continue to use the service without experiencing service interruptions."

Case ID: 176176175800136

I believe this is an automated false positive. I'm requesting human review of my case. I'm a legitimate developer, not a spammer.

Is there any way to escalate this for actual human review?"

Since i was reject how long do i need to wait to reapply again for production?

Topics
Application IntegrationFront-End Web & MobileBusiness Applications
Tags
Amazon Simple Notification Service (SNS)Amazon Simple Email Service
Language
English

asked a year ago329 views

4 Answers
0

Thank you Isac for taking the time to provide me an answer. Can you please tell me what do you mean by "Please pursue your use case review and approval via that case."? I am not asking an approval from anyone here, I am simply asking how can I provide all information, or get answers for my rejections from the real human being instead of a bot. Do i resubmit again a request for a production as I did before? Where should I pursure my use case? What can I do differently to get the production approval? Do I need to submit my email traffic from SendGrid provider to which I switched to prove that I am not a security issue and that I do not get any bounces and that I am not flagged as a spammer?

answered a year ago

  • Isaac Behrens EXPERT
    a year ago

    You refer to support case 176176175800136 in your post. I would update that requesting more information and request either a phone call or web chat to get to a person. If you cannot do it from that case, open a new support case with the information and again, request either call back for web chat to get connected immediately to a support engineer.

0

Hello Isaac, thank you again. The whole point of my question was "Is there any way to escalate this for actual human review?" When you say "requesting more information" I did that via ticket, which was completely ignored as I stated in my initial post. HOW can i request a phone call or a web chat to get to a person once I open a new support ticket, because I was under impression that any request will be met with a bot on the side of AWS. Thank you again.

answered a year ago

0

re:Post is a public forum for advice and guidance between community members. You list a support case in your post. Please pursue your use case review and approval via that case. No one on re:post will be able to provide approval – that must come via the support organization.

I know this is not the answer you are looking for here, but it is the right/only course of action to guide you to resolution.

AWS
EXPERT

answered a year ago

0

Thank you Isaac, based on the quick glance that I did, this seems to be available for a paid tier support which I can activate trial for a 2 months, I think the reason why I did not do this in the beginning is because I did not have activated paid support from AWS. Thank you so much, I will update the question with the situation and further development.

answered a year ago

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.

Relevant content