AWS credits are cash-equivalent vouchers applied against your AWS bill. Unlike discounts — which reduce unit prices — credits offset actual charges and are consumed before you pay. For enterprise buyers managing large AWS estates, a well-negotiated credits strategy can provide material short-term cost relief, fund migration and experimentation programmes, and reduce the cash flow impact of new technology investments.

This article is part of our AWS Enterprise Negotiation Guide. For the broader commercial negotiation framework — including EDP discounts which are a separate and more significant commercial lever — see our AWS EDP negotiation playbook.

KEY INSIGHT

Large enterprise customers routinely receive $50K–$500K+ in AWS credits annually through a combination of EDP service credits, migration credits, Graviton adoption credits, and strategic programme participation. Many procurement teams leave significant credits on the table simply by not knowing what to ask for and when.

Types of AWS Credits

AWS issues credits under multiple distinct programmes, each with different eligibility criteria, application rules, and negotiability. Understanding the landscape is the first step to capturing what is available to your organisation.

1. EDP Service Credits

Enterprise Discount Program agreements frequently include a service credits component on top of the base discount. These credits are provided as an incentive to sign or renew the EDP, and their size is directly negotiable as part of the EDP commercial terms. Typical EDP service credits range from $25K to $250K+ depending on commitment size and competitive dynamics. Credits are often tiered across the EDP term — for example, $50K in year 1, $30K in year 2, $20K in year 3.

EDP credits are typically unrestricted (applicable to any eligible AWS service) and have an expiry date. When negotiating EDP credits, pay attention to the expiry terms — credits expiring within 12 months may not be fully consumed if your consumption ramp is gradual.

2. Migration Credits

AWS has a dedicated migration incentive programme designed to offset the cost of moving workloads from on-premises or competing cloud environments to AWS. Migration credits are typically offered for:

  • Server migration projects (on-premises to EC2)
  • Database migration projects (on-premises or Oracle/SQL Server to Aurora, RDS, or DynamoDB)
  • VMware/Hyper-V to AWS migrations
  • Competitor cloud (Azure, GCP) to AWS workload migration

Migration credits are provided through the AWS Migration Acceleration Program (MAP) for qualifying projects. Enterprise-scale migrations can unlock $100K–$1M+ in MAP credits, though these are tied to specific migration deliverables and milestones rather than provided as unrestricted credits.

3. Proof of Concept (POC) Credits

AWS provides POC credits to support evaluation of new AWS services or architectural patterns. These are typically smaller ($5K–$25K) and restricted to specific services being evaluated. They are commonly available through your AWS account team for:

  • Evaluating new AI/ML services (Bedrock, SageMaker)
  • Testing new Graviton instance families
  • Piloting AWS data analytics services (Redshift, EMR, Glue)
  • Evaluating AWS Outposts in a hybrid environment

4. Graviton Adoption Credits

As part of AWS's push to drive Graviton adoption, account teams have discretion to offer migration credits specifically to support x86-to-Graviton workload migration. These are typically $10K–$50K and are offered in conjunction with Solutions Architect support for the migration project. See our AWS Graviton pricing advantages guide for the commercial angle on Graviton adoption.

5. AWS Marketplace Credits

AWS Marketplace Private Offers can include credits as part of the deal structure. ISV partners selling through Marketplace sometimes provide AWS credits (funded by the ISV from their AWS programme participation) as an incentive to close Marketplace transactions. These credits count toward your EDP commitment spend. See our AWS Marketplace private offers guide for how this works in practice.

6. Partner-Funded Credits

AWS Partners (including consultancies and SIs working on your AWS programme) can apply for partner-funded credits through the AWS Partner Network to support customer workloads. These are funded from the partner's own MDF (Market Development Funds) budget rather than directly from AWS, but they appear on your bill as standard credits. If you work with an AWS Premier Partner on your migration or optimisation programme, ask whether they have partner-funded credits available.

7. Support Credits

