AWS Activate application checklist before you apply.

AWS Activate can be valuable, but a rushed application can create avoidable friction. Before you apply, make sure the company, account, website, and provider details line up.

AWS says eligible startups can apply for up to $100,000 in AWS Activate Credits. It also describes different packages for different startup stages, including Founders and Portfolio routes. The Portfolio route depends on being associated with an AWS Activate Provider and having the provider's Organization ID.

Use this checklist before submitting.

TL;DR

• Use a business email that matches your startup domain.
• Make sure the company website is functional and clearly explains the product.
• Confirm startup age and funding stage fit AWS Activate requirements.
• If using the Portfolio route, get the correct provider Org ID.
• Link the right AWS account and make sure you have admin permissions.
• Explain the actual cloud use case, not just the desire for credits.

1. Confirm which AWS Activate package fits

AWS describes two common paths:

Activate Founders

Usually for earlier-stage startups that are new to AWS Activate Credits. AWS's public guide says Founders eligibility includes being self-funded or pre-Series B, having a functioning company website, and being founded in the past 10 years.

Activate Portfolio

For startups associated with an AWS Activate Provider, such as an accelerator, investor, or startup organization. AWS's guide says this route can provide up to $100,000 in credits and requires the provider's Organization ID.

Do not guess which path applies. If you are provider-backed, ask the provider for the Org ID directly.

2. Use the right email

AWS specifically tells applicants to use a business email address matching the startup's domain for both the AWS Activate profile and credit application.

Avoid:

• Gmail, Outlook, or personal email if the company has a domain.
• Different domains across website, email, and AWS account.
• Applying before the company domain is set up.

Use:

• [email protected]
• [email protected]
• another real company-domain email.

3. Make the website application-ready

Your website does not need to be beautiful, but it should be credible.

It should explain:

• What the company does.
• Who the product is for.
• Why cloud infrastructure matters.
• Whether the product is software-based.
• Basic company/contact information.

Weak websites create review risk. If the site is only a waitlist with no product explanation, improve it before applying.

4. Prepare account access

AWS's application guide says applicants may need to create or link an AWS account, and gives practical reminders like enabling pop-ups and ensuring administrator permissions.

Before applying:

• Confirm the AWS account is active.
• Make sure billing/contact details are current.
• Confirm you can link the account.
• Make sure the person applying has admin-level access.
• Check whether another team member already linked the account to a Builder ID.

5. Prepare the cloud use case

A good application is not just "we are a startup."

Prepare a short cloud use case:

• What are you building?
• Which AWS services do you expect to use?
• Is this MVP, production, AI, data, infrastructure, or customer deployment?
• What will credits help you build or prove?
• What usage do you expect in the next 6-12 months?

If AI is part of the workload, note whether services such as Amazon Bedrock are relevant. AWS says Activate Credits can be used with Amazon Bedrock.

6. Prepare provider details if applying through Portfolio

If applying through Activate Portfolio:

• Get the correct Org ID from the provider.
• Do not share or reuse random Org IDs.
• Confirm the provider relationship is real.
• Check whether the funding round timing matters.

AWS says Org IDs are confidential and must be submitted through the official AWS Activate application page.

What the AWS partner route changes

AWS Activate Portfolio is already partner-linked because it depends on an AWS Activate Provider relationship. Beyond the application itself, AWS also has partner funding and solution-provider programs.

For the startup, the useful part is straightforward:

• A partner can tell you whether Activate Founders, Activate Portfolio, post-Activate support, discounts, migration funding, or funded technical help is the right route.
• If there is a real AWS opportunity, the partner may be paid through AWS-side economics, not by charging you for a basic review.
• If the case is weak, the partner should say that before you waste time.

A partner still cannot guarantee approval, invent an Org ID, or bypass AWS requirements. The case needs to be real.

7. Avoid common mistakes

Common mistakes:

• Applying with a personal email when a business email exists.
• Website does not explain the startup.
• Wrong AWS account linked.
• No admin permissions.
• Applying through Portfolio without a valid provider Org ID.
• Prior AWS Activate credits equal or exceed the requested package.
• Company stage does not match the package.
• No clear cloud use case.

Application checklist

If you already used AWS Activate

Do not submit another generic request before checking the case. If credits are already used, the next path may be:

• AWS post-Activate support.
• Discounts or payment terms.
• Funded technical help.
• Another provider route.
• A project or migration case.

See how to get more AWS credits after Activate.

Sources

• AWS Activate application guide: https://aws.amazon.com/startups/learn/applying-for-aws-activate-credits-a-step-by-step-guide
• AWS Activate credits: https://aws.amazon.com/startups/credits
• AWS Partner funding benefits: https://aws.amazon.com/partners/funding/
• AWS Solution Provider incentives: https://aws.amazon.com/blogs/apn/introducing-new-aws-solution-provider-program-incentives-for-aws-partners/