Most of the AWS credit money — the $100K Activate Portfolio tier and everything above it — never appears on the public Activate page and cannot be claimed through the self-serve form. It is unlocked by an AWS partner who files a structured opportunity record on your behalf through a gated program called ACE. This is the definitive reference on what "partner-filed" actually means: the exact mechanic, what the partner submits, what AWS reviewers check, the timelines, the approval and rejection patterns, and who should use it.
The phrase appears in dozens of AWS-credit guides and almost none define it precisely. Partner-filed is not a marketing label — it describes a specific submission path with a specific portal, a specific record format, and a specific reviewer on the other side.
There are two ways a credit request reaches AWS. The first is the public, self-serve route: you go to the AWS Activate page, fill in a short form, and a small credit amount is granted more or less automatically. The second is the partner-filed route: an authorized AWS partner submits a structured opportunity record on your behalf through a gated business portal, an AWS person reviews it, and a larger credit award is issued against that record. "Partner-filed" is shorthand for the second path.
The distinction matters because the two paths reach different credit ceilings. The self-serve form is built for volume and speed, so AWS keeps the amounts it can grant low — typically the $1K Builders or $5K Founders tier. The larger tiers (the $25K and $50K stacks, and the headline $100K Activate Portfolio award) deliberately have no public form. AWS gates them behind either a venture-capital firm with Portfolio Sub-Program access or an AWS partner with ACE submission rights. If you have searched for the Portfolio application and come up empty, that is by design: the application is not a web page you can find, it is a record a partner files for you.
It helps to separate three things that often get conflated. The credit program is the pool of money and its rules (Activate, Activate Portfolio, Build for Startups, the Generative AI accelerators, MAP). The submission path is how a request enters AWS (self-serve form, partner via ACE, or VC via the Portfolio Sub-Program). The reviewer is the AWS person or automated check that approves the award. "Partner-filed" is purely a statement about the submission path. The same Portfolio program can be reached partner-filed or VC-filed; the program is identical, only the door is different.
One more clarification, because it is the single most common misconception: partner-filed does not mean the partner is selling you the credits, marking them up, or taking a cut of them. The credits land in your AWS account at full face value and apply directly against your AWS invoice. The partner is compensated entirely separately, by AWS, for the engagement work attached to the record — never out of your credit balance. We unpack that economic structure in section VII.
It would be simpler for AWS to put a $100K button on a web page. It does not, and the reason is rational once you see the problem AWS is solving: distributing large discretionary credits to strangers, at scale, without being defrauded or wasting budget on companies that will never become real customers.
A credit is a future revenue commitment. When AWS issues $100K of credits, it is betting that the recipient will consume AWS services, run out of credits in 18–24 months, and convert into a paying customer spending well above $100K over its lifetime. The bet only pays off if the recipient is a real, funded, AWS-committed company building something that actually consumes infrastructure. AWS needs a cheap, scalable way to filter for exactly that profile — and it cannot afford to manually interview every applicant.
The partner is that filter. An AWS partner with Advanced or Premier tier has a commercial relationship with AWS, a track record of registered opportunities, and a financial incentive to only bring forward deals that close. When a partner files an ACE record, they are putting their own standing on the line: partners with low close rates lose fast-track privileges and get extra scrutiny on future submissions. So the partner pre-screens the customer before they ever submit. AWS effectively outsources the first round of due diligence to a party that has skin in the game.
This also explains why the venture-capital route exists in parallel. A VC with Portfolio Sub-Program access is performing the same vouching function — "this is a real company we funded" — through a different relationship. From AWS's point of view, a tier-1 VC and an Advanced-tier partner are interchangeable trust signals. That is why a startup can reach the identical $100K Portfolio tier either through its investor or through a partner. The credit is the same; AWS just needs one credible party to attest that the recipient is worth the bet.
The gating has a second benefit for AWS: it attaches expertise to the money. A partner-filed record usually carries a scope of work — a migration, a Well-Architected remediation, a Bedrock proof-of-concept. AWS would rather fund a startup that has a competent partner helping it deploy correctly than hand cash to a team that will misconfigure everything and churn. The credit and the engagement travel together, which is why so much partner-filed credit money is also AWS-funded engagement money (covered in the MAP and POC cornerstones linked at the end).
AWS gives the large credit tiers to partners and VCs to file because both are cheap, scalable trust signals. The self-serve form has no human vouching for you, so AWS caps it low. A partner-filed record comes with a vouch and usually a scope of work — so AWS is willing to put real money behind it.
ACE — APN Customer Engagements — is the portal AWS partners use to register customer opportunities. Almost every published guide hand-waves through this. Here is the actual flow, because the difference between an application that lands credits in two weeks and one that dies silently usually comes down to whether the partner filed the record correctly.
APN is the AWS Partner Network; ACE is the opportunity-registration system inside it. A partner with Advanced or Premier tier has full ACE submission rights. Select-tier partners do not always have complete submission rights for credit-bearing records — which is one reason the choice of partner matters, and why a routing layer screens for it. When a partner files for you, the lifecycle of the record looks like this:
Before anything is submitted, the partner confirms the basics: that you are a real, incorporated company; that your funding stage and use case fit the tier being requested; that your workload will consume AWS services in volume; and that your product does not directly compete with an AWS service. This is a short call. A good partner kills doomed applications here rather than burning two weeks on a record that will be rejected.
The partner opens a new ACE opportunity and fills in the structured fields (enumerated in the next section). The most consequential field is the free-text use-case description — one to three paragraphs the partner writes from your inputs, describing what you are building, which AWS services it will use, and the scope of work the partner will deliver. This is where the application is won or lost; a vague, generic write-up gets downgraded, a specific and AWS-aligned one gets approved at the full amount.
The partner submits the record and flags which funding source they are requesting from — Activate Portfolio, Build for Startups, Bedrock / generative-AI POC, or a migration program. A single engagement can carry more than one record if there are genuinely distinct workloads (this is how stacking works, covered in section VI). The submitted record now sits in AWS's queue.
An AWS partner-development manager (PDM) — or, for routine records, an automated first pass — reviews the opportunity against the internal checklist detailed in section V. They approve at the requested amount, approve at a reduced amount, ask the partner a clarifying question, or reject. Clean records from credible partners increasingly clear with little friction; borderline records bounce back to the partner for more detail.
On approval, AWS issues the credits against your AWS account ID. They appear in the Billing console under credits, with a face value and an expiration window (commonly 12 months for smaller tiers, up to 24 months for Portfolio). They auto-apply to your monthly invoice until exhausted or expired. You receive an email from AWS confirming the issuance — that email, not the partner's word, is the moment the credits are real.
An ACE credit record is a structured opportunity, not a free-form email. Knowing the fields tells you exactly what information the partner needs from you — and why the 30 minutes of founder input is mostly about supplying clean inputs for these fields.
A credit-bearing ACE opportunity record contains, at minimum, the following fields. The partner completes all of them; your job is to supply accurate inputs for the company-specific ones.
Two of these fields do almost all the work. The use-case description is where a generic submission ("startup wants to use AWS") gets downgraded and a specific one ("B2B fintech migrating its core ledger from Heroku to ECS on Fargate, adding a Bedrock-backed support agent on Claude Sonnet, projecting $6K/month at 12 months") gets approved at full value. The projected-consumption itemization is where implausible numbers get an application cut — a 10-engineer seed company projecting $200K/month of spend signals either a misunderstanding or padding, and reviewers respond by reducing the award. A good partner calibrates both fields to your real situation rather than inflating them, because inflation is the fastest route to a downgrade.
AWS does not deeply investigate every application; reviewers pattern-match against a consistent checklist. Knowing the checklist explains why some records clear in days, why others get downgraded, and why a small share are rejected outright. Partners who file at volume report the reviewer asking roughly these questions, in roughly this order.
None of these are secret, and none are adversarial. The reviewer is trying to answer one question — "is this a real company that will become a real AWS customer?" — efficiently. Each check is a proxy for part of that answer.
This is the heart of the topic. The self-serve form and the partner-filed path are not two speeds of the same application — they reach structurally different ceilings, and stacking is only available on the partner-filed side.
On the self-serve side, the ceiling is the $5K Activate Founders tier (with a $1K Builders tier below it). There is no self-serve path to $25K, $50K, or $100K — those forms do not exist publicly. So the moment your need exceeds about $5K, the only routes are partner-filed via ACE or VC-filed via the Portfolio Sub-Program. For most founders the partner route is faster, because a partner files on your timeline whereas a VC files when they get to it.
The headline partner-filed tier is Activate Portfolio. AWS's public page shows a "Portfolio" tier for funded companies with no dollar figure attached, precisely because it is a discretionary range rather than a fixed button. In practice the floor is around $25K, the typical award is $100K, and the ceiling is higher in outlier situations. Most qualifying Series-A companies land at exactly $100K because that is the round number reviewers default to for a credible, funded company with a real workload.
On top of the Portfolio base, the partner-filed path supports stacking — additional records against distinct funding sources for genuinely distinct workloads. A clean stack is $100K Portfolio (general infrastructure) plus around $25K Build for Startups (a clearly separate project, say a media pipeline on MediaConvert) plus around $25K of Bedrock / generative-AI POC credit (a clearly separate AI initiative). Done correctly, the total reaches roughly $150K without materially extending the timeline, because the records are filed in the same week.
The hard rule on stacking — and the most common reason secondary records get zeroed out — is that each record must describe a distinct workload. Reviewers will not approve $100K of Portfolio and $25K of Build for Startups when both records describe the same product; that is double-counting, and they will approve the Portfolio and silently downgrade the second record to nothing. The additive credits only materialize if there are genuinely additive workloads behind them. A good partner confirms there is a real second scope before filing a second record, rather than padding the total and triggering a downgrade.
Self-serve tops out near $5K. Partner-filed Portfolio typically lands at $100K, with a realistic stacked ceiling around $150K ($100K Portfolio + ~$25K Build for Startups + ~$25K Bedrock POC) when distinct workloads justify each record. Above that you are into migration-program funding (MAP) or competitive accelerator cohorts, which are different mechanics covered in the linked cornerstones.
Two questions decide whether the partner-filed path is worth it for you: how long it takes and what it costs. Both have clean answers, and the cost answer is the one that surprises people.
For a qualifying, institutionally-funded company, the wall-clock from first contact to credits-in-account is typically 11–18 days, and the founder's total time investment is about 30 minutes of supplying inputs. The bulk of the elapsed time is AWS's review queue, not your effort. A representative first-week timeline looks like this:
The economics are the part founders most often disbelieve, so here it is explicitly. The credits are funded by AWS, at full face value, and apply directly to your bill — the partner never touches them and never marks them up. The partner is paid by AWS, separately, through engagement-funding programs tied to the scope of work on the record (the same programs that make MAP migrations and Well-Architected POCs AWS-funded). A routing layer such as CloudRoute is paid by the partner as a referral commission on closed engagements. The result is that the founder sits outside every payment leg: you pay $0, you do not see an invoice, and the only thing flowing into your account is credits. The structure works because every other party is paid by AWS or by each other, and all of them are aligned around the same outcome — getting a funded startup consolidated on AWS for the long term.
Hour 0 — You submit a short inquiry: company name, funding stage, one-sentence use case. Roughly 90 seconds.
Hour 0–24 — You are matched to a partner whose track record fits your stack, region, and the funding source you need (Advanced or Premier tier for Portfolio-scale records).
Hour 24–48 — A 30-minute discovery call. The partner confirms eligibility, explains what your specific record will look like, and outlines the timeline. You decide whether to proceed.
Hour 48–72 — If proceeding, you spend ~30 minutes on the application worksheet (company info, AWS account ID, a short deck or one-pager, the use-case inputs). The partner files the ACE record within a day of receiving your inputs.
Day 11–18 — Credits appear in your AWS Billing console and AWS emails you the confirmation and validity window.
Partner-filed is the right path for a clear majority of funded startups, but not for everyone. Here is the honest fit map, including the situations where the answer is a smaller credit amount or a different program entirely.
Use the partner-filed path if you are an institutionally-funded startup (Series A is the canonical case; a seed company with a credible investor often qualifies) with an AWS-consuming workload and a need above the $5K self-serve ceiling. That profile is exactly what the Portfolio tier was built for, and the partner-filed route is the fastest way to reach it. It is also the right path if you have a substantial migration or a real generative-AI build, because those carry their own AWS-funded programs that a partner files alongside the credits.
It is the wrong path, or a smaller-amount path, in a handful of clear cases:
Three doors lead into AWS credits. They reach different ceilings, run on different timelines, and lean on different trust signals. This is the comparison that decides which one applies to you.
| Variable | Self-serve form | Partner-filed (ACE) | VC-filed (Portfolio Sub-Program) |
|---|---|---|---|
| Who submits | You | An AWS partner | Your investor |
| Credit ceiling | ~$5K (Founders) | $100K Portfolio, ~$150K stacked | $100K Portfolio |
| Trust signal AWS relies on | None (automated) | Partner track record + vouch | Investor reputation |
| Founder effort | ~5 minutes | ~30 minutes | Varies (depends on the VC) |
| Wall-clock to credits | 24–72 hours | 11–18 days | 10–28+ days |
| Stacking supported? | No | Yes (distinct workloads) | Limited |
| Scope of work attached? | No | Usually (often AWS-funded) | No |
| You control the timeline? | Yes | Mostly | No — the VC files when it files |
Situation: The founder had found the public Activate page, claimed the $5K self-serve credit months earlier, and then hit a wall trying to find the $100K Portfolio "application" — which does not exist as a form. The company had a real workload (multi-tenant app on EKS, Aurora, plus a planned Bedrock support agent) and a tier-1 lead investor, but no idea that Portfolio is partner-filed and no relationship with an AWS partner.
What CloudRoute did: Routed within 20 hours to a UK/EU partner with strong ACE close rates for Portfolio and a Bedrock track record. The partner ran a 30-minute eligibility call, wrote the use-case description against the real EKS + Aurora workload, itemized projected consumption at a plausible ~$6K/month, and filed the Portfolio record on day 3. A separate Bedrock POC record for the distinct support-agent workload was filed the same week.
Outcome: Approved within 15 days: $100K Portfolio plus $25K Bedrock POC = $125K total, full face value in the account. The earlier $5K self-serve credit was simply superseded by Portfolio. Founder time across the whole process was about 4 hours. The partner was paid by AWS through engagement funding and CloudRoute by the partner — the customer paid $0.
matched in <24h · founder time ~4 hours · credits secured $125K · cost to customer $0
CloudRoute routes you to a vetted AWS partner who handles the ACE submission end to end. AWS funds the credits; the partner is funded by AWS; you pay $0. No procurement, no markup, no discovery theater.