AWS promotional credits vs Activate credits — two pools, two redemption flows, one stacking story.

IThe two credit pools — what each one actually is

Before getting into mechanics, the two pools need to be cleanly separated. They are not two ways of receiving the same credit — they are two structurally different systems that produce different credit amounts via different issuance flows with different validity windows.

Promotional credits are the AWS-marketing-team credit pool. AWS's marketing organization runs hundreds of distinct programs across a calendar year — re:Invent (the flagship annual conference in Las Vegas), regional AWS Summits (London, Sydney, Singapore, Tokyo, São Paulo, Berlin, Dubai, Riyadh, Mumbai, and roughly 20 other cities), re:Inforce (the security-focused conference), re:Mars (the ML/automation conference until 2024, retired in 2025), AWS GameDay events, AWS DeepRacer competitions, training-portal completion certificates (Solutions Architect Associate, Cloud Practitioner, DevOps Engineer Professional, and similar tracks), partner co-marketing events, hackathon sponsorships, and Marketplace promotional campaigns. Each of these programs issues credit codes to attendees, completers, or participants. The codes are typically $25, $50, $100, $250, or $500, depending on the program and the attendee tier. A re:Invent attendee with a full conference pass might receive a $250 code in their attendee bag; a training-portal completer of the Cloud Practitioner certification might receive a $100 code at certification time; an AWS Summit Dubai attendee might receive a $100 code at the welcome desk.

Activate credits are the AWS-startup-team credit pool. The Activate program is structurally separate from promotional marketing. It runs through aws.amazon.com/startups/credits (the self-serve forms) and through the ACE program (partner-filed). The credit amounts are larger and the eligibility criteria are stricter — incorporated entity, AWS-eligible use case, sometimes institutional vouch for the larger pools. The Activate tiers, in ascending order of credit ceiling: Builders ($1K self-serve, no company entity required), Founders ($5K self-serve or $25K partner-filed, incorporated company required), Portfolio ($50K–$100K partner-filed, institutional vouch typically required), Build for Startups (+$25K stack-additive for migration scope), Bedrock POC ($10K–$50K stack-additive for AI workload).

The two pools come from different AWS budgets. The promotional credit pool is funded out of marketing — the same budget that pays for the conference venues, the swag, the booth costs, and the speaker travel. The Activate pool is funded out of AWS's startup-acquisition budget, structured as a customer-acquisition cost where AWS is willing to spend $5K–$100K per startup to onboard them into the AWS ecosystem long-term. The two budgets do not interact; the customer-facing presentation does not distinguish them; the billing console handles both as fungible credit balances.

For a founder, the practical implication is that both pools exist independently and both can be claimed independently. A founder who already received a $250 promo code at AWS Summit Dubai is not blocked from applying for Activate Founders — the promo code is in one pool, the Founders award would be in another. A founder pursuing Activate Portfolio is not blocked from later receiving promo codes at re:Invent attendance. Sections IV and V cover the stacking math in detail.

IIThe redemption mechanic — manual code entry vs auto-issued

The most operationally consequential difference between the two pools is how the credit lands in the AWS billing console. The mechanic for each is structurally different — different page, different action, different timing.

Promotional credits arrive as redemption codes. The founder receives a code — typically a 16-character alphanumeric string like "AWSXMAS-XXXX-XXXX-XXXX" — through email, on a physical card at an event, in an attendee bag, or printed on a certificate. The code must be manually entered into the AWS Billing Console. The flow: log into the AWS Management Console, navigate to Billing and Cost Management, click "Credits" in the left navigation, click "Redeem credit," paste the code into the input field, confirm the redemption. The credit posts to the account immediately upon redemption — there is no review queue, no approval workflow, no waiting period. The redemption is irreversible once submitted, and the code is tied to the AWS account that redeemed it (it cannot be transferred to another account later).

Activate credits never go through the manual code-entry flow. The Activate award is auto-issued by AWS's internal credit-posting system after the application is approved. The founder fills out the Activate Founders form (or the partner files the ACE record), the reviewer approves the award, and AWS's internal billing system posts the credit directly to the account. The founder receives an email confirmation — "Your AWS Activate Founders credit has been issued" — and the credit is immediately visible under "Billing → Credits → Promotional credits" (yes, the billing console groups all credits under the "Promotional credits" label regardless of source pool, which is a frequent source of confusion).