If you experience significant service issues that result in AWS SLA breaches, AWS may issue service credits in accordance with the SLA terms of affected services. These are typically calculated as a percentage of the affected service charges for the impacted period. For most enterprise customers, service credit claims are processed reactively — but for mission-critical workloads, proactively negotiating enhanced SLA terms and credit structures as part of your EDP is worth considering.

AWS Credits Reference Table

Credit Type Typical Size Negotiable? Restrictions When to Request
EDP Service Credits $25K–$250K+ Yes — directly Usually unrestricted During EDP negotiation or renewal
Migration Credits (MAP) $100K–$1M+ Yes — via MAP programme Tied to migration milestones Pre-migration project kickoff
POC Credits $5K–$25K Yes — via account team Specific services only When scoping new service evaluation
Graviton Adoption Credits $10K–$50K Yes — via account team Migration-related services When committing to Graviton roadmap
Marketplace Credits $5K–$100K+ Via ISV/partner Marketplace-eligible services During private offer negotiation
Partner-Funded Credits $5K–$50K Via partner Programme-specific At programme kick-off with AWS Partner
SLA Service Credits Varies (% of charges) Limited Affected services only After SLA breach — claim within 30 days

How AWS Credits Work Technically

Understanding the mechanics of how AWS credits are applied prevents unpleasant surprises at billing time. AWS credits are applied in a specific order:

Credits are applied to your AWS bill automatically before any EDP discount calculation. This means that a $100K credit reduces your gross bill first, and then the EDP discount percentage applies to the remaining charges. Importantly, credits consumed in a month count toward your EDP minimum spend commitment — so credits do not "shortchange" your EDP ramp.

Credits are applied oldest-first (FIFO). If you have multiple credit batches with different expiry dates, the oldest credits are consumed first. Monitor your credit balance and expiry dates monthly through the AWS Billing Console. Unused credits that expire represent direct value leakage — a common problem for organisations that receive large credit packages during EDP negotiations but then don't consume them due to gradual ramp curves.

Credit Expiry: The Trap to Avoid

The most frequent credits-related mistake is accepting EDP service credits with a 12-month expiry when your EDP ramp period means you won't hit full spend velocity for 18–24 months. Always negotiate credit expiry dates that align with your projected consumption timeline. Request 24-month or 36-month expiry for credits provided as part of a multi-year EDP agreement. AWS will often accommodate this request without significant pushback.

Negotiation Strategy: How to Ask for Credits

Credits are not spontaneously offered in most cases — you need to ask for them at the right moment, with the right framing. The commercial calendar creates natural moments for credit requests, and understanding these moments is key to a successful credits strategy.

EDP Negotiation Window

The most important moment for credits negotiation is during EDP discussions. When your account team is seeking your signature on a multi-year spend commitment, they have internal approval authority (or can escalate to get approval) for service credits as part of the deal structure. Frame your credit request as part of the overall commercial package — not as an afterthought. A standard negotiating position: "We're prepared to commit $X million over 3 years, but we need $Y in service credits to offset the migration costs and make the business case work internally."

Migration Project Framing

For migration credits, the MAP programme requires a formal application supported by a migration plan and milestone commitments. Engage your AWS account team before the migration project begins — not after. Late-stage applications for MAP credits are less likely to be approved at full value.

Competitive Pressure

Credits requests are most successful when accompanied by credible competitive tension. If you are evaluating Azure or GCP for part of your workload, or if a significant application is up for replacement with a SaaS alternative, the competitive dynamic creates commercial motivation for AWS to offer credits to retain the workload. Our cloud vendor negotiation leverage guide covers how to structure competitive pressure effectively.

Renewal and Renegotiation Windows

EDP renewals and significant contract renegotiations are prime credits windows. AWS account teams have renewal-specific budgets for credits and incentives. If your EDP is approaching renewal, begin the credits conversation 6–9 months before expiry — not in the last 60 days when AWS knows you have limited leverage. See our software renewal timing strategy for the general framework.

10 Tactics for Maximising AWS Credits

