Skip to content

Repeated rejection for AWS Activate credit application

-1

Hello,

I am writing to seek guidance on an issue with my AWS Activate applications. I have been rejected three times (twice for Founders, once for Portfolio) and am struggling to understand the specific reason.

Here is a summary of my experience:

  1. After my initial applications for the Founders tier were rejected, I contacted the Activate support team through the form in the AWS page for three times. They requested:

    • Official documentation of my company's incorporation/registration.
    • A written justification of my use case for AWS Activate Credits.
  2. I replied with our official company registration documents and a detailed plan for how we would use AWS services. I sent this information three times in separate instances, but after sending my reply, I never received a follow-up response from the support team.

  3. Most recently, I applied for the Portfolio tier through a partner organization and was rejected again for not meeting "internal requirements."

I believe I meet all the stated criteria. The only potential issue I can think of is a naming discrepancy:

  • In the "company website" field of the application, I entered the URL for our main service/product, not a corporate website for my company itself. However, I have already mentioned it in the email.

Could this mismatch between the official company name and the service website URL be the cause of the rejections?

I would greatly appreciate any clarification on whether this is the likely issue, and what steps I should take to resolve it for a future application.

Thank you for your time and help.

asked a year ago1.1K views

1 Answer
0

Based on the information provided, there could be several reasons for your AWS Activate application rejections, and the discrepancy between your company name and website URL might indeed be one of them.

AWS Activate has internal requirements that go beyond what's publicly listed in their documentation. Consistency in business information is particularly important - even small discrepancies between your application, company website, and public records can trigger rejection. The mismatch you mentioned between your official company name and the service website URL could definitely be contributing to the rejections.

Here are some common reasons for AWS Activate application rejections:

  1. Inconsistent business information across your application, website, and corporate records
  2. Issues with billing details or payment methods
  3. Account associations with previous policy violations
  4. Incomplete or insufficient documentation to verify your startup's existence

For your next application, ensure that:

  • All business information is consistent across all platforms
  • Your company website clearly reflects your business identity
  • All documentation matches exactly with your application details
  • Your billing profile is complete with a valid payment method

Unfortunately, AWS typically doesn't provide detailed reasons for rejections due to their internal policies. Many applicants face similar challenges with limited feedback. If you decide to apply again, make sure to address the naming discrepancy issue and ensure all your information is perfectly aligned across all channels.

If you continue to face rejections, you might try reaching out to your partner organization (for Portfolio tier applications) to advocate on your behalf, as they may have more direct channels of communication with the AWS Activate team.
Sources
Repeated Rejections for AWS Activate Founders Credits – Need Guidance | AWS re:Post
AWS Activate credits rejected – which “internal requirements” am I still missing? | AWS re:Post
Eligibility criteria for AWS Activate $100K Credit | AWS re:Post

answered a year ago

  • Again they reply to me with almost the same message: "need information to substantiate my startup's existence, and written justification of use case for AWS Activate Credits.". I'm afraid that the same would happen again.

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.