The mechanical implication for founders: any code received from an AWS marketing event must be actively redeemed by the founder. The code does not auto-apply. A founder who attends AWS Summit Sydney, receives a $250 promo card, and tucks it in a wallet without redeeming it has nothing in the billing console — the credit only lands after the redemption flow completes. By contrast, an Activate Founders award requires zero action from the founder once approved; it arrives in the billing console automatically and starts applying against the next invoice without any further step.

A consequence of this difference is that promo codes can be lost. A founder who throws away the conference bag without noticing the credit card inside has thrown away the credit. A founder who forwards the redemption email to a teammate, has the teammate redeem the code in a personal AWS account by accident, has now lost the credit to the wrong account. Activate awards do not have this risk class — they cannot be lost because they never exist as a transferable code; they exist only as a posted balance in the company AWS account.

The redemption page in the billing console is identical for all promotional code types. Whether the code is a $25 training-completion code, a $250 re:Invent attendee code, or a $500 Solutions Architect track code, the redemption interface is the same — paste the code, click confirm. AWS does not require the founder to declare the source of the code or any context about where it came from. The code itself carries all the metadata needed for AWS to credit the correct internal program.

IIIValidity windows — the 12-month default and the 24-month Portfolio exception

Both pools carry expiration dates. The default is 12 months from the date the credit posts to the account, but the Portfolio sub-program is the exception at 24 months. Understanding the validity window matters because it determines real usable runway, not the headline credit number.

Promotional credits typically carry a 12-month validity from the issue date. The issue date is when the marketing event occurs, not when the founder redeems the code. A $250 code distributed at AWS Summit Sydney on March 15, 2025 carries a validity until roughly March 15, 2026 regardless of when the founder redeems it. If the founder redeems the code on March 14, 2026 (one day before expiration), the credit posts to the billing console with a remaining validity of one day — meaning the credit must be consumed against the next invoice or it expires. This is a real failure mode worth flagging: codes held without being redeemed lose value as the calendar runs forward, and a code with a stale issue date can be effectively worthless by the time the founder gets around to redeeming it.

Some promotional codes have shorter validities. Training-completion codes (issued at certification) typically run 6 months. Hackathon participation codes sometimes run 3 months. Marketplace cross-promotion codes can run as short as 60 days. The validity window is printed on the physical card or on the certificate, and is included in the redemption email when the code arrives digitally. Founders should redeem codes shortly after receipt rather than holding them — the validity clock starts at issuance, not at redemption.

Activate Founders, Builders, Build for Startups, and Bedrock POC all carry the 12-month validity standard. Activate Portfolio is the exception at 24 months — the longer window reflects the larger credit pool ($50K–$100K) and the assumption that institutionally-funded startups have a longer runway profile and need more time to consume the credits productively.

Both pools handle expiration the same way. At the moment of expiration, any remaining balance is zeroed out automatically. The credit line item in the billing console shows "$0.00 remaining" and stops applying against invoices. There is no grace period, no extension request workflow, no carryover into a new credit award. AWS does not notify the founder before expiration; the founder discovers it on the first invoice after expiration when the bill no longer shows credits applied.

For planning purposes, a founder holding multiple credit awards should think of them as a stacked queue with expiration dates. A founder might hold: a $250 promo code (expiration July 2026), a $5K Activate Founders award (expiration February 2027), a $100K Activate Portfolio award (expiration February 2028). The total balance at any given month is the sum of unexpired remaining balances. The order of consumption is dictated by AWS (credits expiring soonest are consumed first against invoices), so the $250 promo code burns first, then the $5K Founders, then the $100K Portfolio.

IVThe stacking mechanic — how promotional and Activate credits coexist on the same account

Promotional credits and Activate credits live in the same billing console under the same "Promotional credits" header. They stack additively — the total balance is the arithmetic sum of unexpired credits across both pools. The order of consumption follows expiration date.

