> ## Documentation Index
> Fetch the complete documentation index at: https://help.nops.io/llms.txt
> Use this file to discover all available pages before exploring further.

# MAP Manager

> Track and tag AWS Migration Acceleration Program (MAP) resources to maximize your credits.

**MAP Manager** helps you track and tag resources for your [AWS Migration Acceleration Program (MAP)](https://www.nops.io/aws-map/) contracts. Getting AWS MAP credits depends on tagging migrated resources correctly and as early as possible. MAP Manager centralizes that tracking and tagging so you don't lose out on earned benefits.

## Get started

1. Sign in to [nOps](https://clara.nops.io/dashboard).
2. Connect an **active AWS integration** in Settings if you have not already. MAP Manager appears in the sidebar only when AWS is connected.
3. In the sidebar, open **Inform → MAP Manager**, or go to [clara.nops.io/map-manager](https://clara.nops.io/map-manager).
4. Click **Create MAP Project** to register a MAP migration contract, or open an existing project to track and tag its resources.

## Key features

### AWS MAP Projects Summary

The landing page shows:

* **MAP Tagged Spend** and **Benefits Realized** summary cards.
* **Current MAP Status:** a bar chart comparing tagged vs. untagged resource spend.
* **List of MAP Contracts:** every MAP project you've created, with actions to open, edit, or delete.

### Creating a MAP project

Click **Create MAP Project** and fill in:

| Field | Notes |
| - | - |
| **MAP ID** | Your AWS MAP contract's project ID. |
| **MAP Name** | A name meaningful to your team. |
| **Start Date** / **End Date** | Per your MAP contract terms. Credit Period End Date is calculated automatically. |
| **Max Credit** | Your contract's maximum credit cap. |
| **Target Spending** | Your contract's target spending amount. |
| **Credit %** (Standard MAP) | Your discount percentage for standard MAP resources. |
| **Tag Key / Tag Value** | The exact tag value string from your AWS contract, used to identify migrated resources. |
| **Windows optimization** | Yes/No, if your contract includes this incentive. |
| **MAP Optimizations** | Additional entity types your contract covers (for example, Commercial DB\&A or Private Equity), each with its own Credit % and tag settings. |
| **Filter Selection** | Optionally scope the project to specific AWS accounts, regions, or AWS services. Leave blank to include all. |

Creating a project only registers what to track. It doesn't tag any resources for you.

### Project detail

Opening a project shows:

* **View By:** switch between **Standard** and any additional entity types enabled for the project (for example, Windows Optimization).
* **MAP Tracker:** a table of your incentive credits over the migration period.
* **Current QTD Tagging Status:** a bar chart of tagged vs. untagged resource spend for the current quarter.
* **List of Resources:** every resource tied to the project, grouped by AWS service.

### Tagging resources

To tag untagged resources for MAP credit:

1. In **List of Resources**, use the **Tagged / Untagged** toggle to view untagged resources, and filter by account or region if needed.
2. Expand a service to see individual resources, and select the ones you want to tag.
3. Click **Add Migration Tag**, then **Tag Now** for the account/region group you want to tag.
4. Confirm **Yes, tag resources**. This opens **AWS Systems Manager** in a new browser tab (or multiple tabs for large batches) with the tag key, value, and resource ARN pre-filled.

Tagging happens in AWS, not automatically in nOps. You'll need access to the account and permission to use Systems Manager to complete the tag. Once tagged in AWS, it takes about a day for nOps to reflect the change.

Use **Download CSV** to export the current list of resources (tagged or untagged) for offline review.

## FAQs

<AccordionGroup>
  <Accordion title="Does creating a MAP project automatically tag resources?">
    No. Creating a project only registers what to track. You tag resources yourself from the project's **List of Resources**, which redirects you to AWS Systems Manager to apply the tag.
  </Accordion>

  <Accordion title="Why don't the numbers in nOps match AWS?">
    Check that your map-migrated tag key is set as an active Cost Allocation Tag, confirm the tagging dates line up, and use Explorer's tag filters to verify the tag was actually applied.
  </Accordion>

  <Accordion title="What permissions do I need to tag resources?">
    You need access to the AWS account the resources reside in, plus permission to use AWS Systems Manager to tag them. Ask your AWS admin if you're missing access.
  </Accordion>

  <Accordion title="How long after tagging in AWS does nOps update?">
    Typically about a day after you tag a resource in AWS, the change is reflected in MAP Manager.
  </Accordion>
</AccordionGroup>

## Related

* [Explorer](/inform/explorer): verify tag application with the tag filters and Group by
* [Dashboard](/inform/dashboard): account-wide spend summary


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.