01
Always ask — credits are not automatically offered. The baseline rule: if you don't ask for credits, you won't receive them in most cases. Build credits requests into every significant AWS commercial engagement.
02
Bundle credit requests with EDP negotiations. Credits are easiest to obtain when you are simultaneously committing to an EDP spend level. The spend commitment gives AWS's account team the business case to approve credits internally.
03
Apply for MAP before starting migration projects. MAP migration credits require pre-approval and milestone commitments. Starting the application process 6–8 weeks before migration project kickoff ensures credits are in place when needed.
04
Negotiate 24–36 month credit expiry. Standard credits may have 12-month expiry terms. For large EDP credits packages, negotiate expiry dates that match your consumption ramp. Don't accept credits you can't consume.
05
Use architectural commitments as credits leverage. Commitments to adopt Graviton, migrate to Aurora, deploy specific AWS services, or achieve certification milestones all provide AWS with reasons to fund credits that support those programmes.
06
Request POC credits for every new service evaluation. Before embarking on any significant AWS service evaluation, ask your account team for POC credits to fund the test workload. This is a low-value ask for the account team but meaningful for your teams running the evaluation.
07
Involve your AWS SA in credit applications. Solutions Architects assigned to your account can advocate for credits internally and help frame credit applications to AWS's approval process. A well-supported SA recommendation significantly improves the probability of credit approval.
08
Track credit consumption monthly. Monitor your AWS credit balance in the Billing Console monthly. Alert your procurement team when balances drop to 20% of original value — this is a signal to initiate the next credits negotiation cycle.
09
Ask about ISV partner credits via Marketplace. If you are evaluating software from AWS Marketplace ISVs, ask whether the ISV offers AWS credits as part of their private offer structure. Some ISVs allocate partner credits specifically for enterprise Marketplace deals.
10
Claim SLA credits proactively. Review your AWS service usage for SLA breaches monthly. Most customers never claim SLA credits because they don't track availability metrics at the granularity required. Use AWS Service Health Dashboard and CloudWatch to identify eligible claims and submit within the 30-day claim window.

Credits vs Discounts: The Right Balance

Credits and discounts are not interchangeable. Credits provide one-time cash-equivalent value but do not reduce your ongoing unit cost. Discounts (via EDP) reduce unit pricing permanently for the duration of the commitment. For long-term cost optimisation, discounts are structurally more valuable than credits of equivalent face value. A $100K credit consumed in year 1 of a 3-year EDP is worth $100K. A 1% improvement in EDP discount on $10M/year spend is worth $300K over the same period.

The practical implication: prioritise discount negotiations in EDP discussions and treat credits as a secondary benefit that helps fund specific programmes (migration, adoption, POC work) rather than as a substitute for securing the best possible base discount. Our AWS EDP negotiation playbook provides the framework for maximising your discount before turning attention to credits.

Want Help Maximising Your AWS Credits and Discounts?

Our specialist advisory partners understand AWS's internal approval processes and know what credits are available and when. Get matched with an expert who can help structure your next AWS commercial negotiation.

Get Matched →

Frequently Asked Questions

Do AWS credits count toward my EDP minimum spend commitment?

Yes. Credits consumed in a billing period count toward your EDP minimum commitment threshold. This is an important protection: receiving and consuming credits does not put your EDP commitment at risk of under-spend.

Can I negotiate AWS credits without an EDP?

Yes, though the amounts available outside an EDP context are typically smaller. POC credits, migration credits through MAP, and Graviton adoption credits can all be obtained independently of an EDP commitment. However, the largest credits packages are typically attached to EDP negotiations.

How long do AWS service credits last?

Credit expiry varies. EDP service credits are typically valid for 12 months from issuance unless negotiated otherwise. MAP migration credits are milestone-based with specific expiry schedules. Always negotiate expiry dates as part of the credits discussion — 24-month and 36-month terms are achievable for EDP-attached credits.

What is the AWS Migration Acceleration Program (MAP)?

MAP is AWS's formal migration incentive programme. Qualifying migration projects receive funding in the form of AWS service credits, typically structured in two phases: an assessment phase (smaller credits for discovery and planning) and a migration phase (larger credits tied to workload migration milestones). Enterprise migrations typically qualify for $100K–$1M+ in MAP funding.