cloudcostdown.euAWS Activate · Startup Credits Guide
AWS Activate Credits: Get Up to $100K and Make Them Last
AWS Activate gives startups up to $100,000 in cloud credits - but most burn through them in months on unoptimised infrastructure. This guide covers how to qualify for the highest tier, apply step by step, and stretch your credits 30–40% further by optimising before you spend.
Founders vs Portfolio Package
AWS Activate offers two packages. The Portfolio package is where the real money is - and more startups qualify for it than they realise.
| Package | Credits | Eligibility | Best for |
|---|---|---|---|
| Activate Founders | $1,000 in AWS credits + $350 in AWS Developer Support credits Credits valid for 2 years | Self-funded, no VC/accelerator affiliation, new to AWS Activate, pre-Series B, company ≤ 10 years old | Pre-seed founders bootstrapping their MVP |
| Activate PortfolioRecommended | Up to $100,000 in AWS credits Varies by provider tier Credits valid for 1–2 years (provider-dependent) | Associated with an AWS Activate Provider (VC, accelerator, incubator), pre-Series B, most recent funding round within last 12 months, company ≤ 10 years old | Seed or Series A startups backed by any recognised investor |
The Portfolio package credit amount varies by provider and your startup's stage - some providers offer tiered amounts ($25K for pre-seed, $100K for seed-stage). Always ask your investor what tier they offer.
How to Apply: Step by Step
The application takes 20–30 minutes if you have everything ready. Processing takes 7–10 business days. Here's exactly what to do.
Create your AWS Builder ID
Go to the AWS Credits page and create an AWS Builder ID using your personal email. This ID travels with you across jobs and orgs. Verify the confirmation email before proceeding.
Complete your AWS Activate profile
Fill in your startup details once. Use your business email (matching your company domain) for both the profile and the application - domain consistency is part of their validation.
Choose your package and get your Org ID
For the Portfolio package, contact your investor, accelerator, or VC to get their Org ID. It is a unique case-sensitive code - do not share it publicly. If you don't have an Org ID yet, you can apply for the Founders package in the meantime.
Provide startup details accurately
Enter your product description, target market, funding stage, and most recent funding date. Accuracy matters - incorrect staging is the most common reason applications are delayed or downgraded.
Link and verify your AWS account
Link your startup's primary AWS account to your Builder ID. You need admin or root access. Only one Builder ID can be linked to an account - check with colleagues before doing this.
Submit and track your application
Processing takes 7–10 business days. Credits appear in your Billing Console within 3–4 hours of approval. Check the Credit Application Status page for real-time updates.
Reapplying for more credits: You can apply again for a higher amount as long as you haven't hit the lifetime credit cap and your new request exceeds your previous approval. If you received $10K and now qualify for $100K, you get the $90K difference.
The Credit Trap: Why Most Startups Burn Through Credits Too Fast
Credits feel like free money, so the natural response is to keep building without worrying about costs. But if your infrastructure is over-provisioned, you are burning those credits at the same rate as wasted real money. Optimising before the credits clock in is the single most impactful thing you can do.
Unoptimised startup on $100K credits
- ✕EC2 instances running at 10% CPU, paying for 100%
- ✕Dev environments running 24/7, never shut down
- ✕NAT Gateway traffic that could use free VPC endpoints
- ✕Credits exhausted in 9–12 months
- ✕Real AWS bill hits immediately after
Optimised startup on $100K credits
- Right-sized instances - same performance, 30% lower cost
- Dev environments scheduled off - saves 60% on non-prod
- VPC endpoints replace NAT - eliminates data transfer fees
- Credits last 14–18 months instead of 9–12
- Transitions to a leaner real bill when credits expire
Six ways to stretch your credits further
Right-size EC2 and RDS instances before your credits are applied - optimised infrastructure runs 30–40% cheaper from day one
Set up AWS Budgets with alerts at 50%, 75%, and 90% credit consumption so there are no surprises
Delete zombie resources (unused EBS volumes, idle load balancers, forgotten test instances) before credits clock in
Apply credits to services that build towards real product milestones - not one-off experiments that get abandoned
Schedule dev/test environments to shut down overnight and on weekends via Instance Scheduler
Move applicable workloads to Graviton (arm64) - 20–40% cheaper with no code changes on most runtimes
Six Common AWS Activate Mistakes
These are the mistakes that cause startups to either miss out on credits entirely or exhaust them faster than necessary.
Burning credits on over-provisioned infrastructure
Credits don't eliminate waste - they just delay the bill. If your EC2 instances are running at 8% CPU, your credits will be consumed at the same rate as real money. Optimise first, spend credits on growth.
Not noticing the expiry date until it's too late
Credits expire 1–2 years after approval. AWS sends reminders but startups miss them. Mark the date on your calendar the day you get approved and review balance monthly in Billing → Credits.
Applying with a personal email instead of a business email
Domain consistency between your Builder ID profile and your AWS account is part of their validation. Using a Gmail or personal address is a common reason for processing delays.
Leaving dev/test environments running 24/7
Non-production environments running around the clock account for 5–8% of total cloud spend. Credits don't make that free - they just mask it until renewal time.
Spending credits on services before confirming eligibility
Not all AWS services are credit-eligible. Third-party Marketplace subscriptions are typically excluded. Check the eligible services list before provisioning new workloads.
Skipping the Portfolio package because you think you don't qualify
AWS Activate Providers include thousands of VCs, angel investors, accelerators, and startup studios worldwide. If your startup has any institutional backing at all, ask your investor for their Org ID - you very likely qualify.
AWS Activate vs Google Cloud vs Microsoft for Startups
If your startup is multi-cloud or evaluating which provider to prioritise, here is how the major startup credit programs compare as of 2026.
| Program | Self-funded credits | Investor-backed credits | Notable advantage |
|---|---|---|---|
| AWS Activate | $1,000 (Founders) | Up to $100,000 (Portfolio) | Deepest service breadth, 200+ services, Bedrock AI models included |
| Google Cloud for Startups | $2,000 | Up to $200,000 over 2 years ($350K for AI-first startups) | Best for AI-first startups needing Vertex AI / Gemini at scale |
| Microsoft for Startups | Up to $5,000 (180 days) | Up to $150,000/year (Investor Network, restructured July 2025) | Includes GitHub, Azure DevOps, and Microsoft 365 tooling |
These programs are not mutually exclusive. Many startups apply to all three and use each for different workloads. AWS Activate is usually the highest priority for infrastructure-heavy startups given AWS's service breadth.