The AWS billing console treats both credit pools as fungible from a balance perspective. When the monthly invoice generates, AWS's billing engine totals all available credit balances (promotional and Activate, regardless of source pool) and applies them against the invoice in expiration order — credits expiring soonest are consumed first. The founder sees a single line item: "AWS promotional credits applied: -$XXX." The breakdown by credit source is visible in the credits detail view but does not affect the application order.

Concretely: a founder holds a $250 AWS Summit code (expiring July 2026), a $100 training-completion code (expiring January 2026), and a $5K Activate Founders award (expiring February 2027). The April 2026 invoice generates at $380. AWS's billing engine applies credits in expiration order — the $100 training code would have already been consumed in earlier invoices, the $250 Summit code is consumed first ($250 of the $380), then $130 of the $5K Founders award is consumed to cover the remainder. Net invoice charged to the company's payment method: $0. Remaining balances after the April invoice: $0 Summit (fully consumed), $4,870 Founders.

The stacking math is genuinely additive — the credits do not interfere with each other procedurally. Holding a $250 promo code does not reduce the $5K Founders award. Receiving an Activate Portfolio award later does not invalidate previously-held promo codes. The two pools coexist as separate line items in the credits detail view, with their own remaining balances and expiration dates, and the consumption is driven by the expiration-order rule.

One mechanical nuance: certain Marketplace cross-promotion credits are scope-restricted. A Marketplace-cross-promotion code might be restricted to consumption against Marketplace charges only (third-party software bought through AWS Marketplace), not against AWS-native service charges (EC2, RDS, S3, etc.). The scope restriction is encoded in the credit metadata; the billing console respects it when applying credits. A scope-restricted credit will not apply against an AWS-native invoice and will sit in the credits balance until consumed against a qualifying charge. This is rare but worth being aware of — most promo codes are general-purpose, but the Marketplace cross-promotion subset is not.

Activate credits do not have this scope restriction. Founders, Builders, Portfolio, Build for Startups, and Bedrock POC all apply against general AWS-native service consumption (EC2, RDS, S3, Lambda, Bedrock, SageMaker, and the full AWS service catalog). They do not apply against Marketplace charges, support fees, or Reserved Instance upfront payments — these exclusions are consistent across both Activate credits and most general-purpose promo credits.

VCommon sources of promotional credits — what the codes typically are

The "I got an AWS code from a Twitter promo / a conference bag / an email" scenario is the most common founder encounter with promotional credits. Understanding what these typically are and why they cap small helps set expectations.

AWS Summit attendance is the highest-volume source of promotional credits. Each regional Summit (roughly 30 cities globally per calendar year) distributes credits to attendees as part of the attendee package. The typical amount ranges $100–$500 depending on the city and attendee tier. London and San Francisco summits tend toward the higher end ($250–$500); regional summits in Riyadh, Bogotá, and similar markets tend toward the $100–$250 range. The code is distributed at the registration desk, included in the attendee bag, or sent in a post-event follow-up email. Validity is typically 12 months from the event date.

re:Invent attendee codes are issued to full-pass attendees of AWS's flagship annual conference (Las Vegas, late November / early December). The credit amount is typically $300–$500 for a full-pass attendee, with higher amounts ($500–$1,000) sometimes available for specific attendee tracks (Builder Pass, Innovation Lab participants). re:Invent codes are sometimes bundled with re:Invent-specific service launches — for example, a Bedrock service announcement at re:Invent might come with a $200 Bedrock-restricted credit code in the keynote attendee bag.

Training-portal completion certificates issue credits at certification time. AWS offers a portfolio of certifications: Cloud Practitioner ($100 typical completion credit), Solutions Architect Associate ($150–$300), Solutions Architect Professional ($300–$500), DevOps Engineer Professional ($300–$500), Machine Learning Specialty ($250–$500), Database Specialty ($250–$500), Security Specialty ($250–$500), Networking Specialty ($250–$500), Data Analytics Specialty ($250–$500), SAP on AWS Specialty ($250–$500), and several others. Not every certification track issues a credit; the issuance is at AWS's discretion and varies by year and by promotional cycle. When a credit is issued, it arrives by email within 30 days of certification.

