Quick Answer
AWS MAP credits are financial incentives provided through the Migration Acceleration Program that offset up to 25% of eligible AWS spending during and after...
Key Topics Covered
AWS MAP credits are financial incentives provided through the Migration Acceleration Program that offset up to 25% of eligible AWS spending during and after migration. These credits are applied directly to your AWS bill, reducing the total cost of moving workloads to the cloud.
How AWS MAP Credits Are Calculated
The credit percentage applies to qualifying AWS services consumed during the migration project. Eligible spend typically includes compute (EC2), storage (S3, EBS), database (RDS), and networking services. Not every AWS service qualifies, so reviewing the approved service list with your AWS account team before planning your budget is essential.
Credits are calculated based on actual consumption, not projected usage. AWS tracks tagged resources linked to your MAP engagement and tallies the spend at the end of each quarter. The resulting credit amount is then applied to your consolidated billing account, reducing your next invoice by the credited amount.
For example, if your migration generates $200,000 in eligible quarterly spend and your agreement specifies a 25% credit rate, you would receive $50,000 in credits applied to the following quarter. This predictable model allows finance teams to forecast net cloud costs with reasonable accuracy throughout the migration timeline.
The Tagging Requirement
To receive MAP credits, every resource associated with the migration must carry a specific cost-allocation tag. AWS provides this tag key-value pair when your MAP agreement is finalized. Without proper tagging, spend on otherwise eligible services will not count toward your credit calculation.
Organizations often assign a cloud operations or FinOps team to enforce tagging standards. Automated tagging policies through AWS Organizations or infrastructure-as-code templates help ensure no resource slips through untagged. A single missed tag can mean thousands of dollars in unclaimed credits over the course of a multi-quarter migration.
AWS Cost Explorer allows you to filter by the MAP tag and verify that tagged spend matches expectations. Running this check weekly during active migration waves catches tagging gaps before they compound into a full quarter of missed credits. Many organizations also set up billing alerts tied to the MAP tag for real-time visibility.
Need help with cloud?
Book a free 30-minute meeting with one of our cloud specialists. We'll analyse your situation and provide actionable recommendations — no obligation, no cost.
Quarterly Distribution and Minimum Thresholds
MAP credits are distributed on a quarterly cycle. At the close of each quarter, AWS reviews tagged spend, calculates the credit, and issues it to the payer account. There is typically a one-quarter lag between consumption and credit application, so plan cash flow accordingly.
AWS enforces a minimum spend threshold, generally starting at $50,000 in eligible consumption. Projects below this floor may not qualify for the program. Larger migrations with annual run-rates above $1 million often receive enhanced terms, including higher credit percentages or extended eligibility windows.
The quarterly cycle means that migration timing affects credit realization. Starting a migration wave at the beginning of a quarter maximizes the tagged spend captured in that period. Conversely, launching a wave late in a quarter may push the bulk of eligible consumption into the next reporting period.
Eligibility Duration
Credits are available for a defined period, usually covering the migration phase plus a post-migration window. The migration phase aligns with your project timeline as documented in the MAP agreement. The post-migration window typically extends 12 to 24 months after workloads reach production in AWS.
Once the eligibility window closes, credits stop accruing regardless of remaining tagged resources. Planning your migration waves to maximize spend within the window is a practical way to extract full value from the program. Workloads with the highest monthly run-rate should be prioritized early.
What MAP Credits Do Not Cover
MAP credits apply only to infrastructure consumption. They do not reimburse professional services fees, third-party licensing costs, or internal staffing expenses. Marketplace purchases and support plan charges are also excluded from credit calculations.
Additionally, credits cannot be transferred between AWS accounts outside the same consolidated billing family. If your organization operates multiple payer accounts, you must coordinate with AWS to ensure the correct account receives the benefit. Reserved Instance and Savings Plan purchases may also have specific treatment under the agreement terms.
Working with an AWS Partner
Most organizations access MAP through an authorized AWS consulting partner. The partner helps prepare the business case, submit the MAP application, and manage tagging compliance throughout the project. Partners with MAP experience can often accelerate approval timelines and avoid common application mistakes.
Opsio, as an AWS Advanced Consulting Partner, guides organizations through the full MAP lifecycle from application to credit realization. Learn more about our AWS migration services or read our detailed guide on what the AWS Migration Acceleration Program includes.
Maximizing Your Credit Value
Start tagging resources from day one of the engagement. Conduct monthly audits to verify tag compliance and catch gaps early. Align migration waves so the highest-spend workloads land within the credit eligibility window, and work closely with your AWS account team to confirm service eligibility before committing to architectural decisions.
Consider scheduling your most compute-intensive migration activities, such as database replication and parallel testing environments, during periods when they will generate the most tagged spend. Decommissioning on-premises resources promptly after cutover also helps concentrate AWS spend within the credit window rather than running dual environments longer than necessary.
Written By
Country Manager, Sweden at Opsio
Johan leads Opsio's Sweden operations, driving AI adoption, DevOps transformation, security strategy, and cloud solutioning for Nordic enterprises. With 12+ years in enterprise cloud infrastructure, he has delivered 200+ projects across AWS, Azure, and GCP — specialising in Well-Architected reviews, landing zone design, and multi-cloud strategy.
Editorial standards: This article was written by cloud practitioners and peer-reviewed by our engineering team. We update content quarterly for technical accuracy. Opsio maintains editorial independence.