AWS MAP Credits: Eligibility, Tiers & Tracking | Opsio

Eligibility Requirements

To qualify for MAP credits, organizations must meet minimum migration thresholds and work with a certified AWS Migration Competency Partner. Key requirements include:

• Minimum migration scope of 10 servers or equivalent cloud workloads
• Engagement with an AWS Partner holding active Migration Competency
• Commitment to complete migration within the agreed program timeline
• Adoption of MAP 2.0 tagging requirements for all migrated resources
• Agreement to AWS program terms and reporting requirements

Organizations with existing AWS workloads can still qualify if they are migrating additional infrastructure. Learn more about MAP funding options and application steps.

Setting Up MAP 2.0 Tagging

Correct tagging is mandatory for credit allocation under MAP 2.0 — untagged resources will not generate credits. Follow these steps to configure tagging:

1. Activate your tag key: In the AWS Billing console, activate the MAP tag key provided by your AWS Partner
2. Assign tag values: Apply the correct tag values to every resource associated with the migration
3. Validate tagging: Use AWS Tag Editor to audit resources and ensure all migrated workloads carry the correct tags
4. Monitor compliance: Set up AWS Config rules to detect and alert on untagged or incorrectly tagged resources

Your MAP Partner should provide the specific tag key and values for your engagement. See the AWS MAP 2.0 Tagging Guide for detailed technical instructions.

Tracking Credit Utilization

AWS provides billing-level visibility into MAP credit allocation and consumption through the AWS Billing console. Best practices for credit tracking include:

• Review credit balances monthly in the AWS Billing and Cost Management console
• Set up billing alerts for credit utilization milestones (50%, 75%, 90%)
• Track credit expiration dates and plan workload migration accordingly
• Coordinate with your AWS Partner on quarterly credit reconciliation

Maximizing MAP Credit Value

Organizations that plan strategically can maximize the financial benefit of MAP credits beyond the basic migration offset. Consider these strategies:

• Prioritize high-cost workloads: Migrate compute-intensive workloads first to maximize credit offset against the highest AWS bills
• Use credits for modernization: Apply credits toward containerization (ECS/EKS) or serverless (Lambda) transitions that reduce long-term costs
• Time migrations strategically: Align migration waves with credit availability windows to avoid gaps in coverage
• Invest in training: Use training allowances to upskill internal teams, reducing future consulting dependency

Frequently Asked Questions

Do MAP credits expire?

Yes, MAP credits have defined expiration dates tied to your program agreement. Typically, credits must be consumed within 12-24 months of allocation. Work with your AWS Partner to ensure migration timelines align with credit availability.

Can MAP credits be used for any AWS service?

MAP credits generally apply to most AWS compute, storage, and database services. However, some services and third-party marketplace purchases may be excluded. Check your specific program agreement for covered services.

What happens if I do not tag resources correctly?

Untagged or incorrectly tagged resources will not count toward your MAP credit allocation. This is the most common reason organizations receive fewer credits than expected. Implement automated tagging validation using AWS Config to prevent this issue.

Can I combine MAP credits with other AWS discount programs?

MAP credits apply after other discounts such as Reserved Instances or Savings Plans. You can use both programs simultaneously, with credits applying to any remaining on-demand charges after volume discounts.

How do I apply for AWS MAP credits?

You cannot apply for MAP credits directly. Credits are allocated through your AWS Migration Competency Partner as part of a structured MAP engagement. Contact Opsio or another qualified partner to initiate the process.