AWS GameDay and DeepRacer competition participation issue credits to participants. The amounts vary by event scale — local AWS GameDay events typically issue $50–$100 codes; the global DeepRacer League final issued $500 codes to qualifying participants in recent years. These codes are typically scoped to specific services (GameDay codes might be EC2-focused; DeepRacer codes might be SageMaker-focused) and are time-restricted to short validity windows (60–90 days in some cases).

Hackathon participation is a common source — AWS sponsors hundreds of hackathons globally per year, either directly or through partner sponsorships. The credit amount is typically $100–$500 per participating team. The codes are distributed at the hackathon kickoff or sent in a follow-up email post-event. Validity windows vary; some hackathon codes run 90 days, others run 12 months.

AWS Marketplace cross-promotion is the smaller-volume source. When a Marketplace partner runs a promotional campaign, AWS sometimes issues cross-promotion credits to Marketplace buyers — typically $50–$200, scope-restricted to either the specific Marketplace product or to AWS Marketplace generally. These codes are scope-restricted in metadata; they will not apply against AWS-native service consumption.

re:Inforce attendee codes (issued at the security-focused annual conference) typically run $200–$300. The re:Mars conference issued codes in the $300–$500 range during its operational years (2019–2024) but is now retired. AWS Public Sector Summit attendees in Washington DC and equivalent regional government-focused events receive codes in the $100–$250 range.

The common thread: promotional codes cap small because they are marketing acquisition tools. AWS's marketing organization is using the codes to drive AWS Summit attendance, training-portal engagement, and conference participation. The codes are not meant to fund a startup's infrastructure runway — that is the role of Activate. The codes are meant to seed an AWS account with enough credit to encourage the recipient to start using AWS services, generating eventual paid consumption.

VIThe "I have an AWS code from a Twitter promo" scenario — what these typically are

A recurring inbound question to CloudRoute and to AWS partner channels is "I received an AWS promo code through Twitter / LinkedIn / a newsletter — what is this and what do I do with it?" Worth covering the typical answer because the founder mental model often misreads the credit's actual scope.

AWS does run periodic Twitter, LinkedIn, and newsletter promotional campaigns. These typically come in two flavors: (a) developer-advocate Twitter giveaways, where an AWS developer advocate distributes codes to followers as part of a content series — these are typically $25–$100 codes with the same redemption flow as event codes, and (b) AWS Builder Center or AWS News Blog newsletter promotions, where AWS's content marketing team includes codes in newsletter footers for subscribers — also typically $25–$100.

Why the codes cap small: the customer-acquisition economics. AWS's marketing team values an active AWS account at a marketing cost in the $25–$100 range for digital-acquisition channels (Twitter, LinkedIn, newsletter) and the $100–$500 range for high-cost-of-attendance channels (Summits, re:Invent, hackathons). The credit amounts mirror the channel value — the channel with the lowest cost-of-acquisition (a Twitter promotion costs effectively $0 to distribute) issues the smallest credit. A founder receiving a $50 code from a developer-advocate Twitter giveaway is receiving the marketing-cost-equivalent of being acquired through a $0-marginal-cost channel.

What the code is not: it is not Activate. A Twitter promo code does not grant Activate eligibility, does not roll into a larger pool, and does not entitle the holder to any further AWS funding beyond the $50 (or whatever the specific amount). A founder who receives a $50 Twitter promo code and assumes it indicates AWS-startup-program interest is reading more into the code than is actually there. The code is a marketing-funnel asset; the Activate program is structurally separate.

The right framing for the Twitter-promo scenario: redeem the code immediately (the validity clock is ticking from issue date, not from receipt), spend the $50 against an experiment or a small workload, and then apply for Activate Founders separately for the actual startup credit pool. The $50 does not interfere with the Activate application — it is a $50 marketing asset, and Activate is a $5K–$100K acquisition program. Both can coexist on the same account simultaneously.

One frequently-asked sub-question: "is the Twitter promo code legitimate, or is it a phishing scam?" Legitimate AWS promo codes are distributed only through verified AWS channels — official AWS Twitter accounts (@awscloud, @awsdevelopers, named developer-advocate accounts with the AWS Hero badge or AWS staff designation), the AWS News Blog, AWS Builder Center, and event registration confirmations. Codes distributed through unverified accounts, codes that arrive without a clear AWS-affiliated source, and codes that ask for AWS account credentials to redeem are not legitimate and should be ignored. Legitimate codes redeem through the AWS Billing Console only — no AWS-legitimate flow asks for credentials outside the AWS Console.

