Direct answer
When AWS credits expire, eligible usage stops being offset by that credit balance. If there is no other active credit or commercial discount, your next bill reflects the real AWS run-rate.
1-2 yrs
AWS says Activate credits usually expire within 1-2 years depending on package.
Billing
Check Credits, Bills, Cost Explorer, and linked account sharing before the month closes.
EU/UK
Partner-led routes can matter more than generic US startup-program advice.
For EU and UK startups, expired AWS credits are usually a runway problem, not just a billing problem. Compute, database, storage, AI, and data-transfer spend that felt invisible can become cash cost in the first full month after expiry.
AWS says Activate credits usually expire within 1-2 years depending on package, and that approved credits and expiration dates appear in the AWS Billing and Cost Management Console. AWS Activate credit guide AWS billing documentation says credits are applied until they are exhausted or expire. AWS Billing credit documentation
For a broader map of direct AWS Activate, post-Activate review, and partner-supported options, read AWS cloud credits for startups.
After the credit cliff
Once the first full bill is visible, the strongest next ask may be credits, discounts, funded work, migration support, payment terms, or billing structure.
The decision table
Situation
Credits expire in 60-90 days
You still have time to forecast the full bill and check another route.
Main risk
You optimize too late
The first full post-credit invoice lands before finance sees the real run-rate.
Move
Run eligibility now
Check prior credits, funding stage, current spend, and provider fit before booking anything.
Credits already expired
The first bill spike is already visible or about to be visible.
You panic-migrate
Moving workloads for headline credits can cost more engineering time than it saves.
Triage in 7 days
Find the top services, pause waste, set alerts, then check credit and commercial options.
Used vs expired
If you used all AWS credits, that may be a stronger signal than simply having credits expire. Fully consumed credits can prove real usage; expired unused credits may need a separate growth trigger to make the case credible.
Read the used-credits guideWhat actually changes
Before expiry
- Eligible AWS usage is offset automatically.
- Your invoice may understate the real infrastructure run-rate.
- Service growth can hide behind the credit balance.
After expiry
- Expired credits no longer offset new eligible usage.
- EC2, RDS, EKS, Bedrock, S3, NAT, and data-transfer spend can surface quickly.
- Linked-account credit sharing can make attribution harder.
AWS applies credits automatically using rules such as expiration date, service eligibility, and account setup. In AWS Organizations, credits may also apply across linked accounts, so the real source of the spike can be less obvious. AWS Billing credit application rules
Check these first
Billing > Credits
Confirm amount remaining, expiration date, and whether the balance is actually gone.
Bills > Savings
Check estimated credit balance for the current billing month.
Cost Explorer
Compare gross usage for the last 90 days, not just net invoice cost.
Cost and Usage Report
Find services that were covered by credits and will become cash spend.
AWS Organizations
Confirm whether credits were shared across linked accounts.
Why founders get surprised
The usual failure mode is mental anchoring. The team sees a small credit-covered invoice for months, then treats that as the real cloud bill.
The pattern
1
Credits active
2
Usage grows
3
Credits expire
4
Cash bill jumps
AWS says Activate Portfolio can provide up to $100,000 for eligible provider-backed startups, and Activate Founders offers $1,000 for eligible self-funded startups. Both paths have eligibility requirements, including company age and funding stage. AWS Activate eligibility page
The EU/UK angle
A generic US guide usually says to apply to AWS Activate or contact AWS Support. That can be incomplete for a funded European startup with existing cloud spend.
Operator note
EU and UK startups often have different partner, reseller, procurement, data-residency, and migration constraints. The question is not only whether credits exist. It is whether the route fits your company, account history, and engineering reality.
Check credit route fit
- Current funding round and timing.
- Previous AWS credit amount.
- Provider or partner affiliation.
- Current and forecasted cloud spend.
Check migration reality
- Data location and customer contracts.
- Marketplace or reseller commitments.
- Engineering time to move workloads.
- Support coverage after migration.
Recent field notes
What we are seeing from startup cloud-benefit reviews.
Based on 45 non-cancelled startup cloud-benefit calls booked since January 2026, the strongest-fit companies usually had one or more clear signals: existing cloud spend, credits ending soon, recent funding, AI or GPU-heavy workloads, or a planned infrastructure project.
These are internal patterns from recent startup conversations, not guaranteed provider approval criteria.
- 45
- non-cancelled calls
- 2026
- booked since January
- 5
- strong-fit signals
What to do before expiry
Pull the real run-rate
Export 90 days from Cost Explorer or CUR. Look at gross usage by service, not just the invoice after credits.
Cut obvious waste
Find idle RDS instances, unattached EBS volumes, oversized dev environments, snapshots, and staging clusters.
Check another credit path
Prior credits, stage, funding date, provider relationship, and current spend all affect the answer.
Avoid panic migration
Provider credits can help, but only if the engineering and compliance cost makes sense.
AWS says credit volume varies by stage, funding timeframe, and Activate Provider affiliation. AWS Activate credit amounts That is why the right next step is an eligibility check, not a generic booking link.
If credits already expired
First 7 days
- Confirm the credit balance is actually expired.
- Find the top services and linked accounts causing the spike.
- Turn on budget alerts for the current month.
- Pause non-production workloads with no owner.
Next 30 days
- Forecast steady-state spend without credits.
- Check if another AWS route is still realistic.
- Check whether Azure or Google Cloud credits fit future workloads.
- Model optimization, resale terms, and migration separately.
When to check another route
Strong fit signals
Next step
AWS credits expired or expiring soon?
Check whether your EU/UK startup may qualify for another cloud credit route before the next full bill hits.
Check eligibilityBottom line
AWS credits are useful because they hide infrastructure cost while the startup is still proving the product. The risk is treating the credit-covered bill as the real bill.
Before credits expire, get the real run-rate, cut avoidable waste, and check whether another partner-led route exists. If the credits already expired, move fast, but do not panic-migrate workloads just to chase a headline credit amount.
