Frequently Asked Questions (FAQs)

Below you'll find answers to the most common questions you may have on MAP 2.0.

How can I create Amazon Bedrock inference profiles to use supported foundation models?

See Track, allocate, and manage your generative AI cost and usage with Amazon Bedrock. You must tag the inference profile as described in Tagging Resources.

What are the supported foundation models in Amazon Bedrock?

For a list of supported foundation models that are eligible for MAP credits, see Supported foundation models in Amazon Bedrock. To gain access to these supported foundation models and purchase any provisioned throughput, you must use the Amazon Bedrock Console or API.

Why is tagging required for MAP 2.0?

Tagging is a way to assign a label to an AWS resource. Tags enable you to categorize your AWS resources in different ways. For example, you can categorize by purpose, owner, department,or environment. Each tag consists of a key and an optional value (for example, Department: Finance), both of which you define. For the purposes of MAP, you must tag migrated workloads with the map-migrated tag to enable the following:

The tagging exercise is done when the workload is migrated to AWS. Typically, tags are applied by the workload owners who will be migrating their workloads. This process is repeated as workloads are moved across until the entire MAP migration scope has been migrated. Tagging your AWS resources is a best practice even outside of MAP. For more information, see the Tagging Best Practices Whitepaper.

Should I activate the Cost Allocation Tag?

The Migration Acceleration Program requires that you tag resources with the map-migrated tag. This tag is automatically activated for you as a cost allocation tag in the management (payer) account that is mentioned in the MAP project plan. For the MAP 2.0 terms signed between November 01, 2022 and November 18, 2024, the cost-allocation tag setup is not automatically activated. See Verify and Fix map-migrated cost-allocation tag.

Should migrations occur under the management (payer) account?

Migrations must occur under the management (payer) account and any accounts linked to the management (payer) account. All migrated resources that are part of the migration plan must be tagged with map-migrated as defined in this guide.

Where do I find my MPE ID?

Your project number found within your migration plan is also known as your MPE ID. For more information about your MPE ID, see MPE ID length.

How do I tag my migrated resources in AWS with map-migrated tag?

While we encourage you to automate tagging your resources, you can tag your resources in AWS in the following ways:

I’ve already onboarded to MAP 2.0 and have been following the tagging process that required CUR and a Server ID from Migration Hub. How should I proceed going forward?

For the previously existing MAP 2.0 projects, keep tagging as it was defined at the time the MAP 2.0 term was signed. For the MAP 2.0 terms signed after November 01, 2022, the related workloads should follow this tagging guide.

What is the process for baseline AWS services that cannot be tagged but may also be included in MAP (which can include VMare Cloud on AWS, Amazon Connect or AWS Managed Services)?

The process is automated for Amazon Connect, VMware Cloud on AWS, and AWS Managed Services (AMS).

Will I receive MAP incentives if I tag an existing AWS resource?

The Program Terms clearly state that only MAP resources that are launched after the agreement acceptance date are eligible for MAP incentives.

Can I use an Amazon S3 bucket that existed before the MAP agreement as destination for my migration?

You are recommended to use new S3 buckets for migration workloads. If, for any reason you have to use existing S3 buckets for migration workloads, you need to provide to your account team with the ARNs for each of the existing S3 buckets be used for migration and each bucket’s current baseline spend. This information is added to the MAP agreement. You will then need to tag these buckets during migration. For more information on how to baseline the existing S3 buckets, see the How do I find the cost of my Amazon S3 buckets guide.

What services are in scope for MAP 2.0?

You can find all eligible services for MAP in the Included Services list: https://s3-us-west-2.amazonaws.com/map-2.0-customer-documentation/included-services/MAP_Included_Services_List.pdf. Certain Specialized Services may also be included in your Migration Plan or MAP Migration Tracking and Incentive Guide. Eligible services for MAP for SAP are provided in the MAP for SAP Migration Tracking and Incentive Guide.

Are tags case sensitive?

Yes. See MAP tag.

Can I use Amazon EC2 Dedicated Hosts as part of MAP 2.0?

Yes, it is possible for you to use Amazon EC2 Dedicated Hosts as part of MAP 2.0.

What should I do if I don't see the map-migrated tag in the Cost allocation tags screen?

The Migration Acceleration Program requires that you tag resources with the map-migrated tag. This tag is automatically activated for you as a cost-allocation tag in the management (payer) account that is mentioned in the MAP project plan. For the MAP 2.0 terms signed between November 01, 2022 and November 18, 2024, the cost-allocation tag setup is not automatically activated. See Verify and Fix map-migrated cost-allocation tag.