VIIThe "I have a promo code, do I still apply for Activate?" decision tree

The most common founder decision-point around promotional credits: "I already have $250 of promo credits sitting in my AWS account — do I still need to apply for Activate Founders?" The answer is essentially always yes, but the framing matters.

The promo credit is bridge credit. It is the amount of AWS spending the founder can do today, immediately, without applying for anything further. It is intended to fund initial experimentation, not to fund a startup runway. A $250 promo code at a small MVP burn rate of $200/month covers 1.25 months. That is a useful bridge — it covers the first few weeks of AWS experimentation, lets the founder build out the initial infrastructure, gets the workload to a point where the founder can describe it in an Activate application — but it is not a substitute for the structured Activate funding.

The Activate Founders award is the structured program. At $5K self-serve or $25K partner-filed, it is calibrated to fund the validation runway of a real startup (3–24 months of MVP-stage burn). The application is short (5 minutes self-serve), the approval window is short (3–7 days), and the credit is incremental to anything held in the account from promotional sources. The $250 promo + the $5K Founders = $5,250 total starting balance.

The decision tree for the "promo + Activate" question: (1) Redeem the promo code today, before validity erodes further. (2) Use the promo credit to fund initial AWS experimentation — spin up the first EC2 instances, deploy the first S3 buckets, get a Lambda function or two running. (3) Within the first 2 weeks of redeeming the promo, file the Activate Founders application. The application benefits from having an active workload to describe — "I am running ECS Fargate + Aurora Serverless v2 for a B2B SaaS MVP, with current monthly burn at $X" is a stronger application than "I plan to run AWS for an unspecified product." (4) The $5K Founders credit lands in 3–7 days and stacks on top of whatever remains of the promo credit. (5) Continue burning credits in expiration order; the promo will exhaust first because of the earlier issue date.

A common error: founders who have a promo code sometimes treat it as their AWS-credit allocation and skip the Activate application entirely. The reasoning is usually some version of "I already got credits, I don't want to come across as greedy by asking for more." This reading misunderstands the structural separation of the two pools. The promo credit was issued by AWS marketing; the Activate credit comes from AWS's startup-acquisition budget. The two budgets do not interact. AWS does not track who has received promo codes when evaluating Activate applications. The Activate reviewer does not see the promo balance and is not influenced by it. Filing Activate after holding a promo is procedurally clean and produces the expected $5K Founders outcome.

A second common error: founders treating promo codes as a signal that AWS "knows about them" and that further outreach will follow. The codes are mass-distributed marketing tools. AWS's startup team is not aware of who received a re:Invent attendee code or a Summit Sydney code. There is no follow-up from the promo-code distribution channel into the Activate program. The founder must initiate the Activate application themselves (or via a CloudRoute-routed partner) for the structured pool to engage.

VIIIA worked example — AWS Summit Sydney 2025 + Activate Founders + first six months

Concrete numbers for the most common single-founder scenario: a solo founder attends AWS Summit Sydney, receives a $250 promo code, layers it on top of $5K Activate Founders, and covers the first 4–6 months of pre-MVP exploration entirely with credits.

Day 0 — Solo founder attends AWS Summit Sydney 2025 on April 9, 2025. Receives a $250 promotional code in the attendee bag with a 12-month validity (expires April 9, 2026). The founder is pre-incorporation at the time of the Summit, attending to learn about AWS services for an upcoming MVP project.

Day 14 — Founder incorporates a Pty Ltd in Australia (Australian company structure equivalent to a US LLC for Activate eligibility purposes). Cost: AUD $508 for ASIC registration plus accountant assistance. Opens an AWS account in the company name.

Day 16 — Founder logs into the new AWS account, navigates to Billing → Credits → Redeem credit, enters the $250 Summit Sydney code, confirms redemption. The credit posts immediately to the account as a $250 balance with the original April 9, 2026 expiration.

