You are halfway through your AWS Activate credits application when a field stops you cold: “Organization ID.” You check your AWS console. Nothing. You search your inbox. Still nothing.
That is because the AWS Activate Org ID does not live inside your AWS account at all. It belongs to the organization that backs your startup, and it unlocks the larger credit package that provider has arranged with AWS.
The confusion is common because AWS has several look-alike identifiers. There is the 12 digit account ID, the AWS Organizations ID, and the Activate Org ID. They have nothing to do with each other.
This guide clears it up. You will learn:
- What the AWS Activate Org ID is, and what it is not
- How it differs from your AWS account ID and AWS Organizations ID
- Where to find an Org ID, and what to do if you do not have one
- A step by step path through the application, with the requirements AWS lists
- The mistakes that delay credits, and how to avoid them
Every claim about AWS programs links to AWS’s own pages. Credit amounts and rules change, and AWS’s own pages do not always show the same maximum, so confirm the current numbers before you plan your budget around them.
What Is the AWS Activate Org ID?
The AWS Activate Org ID is a unique, confidential, case sensitive code that identifies an AWS Activate Provider, such as a venture capital firm, accelerator, or incubator. Startups linked to that provider enter it during the Activate Portfolio application so AWS can match them to the provider’s credit package.
AWS’s own credits FAQ puts it plainly. Each venture capital firm, accelerator, incubator, or other startup-enabling organization that is an Activate Provider has its own Org ID. The code identifies the provider, not your startup.
What the Org ID Actually Does
Think of it as a membership key. It tells AWS that your startup belongs to a trusted network, and that network has an agreement with AWS about credits.
- It unlocks the Activate Portfolio package, which offers larger credits than the self-funded route.
- It lets AWS apply the credit level your provider has arranged.
- It is not needed for the Activate Founders package, which is for startups with no provider.
AWS adds an important warning. An Org ID is not a promotional code and should not be shared publicly. Treat it like a password for a perk.
Org ID vs AWS Account ID vs AWS Organizations ID
This is where most people get stuck. Three different identifiers sound similar, yet they serve unrelated purposes.
| Identifier | What it identifies | Format | Where it comes from |
| Activate Org ID | An Activate Provider (VC, accelerator, incubator) | Unique, case sensitive code | Your provider |
| AWS account ID | One AWS account | 12 digits | Your AWS account |
| AWS Organizations ID | A group of AWS accounts managed together | “o-” plus 10 to 32 lowercase letters or digits | The AWS Organizations service |
The formats come from AWS’s documentation. The account identifiers page describes the AWS account ID as a 12 digit number. The AWS Organizations API reference says an organization ID is “o-” followed by 10 to 32 lowercase letters or digits. A management account, which controls an organization, is just an AWS account with its own 12 digit ID.
None of the steps in AWS’s Activate guide ask for your AWS Organizations ID. The application asks you to link your startup’s primary AWS account, and it asks the provider’s Org ID if you choose the Portfolio package.
A Simple Way to Remember the Difference
- Account ID: the address of your AWS account.
- AWS Organizations ID: the label on a folder that holds several accounts.
- Activate Org ID: the key your investor or accelerator hands you.
If you are looking inside the console for the Activate Org ID, you will not find it. It always comes from outside.
Who Are AWS Activate Providers?
AWS works with a large network of accelerators, angel investors, venture capital firms, and other startup-enabling organizations. On its credits page, AWS lists names such as Sequoia, Andreessen Horowitz, Y Combinator, Greylock Partners, Carta, and Brex as notable providers. The list is not complete, and AWS describes it as only a sample.
Providers manage their relationship through AWS’s Activate Providers program, which also explains how organizations can apply to become a provider. AWS mentions a tool called Provider Central that helps providers invite startups to join Activate.
If your investor or program is not on the featured list, it may still be a provider. Ask them directly.
Key Terms in Plain English
A few more names appear during the application, and they are easy to mix up.
- AWS Builder ID: your personal sign-in profile for AWS tools. AWS says it stays with you across jobs and organizations, so use a personal email for it.
- AWS Activate profile: a one time profile about your startup. Use your business email here.
- Activate Credits: promotional AWS credits that offset eligible charges. They are subject to AWS’s promotional credit terms.
- Activate Provider: the VC, accelerator, or startup organization that holds an Org ID.
- Management account: the AWS account that controls an AWS Organizations setup. It has a normal 12 digit account ID and is not the same thing as the Activate Org ID.
- Paid Tier Plan: the AWS account plan AWS lists as a requirement on its credits page.
Where to Find Your AWS Activate Org ID
The short answer: ask your provider. AWS says the Org ID should be given to you by your Activate Provider, and that startups linked to a provider who lack the code should contact that provider directly. AWS does not hand out Org IDs from your account or through a public lookup.
Where to Look
Providers share the code privately, so the route depends on who backs you. These are the usual places to check:
- Your welcome email or onboarding pack from the accelerator, investor, or startup program
- The program’s member portal or perks page, if your provider runs one
- Your program manager, investor relations contact, or platform team
- Any internal channel the provider uses for member benefits
When you ask, be specific. Say you are applying for the AWS Activate Portfolio package and need the provider’s Org ID for the application.
What to Do If Your Org ID Does Not Work
AWS advises contacting your provider if a code appears invalid. Before you do, run through the basics:
- Check capitalization. The code is case sensitive, so “aB3” and “Ab3” are different.
- Paste it cleanly. Copy it from the source and remove any extra spaces.
- Use the official page. AWS says Org IDs must be submitted through the official AWS Activate application page, not through links sent by strangers.
- Confirm your affiliation is current. If you left a program or switched investors, ask whether you still qualify.
- Reach out for help. If the provider confirms the code is right, contact AWS Activate Support.
What If You Do Not Have an Org ID?
You still have options, and none involve guessing a code.
- Apply for the Founders package. It is designed for self-funded startups and does not require an Org ID. AWS lists it at $1,000 in credits, and says select startups may qualify for up to $5,000 over time.
- Join a provider’s program. If an accelerator or investor you work with is an Activate Provider, ask for their code.
- Come back later. AWS says you can apply again for a higher amount if you still meet the requirements and have not reached the lifetime credit cap.
AWS explains the logic in its step by step application guide: without an Org ID, you are initially eligible for the Founders package, and with one, you are eligible for that provider’s specific package levels.
Credit Amounts: Read the Numbers Carefully
AWS’s own pages currently show different maximums for the Portfolio package. The AWS credits page lists up to $100,000, while the June 2026 application guide lists up to $200,000 for provider-backed startups. The Founders package appears as $1,000 on both.
The practical lesson is simple. Your provider decides which package level you receive, so ask them for your specific amount instead of relying on a headline figure.
What Activate Credits Do and Do Not Cover
Credits offset charges for eligible AWS services, including many of the 200 plus services AWS offers. They also work with third party foundation models on Amazon Bedrock.
AWS says they cannot be applied to:
- AWS Managed Services
- AWS Marketplace, except third party foundation model charges on Bedrock
- AWS Professional Services, AWS Training, and AWS Certification
- Amazon Route 53 domain name registration or transfer
- Cryptocurrency mining
- Upfront fees for Savings Plans and Reserved Instances
Credits apply to new usage, not past bills. You cannot choose which services use them, and they usually expire within one to two years, depending on the package.
AWS Activate Eligibility: Founders vs Portfolio
Whether you need an Org ID depends on which package you apply for. AWS describes two tiers, and the requirements below come from its credits page and its June 2026 application guide.
| Requirement | Activate Founders | Activate Portfolio |
| Org ID | Not required | Required, from your provider |
| Funding | Self-funded | Provider-backed, pre-Series B |
| Latest funding round | Not applicable | Within the last 12 months, if applicable |
| Credit history | New to Activate credits | Has not received Activate credits of equal or greater value |
| Company age | Founded in the past 10 years | Founded in the past 10 years |
| Website | Fully functioning company website | Fully functioning company website |
| AWS account | On the Paid Tier Plan | On the Paid Tier Plan |
| Credits | $1,000, with up to $5,000 possible over time for select startups | Set by your provider, up to the maximum AWS lists |
The credits page also mentions that a company profile can stand in for a website. When two AWS pages differ, follow the stricter one to stay safe.
How to Apply for AWS Activate Credits Step by Step
This is the process AWS lays out in its step by step guide. Have your Org ID ready before you start if you plan to apply for the Portfolio package.
- Sign in or create an AWS Builder ID. Select Apply Now on the AWS credits page. Use a personal email for the Builder ID, then verify it through the confirmation email.
- Complete your Activate profile. Use a business email that matches your startup’s domain. AWS says consistent domain information helps validate your application.
- Choose your credit tier. Pick Founders for self-funded startups or Portfolio for provider-backed ones. For Portfolio, enter your provider’s Org ID here.
- Provide startup details. Describe your product, target market, and traction. State your current funding stage and the date of your most recent round, using the latest date if a round had several closings.
- Link your AWS account. Connect your startup’s primary AWS account to your Builder ID. You need administrator permissions, either as the root user or an IAM user or group with admin level access.
- Verify the account. Select the verification button in the AWS Management Console. When it works, you will see that the accounts linked successfully.
- Review and submit. Double check funding stage and email domains before you submit. A confirmation email follows.
Tips for Linking Your AWS Account
AWS flags a few common snags at step five:
- Enable pop-ups in your browser.
- Make sure you have admin permissions.
- Only one Builder ID can link to an AWS account at a time. If you get an error, check whether a colleague already linked it, and unlink it from the AWS Activate profile if so.
- Confirm the account is active. If it is inactive or suspended, contact AWS Activate Support first.
Choose carefully which account you link. AWS notes that credits typically sit at the AWS account level.
What Happens After You Submit
- Timing. AWS says processing usually takes 7 to 10 business days, with the outcome sent by email.
- Tracking. The Credit Application Status page shows pending and past applications from the last 18 months.
- Credits arrive automatically. After the approval email, credits deposit into your account. You can see the balance and expiration date in the AWS Billing and Cost Management console within 3 to 4 hours.
- No edits after submission. If you spot a mistake, AWS says to cancel the application, unlink your AWS account from the Builder ID, and submit a new one with the correct details.
- Reminders. AWS emails you before credits expire and as they run low.
If you wait more than 10 business days, check your spam folder and the status page, then contact AWS Activate Support.
Why AWS Activate Applications Get Delayed or Rejected
In the AWS pages reviewed for this guide, AWS does not publish a full list of rejection reasons. What it does publish is a set of requirements and warnings. Missing any of them is the most likely cause of a delay or a no.
- Mismatched email domains. AWS says to use a business email matching your startup’s domain for both the profile and the application.
- Wrong funding details. AWS says accurate funding stage and most recent funding date are essential to the assessment.
- Past credits. Portfolio applicants must not have received Activate credits of equal or greater value.
- Stage and age limits. Portfolio startups must be pre-Series B and founded in the past 10 years.
- No working website. AWS asks for a fully functioning company website.
- A problem AWS account. An inactive or suspended account, or one not on the Paid Tier Plan, can block the process.
- An account already linked elsewhere. Only one Builder ID can link to an AWS account at a time.
- An invalid Org ID or ended affiliation. If the code looks wrong, your provider can confirm it.
You can follow each application through the Credit Application Status page, which AWS says includes details on each stage of the review.
Common Mistakes to Avoid
Most avoidable problems come from confusion about what the Org ID is and how credits work.
- Entering the wrong identifier. Your 12 digit account ID and your AWS Organizations ID are not the Activate Org ID.
- Sharing the code publicly. AWS calls Org IDs confidential and says they are not promotional codes. Be wary of anyone offering to sell one.
- Using a personal email in the profile. Use your startup’s business domain for the profile and application.
- Linking the wrong AWS account. Credits typically sit at the account level, so link your primary account.
- Assuming credits cover everything. Marketplace purchases, domain registration, and upfront Savings Plans or Reserved Instance fees are excluded, as are AWS Managed Services.
- Quoting a headline amount. Your provider sets your package, so confirm your actual credit level.
- Letting credits expire. Mark the expiration date and check the billing console regularly.
One honest limit applies here. An Org ID gives you the right to apply, not a guarantee of approval. AWS reviews each application against its requirements.
Which Path Is Right for You?
Use this quick guide to decide where to start.
- You are self-funded and have no provider: apply for the Founders package. No Org ID is needed.
- An accelerator, VC, or angel group backs you: ask them whether they are an Activate Provider and request their Org ID for the Portfolio package.
- You hold an Org ID but your startup is past Series B: you likely fall outside the Portfolio stage limit, so check the current requirements or talk with your AWS account team.
- You already received some credits: you may be able to apply again for a higher amount, as long as you still qualify and stay under the lifetime cap.
- You are an AI startup scaling past the tiers: AWS says additional credits above $200,000 exist and points you to your Account Manager.
Practical Examples
These three scenarios are illustrative, not real customer cases.
The accelerator cohort. A founder joins an accelerator that is an Activate Provider. The program manager shares the Org ID in the welcome pack. The founder selects Portfolio, enters the code exactly as written, and links the company’s primary AWS account.
The bootstrapped builder. A solo founder has no investors. She applies for the Founders package with her company website and business email. Later, after joining a provider’s program, she asks for the Org ID and applies again for a higher amount.
The mistyped code. A founder pastes an Org ID with a lowercase letter that should be uppercase. The application fails the check. A quick copy from the provider’s original message fixes it.
Make Your Credits Last
Credits are generous, but they are not endless. Once approved, track your balance in the AWS Billing and Cost Management console and set alerts with AWS Budgets. AWS also publishes cost management guidance for startups for after your credits land.
Remember that once credits run out or expire, you pay standard rates for ongoing services.
Conclusion
The AWS Activate Org ID is simpler than it looks once you know where it comes from. It is a confidential, case sensitive code issued by your Activate Provider, used only for the Portfolio package, and unrelated to your AWS account ID or AWS Organizations ID.
Ask your provider for it, enter it through the official AWS application, and match your details carefully. If you have no provider, the Founders package is your starting point. Gather your documents, confirm the current credit levels on AWS’s pages, and apply with confidence.
