$100K in AWS credits — who actually gets them, and how (2026).

IWhy $100K is the headline number — and where it sits in AWS's credit math

$100K is the largest single credit pool AWS Activate offers without you needing to be in a specific accelerator cohort or migration program. It sits at the top of the standard credit ladder; the next rung up requires a specialized pathway.

AWS's public Activate page shows credit tiers stepping from $1K (Builders) to $5K (Founders) to "Portfolio for VC-backed companies" with no dollar figure. The reason there's no dollar figure on the Portfolio tier is that it's a discretionary range — the floor is $25K, the typical award is $100K, the ceiling is theoretically higher for outlier situations. Most startups land at exactly $100K because that's the round number AWS reviewers default to.

In dollar terms, $100K covers approximately 18–24 months of AWS spend at typical Series-A burn rates ($4K–$5K/month average across compute, database, networking, and observability). That's deliberate on AWS's part — they want the credits to fund the company through the period when it would otherwise be cost-sensitive. By the time the credits run out, you're committed to AWS infrastructure and a willing paying customer.

There are larger credit tiers — the Generative AI Accelerator runs up to $1M for ~50 startups globally per cohort; MAP funds $200K+ for substantial migrations; EDP gives mid-market and enterprise companies committed-spend discounts. But $100K is the most accessible large credit tier — it doesn't require winning a competitive cohort, doesn't require a $5M existing AWS commitment, doesn't require enterprise sales contracts.

If you're reading this page because you searched "$100K AWS credits," you're likely in the right band. The next sections walk through which route to the $100K is right for your specific situation.

IIThe four routes to $100K — and which one fits

Most "AWS credits" guides only describe one of these routes. The honest answer is that there are four distinct routes to a $100K-class credit pool, with different eligibility criteria, different timelines, and different success rates.

Knowing which one applies to you matters because filing the wrong application wastes 2–4 weeks. The CloudRoute routing logic — when we triage your inquiry — is essentially: which of these four routes is the fastest path to a credit balance for this specific company?

IIIWhat "partner-filed via ACE" actually means, mechanically

Most published guides hand-wave through this. Here's the actual mechanic, in detail, because the difference between Portfolio working (credits in 14 days) and Portfolio failing (silent rejection, no email) often comes down to whether the partner filed correctly.

ACE stands for APN Customer Engagements — it's the gated portal AWS partners use to register customer opportunities. Every legitimate AWS partner with Advanced or Premier tier has ACE access. The Select tier does not always have full ACE submission rights; check whether the partner you're working with does.

When a partner files an ACE record for your credit application, they create a structured opportunity record with these fields:

• Customer name + URL — your company
• Use case description — 1–3 paragraphs the partner writes based on your inputs
• Projected AWS consumption — itemized by AWS service (EC2 / RDS / Bedrock / etc.)
• Engagement type — typically "build" or "migrate" for credit-eligible records
• Estimated deal size — projected annual AWS spend after credits exhausted
• Partner role — what the partner will deliver alongside the credit application
• Funding-source request — which credit pool the partner is requesting from (Portfolio, Build for Startups, Bedrock POC)

AWS's reviewer (typically an AWS partner-development manager) reads the record. They check that:

IVWhat the AWS reviewer is actually looking for

AWS reviewers don't review every application personally; they pattern-match against a checklist. Knowing the checklist tells you why some applications get approved fast, why others get downgraded, and why a small number get rejected outright.

CloudRoute partners have submitted hundreds of these and report the same pattern. The reviewer asks (in order):

• Is this a real company? — Verifiable website + LinkedIn + funding history (Crunchbase or news mentions). 95% of submissions pass this.
• Is the use case AWS-compatible? — Will the workload use AWS services in volume? Not just a static website on S3. Reviewer wants to see EC2/ECS/RDS/Bedrock/Lambda usage in the projection.
• Is the projected spend realistic? — If you project $200K/month of AWS consumption as a Series-A startup with 10 engineers, the reviewer will downgrade your credit award because the projection is implausible. Realistic projections: $3K–$15K/month at Series-A.
• Does the partner have a track record? — Partners with high ACE close rates get fast-tracked. New partners with no track record get extra scrutiny. This is why CloudRoute routes you to partners with > 70% ACE approval rates specifically for the credit pool you're targeting.
• Is the company already an AWS customer? — If yes, the reviewer can see your spend history. If you've been on AWS for 18 months at $4K/month and you're now asking for $100K credits, the math is plausible. If you're brand-new with no AWS history but asking for $100K, the reviewer needs the partner's vouch to compensate.
• Is the company a competitor? — AWS will not fund competitors. Direct competitors (other cloud providers, certain AI infrastructure companies) get rejected. ~2% of applications hit this filter — usually because the founder didn't realize their product overlaps with an AWS service.