Day 17 — Founder spins up initial infrastructure: a t4g.small EC2 instance for development (~$10/month), Aurora Serverless v2 minimum capacity (~$45/month at idle), S3 buckets for static assets (~$2/month), CloudWatch logging (~$5/month). Total day-17 burn rate projection: ~$62/month.

Day 20 — Founder applies for Activate Founders through the self-serve form at aws.amazon.com/startups/credits. Application takes 7 minutes (slightly longer than the typical 5 minutes because the founder writes a thorough use case description referencing the existing infrastructure already running on AWS).

Day 24 — $5K Activate Founders credit approved. Posts to the billing console with a 12-month expiration (May 24, 2026). Total credit balance at this point: $250 Summit Sydney (with $58 already consumed against the partial-month April invoice) + $5,000 Founders = $5,192 remaining balance.

Months 1–4 (May, June, July, August 2025) — Founder builds out the MVP at a burn rate that gradually scales from $62/month at the start to ~$180/month by month 4 as the workload grows (dev environment expands, more Aurora capacity, larger CloudWatch retention, additional Lambda functions). Cumulative AWS burn months 1–4: ~$520. Credit balance after month 4: $5,192 - $520 = $4,672 remaining.

Month 5–6 (September, October 2025) — Founder enters MVP polish phase, burn rate ~$240/month. Cumulative additional burn: ~$480. Credit balance after month 6: $4,672 - $480 = $4,192 remaining.

Month 7 (November 2025) — Founder launches MVP to first beta users. Burn rate spikes to ~$520/month due to traffic and Aurora capacity scaling. The Summit Sydney $250 promo credit exhausted in month 1 (consumed first because of earlier expiration). The Founders $5K is still active with ~$4,000 remaining as of month 6. Founder still has 6 months of validity remaining on the Founders credit.

Total credit position from the dual-pool stack: $5,250 starting balance covering ~4–6 months of pre-MVP burn plus partial MVP launch costs. The customer-paid amount across this entire window: $0. Total founder time invested in claiming both pools: ~12 minutes (5 min Summit code redemption + 7 min Activate Founders application).

The worked example illustrates the right pattern. Promotional credits are bridge credits — they fund the very first weeks of AWS exploration while the founder finalizes the entity and prepares the Activate application. The Activate Founders award is the structured runway — it covers the validation phase at a real burn rate. Together they form the "$5K-plus" starting balance that most solo-founder MVP profiles can secure with under 15 minutes of total effort.

IXThree founder profiles where the promo + Activate stack fits

The promotional-plus-Activate stack is the canonical entry-point pattern for three specific founder profiles. The fit is determined by stage, by access to AWS-marketing channels, and by the availability of the self-serve Activate form.

• Solo founder, pre-MVP, attended a regional AWS Summit — Most common profile. Solo technical founder, already attended an AWS Summit (Sydney, Singapore, London, Riyadh, Bangalore, Mumbai, São Paulo, Tokyo, Dubai, or another regional summit), holds a $100–$500 promo code, has incorporated or is preparing to incorporate. The right move: redeem the code, file Activate Founders self-serve immediately after, layer the two pools. Total credit: $100–$500 promo + $5K Founders = $5,100–$5,500 starting balance. Covers 4–8 months of typical solo-founder MVP burn.
• Pre-seed founder, training-portal certified — Founder has completed an AWS certification (Cloud Practitioner, Solutions Architect Associate, or similar) before incorporating the company, holds a $100–$300 training-completion code. Incorporates within 60–90 days of certification. Same pattern as above: redeem the code, file Founders, layer the pools. The training-completion path has the additional signal value of demonstrating AWS-services familiarity in the Activate application, which can favorably influence the reviewer's assessment of the use case.
• Bootstrapped founder, no institutional vouch, real production workload — Bootstrapped founder running production AWS at $500–$2,000/month, holds one or more accumulated promo codes (from event attendance, training, or hackathon participation), is eligible for partner-filed Founders ($25K) rather than self-serve Founders ($5K). The right move: redeem the promo codes first as a bridge, then file partner-filed Founders through a CloudRoute-routed partner for the $25K pool. Total credit position: accumulated promo balance + $25K partner-filed Founders. Customer cost: $0 (the partner is paid by AWS engagement-funding separate from the customer).