AWS Activate Startup Credits: How to Check the Route

AWS Activate is one of the most commonly forwarded “startup credit” links in founder chats. The page is useful because Amazon publishes it. It is also easy to misuse: someone pastes a large “up to” number into a budget, applies with the wrong account, or assumes a catalog card has already checked the current tier.

This note is not an AWS application guide and not a list of current amounts. It is an inspection workflow for the official AWS Activate credits page. Use it before you create an account, connect a billing method, or count a credit in a plan.

Quick answer: Open the current AWS Activate credits page, record the access route and promotional-term link you actually see, and copy the eligibility language verbatim. AWS—not Startup Perk List and not a catalog snapshot—decides whether an applicant qualifies and what credit is granted.

Pair this inspection with the generic evaluation workflow and keep the result in a small perk ledger.

1. Start from the provider host, not a recap

The primary source is the AWS-owned credits page, not a newsletter, partner roundup, or catalog card. A Startup Perk List listing that mentions Activate is a discovery aid. The decision source is the page AWS currently serves.

Record:

the exact URL after any redirect;
the page title;
the date and timezone you checked it; and
whether you reached a credits page, a broader startups page, or a sign-in wall.

If you landed on a partner or catalog host, stop and use the source-kind checklist. Do not continue the Activate inspection against a third-party summary.

2. Separate the program name from the access route

On the current Activate credits page, AWS presents more than one way to reach credits. The inspection job is to write down which route you are actually eligible to use, not to merge every tier into one number.

Ask the page:

Which routes are named (for example a self-serve path versus a path that requires a funding or founding-partner relationship)?
Which eligibility words are defined on this page—company age, funding stage, account type, or prior credit use?
Does the page send you to promotional-credit terms, an account console, or another AWS document?
What does the page say happens if the applicant already used Activate or holds a different AWS account plan?

Copy the answers in the provider’s words. If two routes show different maxima, record both and mark which one matches your company. A catalog card that shows only one number is incomplete once the provider page shows a split.

The existing Startup Perk List methodology already treats this page as a first-party example of “published tier, access route, and promotional-terms link.” That is the ceiling of what a public page can prove. It cannot prove the amount that will land in your account.

3. Open the promotional terms before you model value

A credits marketing page is not the complete rule set. If the Activate page links to promotional-credit terms, open that document in the same session and add it to the evidence packet.

Look for language about:

what the credit can and cannot be applied to;
whether unused value expires;
whether a payment method is required before activation; and
what happens after the promotional period.

If those answers are not on the page you opened, write needs confirmation instead of inferring AWS marketplace, support, or third-party usage rules from a forum post.

Only after that packet exists should you estimate usable value. Use the conservative filter from the evaluation guide: fit, timing, and friction. A large Activate headline that requires an account migration you will not finish before expiry is not that headline to your team.

4. Check the account you will actually use

Activate decisions attach to an AWS account, not to a Slack thread. Before anyone clicks apply, write down:

the AWS account ID or alias the team intends to use;
who can add a payment method and read billing alerts;
whether the account already received promotional credits; and
whether production workloads already run there.

Applying from a personal account and later “moving” the credit is a common failure mode. The ledger should store an account reference, not a root password or access key. If the page or terms say prior credit use matters, treat a second application as a new eligibility question.

5. Decide with a visible status

Use the same rubric as the rest of this journal:

Proceed: you have the current credits page, the terms link, a matching access route, and an owner for the AWS account.
Verify: the page is behind sign-in, the access route is unclear, or prior-credit language does not match your account history.
Pass for now: the route requires a partner or funding condition you do not have, or the setup cost exceeds the realistic use window.

Keep AWS’s confirmation—if one arrives—separate from the catalog observation. The confirmation is evidence of your account. The catalog record is only a dated pointer.

Evidence, boundary, and last verified

Evidence. This article inspects the first-party AWS Activate credits page as an example of how to read tiers, access routes, and promotional-term links. Amounts, regions, and eligibility rules are not reproduced here because they can change on the provider page after publication. See the methodology and source policy.

Boundary. Startup Perk List does not submit Activate applications, allocate credits, or confirm AWS account eligibility. AWS controls approval, value, expiry, and product scope. See About this journal.

Last verified. The linked AWS page and this inspection workflow were checked on 2026-08-30 (Asia/Shanghai). Re-open the page immediately before applying. A current AWS page replaces this note.

Final check

Open the AWS Activate credits page yourself. Write the access route, the promotional-terms URL, and the eligibility sentence that applies to your company. If one of those three is missing, do not copy a maximum into the budget. Mark needs confirmation and ask AWS or your founding partner a specific question.