How AWS MAP Credits Work — And Why Most Companies Don't Capture All of Them

AWS's Migration Acceleration Program (MAP) is one of the largest financial incentive programs in cloud. It offers substantial credits to organizations migrating workloads to AWS — credits that directly offset your bill. The dollar amounts at stake can be significant: six and seven figures for mid-market companies, and well into eight figures for large enterprises.

But most companies don't capture all the credits they're entitled to. The reason isn't that the program is hard to qualify for. It's that the tagging requirements are hard to maintain.

What the Migration Acceleration Program is

MAP is an AWS program designed to accelerate cloud adoption by reducing the financial barriers to migration. If your organization is moving workloads to AWS — from on-premises data centers, from other clouds, or from legacy platforms — MAP provides credits based on your new AWS spending.

The structure is straightforward: AWS agrees to credit back a percentage of qualified spend over a defined migration period. The credits are applied against your AWS bill, reducing your effective cost of running migrated workloads. For many organizations, MAP is the single largest cost-offset opportunity available during a cloud migration.

The program is typically structured through your AWS account team and may involve an AWS partner. Qualification depends on the scale of migration, current AWS spending, and a documented migration plan.

How the credits work

MAP credits are tied to spending on migrated workloads. This is where the complexity begins.

AWS doesn't just look at your total bill and apply a discount. Credits are calculated based on spending that's associated with resources tagged as part of the migration. Every eligible resource — EC2 instances, RDS databases, S3 buckets, Lambda functions, EKS clusters, and dozens of other services — must carry a specific MAP tag that identifies it as a migrated workload.

If a resource isn't tagged, the spending on that resource doesn't count toward your MAP credits. It's that simple, and it's where most of the money gets left on the table.

• Tag key and value must match exactly. AWS specifies the tag key (typically map-migrated) and the value format. A typo, a case mismatch, or a missing value means that resource's spend is excluded.
• Tags must be present at time of billing. If a tag is added mid-month, only the portion of spend after tagging counts. Retroactive credit for untagged periods is not available.
• Coverage must span all eligible services. Organizations frequently tag their EC2 instances but miss associated EBS volumes, network interfaces, or data transfer costs.

Where most companies lose credits

Tagging is the number-one failure point in MAP credit capture. It's not a technical mystery — everyone knows the tags need to be there. The problem is operational.

Migrations happen over months or years. New resources are provisioned daily. Auto-scaling groups spin up instances that don't inherit MAP tags. Infrastructure-as-code templates get updated without the tag. Engineers deploy to new regions or accounts where the tagging policy wasn't replicated. The result is a slow, steady drift away from compliance.

Native AWS tools can identify untagged resources, but they don't fix the problem at scale. Tag Editor is manual. Resource Groups are read-only. AWS Config can flag violations but doesn't remediate them. Organizations end up assigning engineers to manually tag resources — a process that's slow, error-prone, and constantly falling behind.

Consider what happened at ATN International. They were participating in MAP but sitting at 44% tagging compliance. That means more than half of their eligible spending wasn't generating credits. They dedicated engineering resources to the problem, and after six months of manual effort, they'd tagged approximately 5,100 resources. Progress, but nowhere near complete coverage — and every untagged resource was money forfeited.

What proper MAP tagging looks like

Effective MAP compliance has three characteristics:

1. Complete coverage.Every eligible resource across every account, region, and service carries the correct MAP tag. Not 80%. Not 95%. The goal is 100%, because every untagged resource is a credit you're not capturing.
2. Automatic maintenance.Tags are applied and corrected programmatically, not manually. When new resources are created, they're tagged immediately. When tags drift, they're corrected in real time.
3. Continuous validation.Compliance is monitored continuously, not audited quarterly. By the time a quarterly review catches a tagging gap, you've already lost two months of credits.

To return to the ATN International example: after engaging Cloudsaver's tag automation, they went from 44% to 99.7% MAP compliance in under two hours. Not two months. Two hours. The automation identified every untagged eligible resource, applied the correct tags, and established ongoing monitoring to prevent drift. The credit recovery was immediate.

How to check your MAP compliance

If you're currently participating in MAP — or planning a migration where MAP credits are part of the business case — here's how to audit your current position:

1. Pull your MAP agreement. Confirm the exact tag key and value format required. Verify the eligible services and the migration period dates.
2. Run a tag coverage report. Use AWS Resource Groups or Tag Editor to identify resources missing the MAP tag across all accounts and regions in your organization.
3. Calculate the gap.Compare tagged spend against total eligible spend. The difference is the credits you're forfeiting each billing cycle.
4. Assess your remediation capacity.Be honest about whether your team can close the gap manually, maintain compliance as the environment changes, and do it fast enough that you're not losing credits every month the problem persists.

For most organizations, step four is where the math breaks. The gap is clear, the money is real, but the operational effort to fix it manually exceeds what the team can deliver alongside their other responsibilities.

If you're mid-migration or planning one, Cloudsaver's free savings assessmentincludes a MAP compliance review. It shows your current tagging coverage, the credits you're capturing vs. forfeiting, and what automated remediation would recover — against your actual AWS environment, in 2–3 business days. No connectivity required for the initial assessment.

Read the full ATN International case study to see how 44% became 99.7% in under two hours.