VComposing $100K + extras to push toward $150K

The Portfolio $100K is the base. If you also have a clear additive workload, the Build for Startups + Bedrock POC tracks stack on top. Done correctly, the total credit pool reaches $150K without expanding application time materially.

The phrase "stack on top" matters. AWS reviewers will NOT approve $100K of Portfolio + $25K of Build for Startups if both records describe the same workload — that's double-counting. They will approve $100K of Portfolio for general AWS infrastructure + $25K of Build for Startups for a clearly distinct project (e.g., a video transcoding pipeline using MediaConvert) + $25K of Bedrock POC for a clearly distinct AI initiative (e.g., a customer-support agent using Claude Sonnet).

The honest framing: the additive credits only apply if you have additive workloads. Filing extra applications to push the total higher when the actual workload is one product is the most common rejection cause for the secondary tracks. The reviewer will approve Portfolio and silently downgrade Build for Startups to $0.

When CloudRoute routes a Series-A team, the partner has a 15-minute call to confirm the scope of the additive applications — basically, "is there a real second workload here?" If yes, file both. If no, just file Portfolio and stop.

VIThe four routes side by side

VIIWho can't get $100K (and what to do instead)

Not everyone reading "$100K AWS credits" pages will qualify for $100K. Here's the honest list of situations where the answer is smaller — and what to apply for instead.

• You're pre-seed with no institutional funding — Realistic ceiling: $5K self-serve + $25K Founders track (partner-filed, no VC required) = $30K total. Apply for those; the $100K conversation happens after your seed round.
• You're an individual hobbyist / side-project — AWS Activate is for companies. Individual hobbyist projects qualify for the $200 free-tier credits but not Activate. Build the project, incorporate, raise funding, then revisit.
• Your use case is mostly Marketplace SaaS — If your AWS spend is mostly billed-through-Marketplace (Datadog, Snowflake, etc.), Activate credits don't cover Marketplace billings. Realistic credit pool for you: $5K–$25K covering the AWS-native portion. Bill Marketplace SaaS directly via vendor's own portal.
• You're a direct AWS competitor — AWS won't fund alternative cloud providers, competing AI infrastructure, or services that directly substitute AWS-native ones. Reject rate ~100% for direct competitors. Build your product without the credits.
• You're an enterprise / public-sector buyer — Enterprise procurement goes through EDP (Enterprise Discount Program), PPA (Private Pricing Agreement), or Public Sector Programs — not Activate. Talk to your AWS account team directly; expect 8–16-week sales cycles.
• You're international from a country with sanctions — AWS credit programs follow US export-control regulations. Some country/region restrictions apply. If you're in a non-sanctioned MENA / LATAM / Asia country, you're fine. If your country is on the sanctions list, AWS credits don't flow.

VIIIWhat the first 72 hours actually look like

Hour 0 — You submit an inquiry to CloudRoute. Three questions: company name, funding stage, AWS use case (one sentence). Total form time: 90 seconds.

Hour 0–4 — CloudRoute's admin reviews the inquiry and scores it for routing eligibility. Series-A inquiries with clear use cases route within the first business day.

Hour 4–24 — Routed to a vetted AWS partner matching your stack (Heroku-migration, Bedrock-POC, etc.), region (US-East, EU-Central, MENA, etc.), and tier (Advanced or Premier for Portfolio-scale applications). You receive a Calendly link from the partner.

Hour 24–48 — Partner discovery call (30 minutes). They confirm your eligibility, walk through what the credit application looks like for your specific scenario, and outline the timeline. You decide whether to proceed.

Hour 48–72 — If proceeding, you spend ~30 minutes filling in the credit application worksheet (company info, AWS account ID, deck, use case paragraph). The partner submits it through ACE within 24 hours of receiving your inputs.

Day 11–18 — Credits show up in your AWS billing console. You receive an email from AWS confirming the credit issuance and the validity window.