Search for AWS discounts and you meet a wall of aggregator platforms all claiming "save up to X%", with no way to tell which layer is being reduced. There are four official sources and three third-party models, and vetting any quote takes three questions - the most important being who owns the account.
Search for AWS discounts and you meet a wall of platforms with near-identical copy: a list of offers plus one line claiming "save up to X%". The problem is that you cannot tell which layer is being reduced, or what the percentage is measured against.
This page does not evaluate any particular platform. It gives a verifiable framework: first understand that "discount" splits into three layers in an AWS context, then vet any quote with three questions.
Split "discount" into three layers first, or nothing is comparable
This is the foundation. A "discount" is not one thing: it acts on a different position of the bill depending on which layer it comes from.
| Layer | Provided by | What it reduces |
|---|---|---|
| Official discount | A commitment you buy from AWS (Savings Plans / reservations) | The unit price on the bill |
| Channel discount | The settlement channel you choose | The amount you actually pay |
| Credits | Eligibility and issuance (free tier / startups / campaigns) | A portion of the bill amount, and it expires |
Why this must come first: the three layers stack and do not substitute for each other. If a platform claims "save 35%" without saying which layer it touches, the claim cannot be verified - it may be an additional reduction on top of the official discount you already hold, or it may simply be counting the official discount inside its own headline. The three layers are explained in AWS credits and discounts are not the same thing.
Four official sources, each with its own purpose
Before going anywhere third-party, know what the official sources give you. Four entry points, four different uses:
| Entry point | What you get | Limitation |
|---|---|---|
| Service pricing pages | Current published unit prices (the official public reference) | Many services; slow to check one by one |
| AWS Price List API | Programmatic price queries, batch extraction and comparison | Needs some technical ability |
| Pricing Calculator | An estimate for your configuration, with before and after discount rates | Excludes taxes; marketing page prices take precedence where they differ |
| Official offers page | Which programmes and campaigns are running (free tier / startups / limited-time) | Campaigns are time-limited and capped, so they need active attention |
How to combine them: use a pricing page or the price list API for the official unit price, use the calculator to see what your configuration would cost, then use the offers page to check what credits you can claim. Only after those two steps do you have a baseline against which any third-party quote can be judged. The calculator is covered in AWS Pricing Calculator.
The three models behind third-party discount platforms
Pages ranking for these keywords are actually three different things. Telling the models apart beats reading the copy:
- Aggregators. They compile official and third-party offers into a list. They provide no service and do not change what you pay - their value is knowing what exists. This content goes stale extremely fast, so when you see specific numbers (what a campaign gives, when it closes) always verify on the official page.
- Channel / service providers. You provision and settle through them, and the margin comes from the channel itself. This is a legitimate model and it is the second layer above. Judging one is not about copywriting but about the three questions in the next section.
- High-risk operations. Their markers: asking you to pay before "unlocking" a discount, promising a fixed discount far below market without written terms, or involving "account transfer" and "account holding". The risk is not the price but account ownership and compliance - see the risks of buying AWS accounts.
⛔ A simple way to tell them apart: a legitimate channel discusses how settlement works, who owns the account, and how long the price holds. A high-risk operation discusses how cheap, how fast, and stop asking questions. The former will put terms in writing; the latter manufactures urgency.
Vetting a quote: three verifiable questions
For any quote, from a channel or a platform, ask these three. Those that answer clearly are worth talking to; those that deflect are not:
- One: which layer does this price reduce? The unit price on the official bill, or the amount you actually pay? The two are different, can both apply, but must not be described as one thing - conflating them usually means the other party has not separated them either.
- Two: how long does this price hold? A one-off concession and a sustainable price are different things. A price that can be held long-term is worth more than a one-time best price, especially if your workload will run for a year or more.
- Three: who owns the account and the subscription? This is the most important one. A low price with an account you do not own means handing over ownership of your infrastructure. Permissions, data, migration and even the risk of the account being reclaimed all follow from this.
None of these requires technical expertise, yet together they filter out most vague quotes. Put the three answers side by side and whether a "save 35%" offer is a real advantage or a talking point becomes fairly clear. A general method for assessing channels is also in partner or buying direct from AWS.
How to read a claim like "save 35%"
The number itself is not necessarily wrong - the issue is that the baseline is almost never stated. Add three qualifications and you can tell whether it applies to you:
| Ask | Why |
|---|---|
| Relative to what? | On-demand price, what you currently pay, or the price after official discounts - the same figure means entirely different things |
| Covering which services? | Everything, or only EC2 / S3 / RDS. When coverage is partial, the effect on the whole bill is far smaller than the headline |
| Over what period? | A one-off first year, or a sustainable reduction for a term. A first-year concession and a long-term cost structure are two different things |
Concretely: "save 35%" meaning "against on-demand, across all services, sustained" is a strong offer; meaning "against on-demand, EC2 only, first year only" has limited effect on a bill dominated by storage and transfer. One number, two meanings.
A pragmatic approach: do not compare advertised percentages - map the offer onto your own bill structure. Work out which line items dominate your spend (method in AWS billing: six actions that actually work), then check whether the concession covers those. Coverage of the big items is a real saving; coverage of the edges is not.
When a channel makes sense, and when it does not
A channel is neither mandatory nor a trap - it is an option that depends on your situation. The test is clear:
| Your situation | Suggestion |
|---|---|
| Blocked at the sign-up barrier (overseas phone number, card binding, verification) | A channel solves this directly - its most concrete value |
| Steady usage at a meaningful spend | Worth comparing channels - the larger the spend, the more room there is |
| Do not want to manage provisioning and settlement yourself | A channel absorbs that work |
| Very small usage, or just learning | The official free tier is simpler - see AWS Free Tier for new accounts |
| Need full control of the account (compliance, audit, internal governance) | Prefer buying direct or official commitment discounts |
One closing note: all three layers can run at once. An official discount changes the unit price, a channel discount changes what you pay, credits offset the amount - going through a channel does not mean giving up official commitment discounts. Working out all three is what a complete cost structure looks like. Channel mechanics vary sharply by provider (on some, the channel is itself part of the pricing) - see cloud discount mechanisms compared, and the AWS-specific channel pricing and sign-up barriers in AWS discounts and reseller pricing.
FAQ
Are the "AWS discount codes" online real?
AWS does not issue public, e-commerce-style discount codes. What exists is promotional credits: issued in a targeted way, redeemed in the console, and subject to terms. Most "codes" on aggregator sites are either expired or not valid for your region. Redemption mechanics and the scams around them are in how to redeem AWS promotional credits.
How do I confirm a campaign is genuine?
Check the domain. Official campaigns sit on the official domain (usually under a campaigns path) and never ask you to pay first. Third-party write-ups are useful as leads, but verify the rules and deadlines on the official page - campaigns are time-limited and third-party content ages quickly.
Is the official route or a third-party channel cheaper?
It is not a like-for-like comparison. What you can get officially is public (commitment discounts, free tier, campaigns); what you can get through a channel depends on the channel (tier, purchase volume, margin strategy). So the right comparison is: establish your baseline cost from official sources first, then see how much lower a channel quote actually is on your dominant line items.
Is a "guaranteed lowest price" claim credible?
Treat absolute claims with caution - official AWS pricing varies by region and service, and a channel margin varies with its own costs, so "guaranteed lowest" is both hard to verify and hard to sustain. The more useful questions are the three in the third section: which layer, how long, and who owns the account.
How often should I review my cost structure?
Two things are worth doing regularly: check the shape of the bill once a quarter (shifts in which line item dominates usually matter more than the total), and review whenever a credit expires, a commitment expires, or your scale changes materially. Cost structure is not a one-off optimisation; it moves with the business.