Drift detected
On the nightly pipeline run, FinOps Center finds that a resource's MAP tag has been removed, altered, or overwritten. The resource state transitions from TAGGED → STALE_TAG immediately.
Stop losing MAP credits to tagging gaps and billing confusion.
FinOps Center tracks every eligible resource through its MAP lifecycle — from eligibility confirmation through credit receipt — so no migration dollar goes unclaimed.
Your MAP credits depend on a tag your team might not know exists.
WHY DID WE BUILD?
MAP credits don't arrive automatically. They accrue based on eligible spend against resources tagged with the MAP cost allocation tag. If a resource is missing the tag, that spend doesn't count — and the credit doesn't arrive. Most teams don't find out until the milestone report lands short.
When credits do arrive, they're applied at the consolidated billing level — pooled across every linked account. The product team whose migration workload earned the credit has no native way to see their share. Finance reverse-engineers it manually, month after month.
FinOps Center closes both gaps. Every resource is tracked through a defined lifecycle. Every credit is matched to the workload that earned it. Every role sees the number relevant to their work.
CREATE MAP CONTRACT — IN FINOPS CENTER
MAP contracts created in FinOps Center — not the AWS console.
FinOps Leaders create MAP contracts directly inside FinOps Center using a guided four-step wizard. Select eligible services using Standard or AI Modernization defaults, define accounts in scope, and configure auto-enrollment rules — all without leaving the platform.
Standard defaults
One-click to apply the standard MAP eligible service set — EC2, Lambda, EKS, RDS, DynamoDB, S3. No manual checklist required.
AI Modernization defaults
Adds Amazon Bedrock and SageMaker to the eligible set. Applies when your MAP contract covers AI workload migration as well as infrastructure.
Bedrock guidance built in
When Bedrock is selected, FinOps Center flags that an Application Inference Profile is required and routes a task to Cloud Engineering — no separate reminder needed.
THE FIVE STATES
Every MAP-eligible resource has a state. Most tools don't track it.
FinOps Center assigns a lifecycle state to every resource that appears in your CUR as MAP-eligible. That state determines whether credit is accruing, at risk, or lost.
✓ELIGIBLE
Resource confirmed in CUR as MAP-eligible. mapEligibilityDate is set on first CUR confirmation. The clock starts here.
⏳PENDING_TAG
Eligible but untagged. Every day in this state is spend that won't accrue MAP credits. FinOps Center surfaces these immediately to the assigned Cloud Engineer.
🏷TAGGED
MAP cost allocation tag confirmed present and correct. Spend on this resource is accruing toward MAP credit milestones.
⚠STALE_TAG
Tag was present but has drifted — removed, overwritten, or altered. A CloudEngineeringTask is auto-created. Credit accrual stops until resolved.
Drift path from TAGGED
⚠STALE_TAG
Tag was present but has drifted — removed, overwritten, or altered. A CloudEngineeringTask is auto-created. Credit accrual stops until resolved.
→ CloudEngineeringTask
THE NIGHTLY PIPELINE
Credit matching that runs while you sleep.
When your CUR lands in S3 each morning, FinOps Center's pipeline processes every charge line — confirming eligibility, verifying tags, matching MAP credits via the mig* promotion code pattern, and updating every role's view before the workday starts.
S3 CUR Landing
CUR2 file lands in S3 ~7am daily
ProcessCUR Lambda
Event-driven trigger on S3 object creation
MAP Extension
Tags verified, eligibility states updated, drift detected
Credit Parser
promotionCode matching mig* pattern, expiry-first pooling applied
Scoreboard Metrics
MAP Compliance Rate updated per team, portfolio, product
QuickSight SPICE
Agent Bill and dashboards reflect today's MAP state by morning
S3 CUR Landing
CUR2 file lands in S3 ~7am daily
ProcessCUR Lambda
Event-driven trigger on S3 object creation
MAP Extension
Tags verified, eligibility states updated, drift detected
Credit Parser
promotionCode matching mig* pattern, expiry-first pooling applied
Scoreboard Metrics
MAP Compliance Rate updated per team, portfolio, product
QuickSight SPICE
Agent Bill and dashboards reflect today's MAP state by morning
Auto-claiming enabled
For accounts where 100% of spend is allocated to a single MAP workload, FinOps Center automatically claims credits without requiring manual attribution. Finance teams see the correct numbers without the manual reconciliation.
DRIFT DETECTION
Tags drift. MAP credit accrual stops immediately.
A TAGGED resource doesn't stay TAGGED automatically. Infrastructure changes, tag overwrites, and configuration updates all cause drift. FinOps Center detects it on the next pipeline run and acts.
CloudEngineeringTask created
A task is auto-created and assigned to the Cloud Engineer responsible for the resource. The task includes the resource ID, the last known correct tag value, the date drift was detected, and the MAP credit accrual impact per day unresolved.
Resolution confirmed
Once the tag is corrected, the next pipeline run confirms it in CUR and transitions the resource back to TAGGED. The task closes automatically. Credit accrual resumes for subsequent spend.
WHO SEES WHAT
MAP visibility scoped to each role.
Every persona in FinOps Center sees the MAP data relevant to their work — not the full billing complexity, not a generic dashboard. RBAC enforces the scope at the data layer.
FinOps Leader
- ›Portfolio-wide MAP Compliance Rate
- ›Total MAP credits claimed vs. projected
- ›PENDING_TAG exposure in dollar terms
- ›Compliance trend over rolling 30 days
Portfolio Manager
- ›Compliance breakdown by product
- ›MAP Compliance Rate in CFM Scoreboard
- ›PENDING_TAG resources per product team
- ›Credit attribution per portfolio
Cloud Engineer
- ›Assigned PENDING_TAG task list
- ›STALE_TAG drift alerts via CloudEngineeringTask
- ›Tagging confirmation timeline
- ›Resource-level lifecycle state view
Product Owner
- ›Product-level MAP credit attribution
- ›Coverage rate for owned workloads
- ›Pending tag actions that affect credit accrual
- ›Monthly credit received vs. expected
ASK YOUR MAP DATA
Every MAP question has an answer in Agent Bill.
Compliance rate, credit attribution, at-risk spend, open tagging tasks — Agent Bill answers at every level of your hierarchy, in plain language, in real time.
FinOps Leader
“How much MAP credit have we claimed this month versus what we projected?”
Agent Bill
You've claimed $47,200 in MAP credits month-to-date against a $52,000 projection. The gap is 3 resources in PENDING_TAG state in the Platform portfolio — $4,800 in daily eligible spend that isn't accruing. Two are Cloud Engineer–assigned tasks opened today. The third was tagged yesterday but the Pipeline hasn't confirmed it yet — it will resolve tonight.
CFM Scoreboard signal
MAP Compliance Rate is a weighted Scoreboard signal.
MAP Compliance Rate contributes to every team's CFM Scoreboard grade alongside CFM Efficiency Score, EDP Tracking, and Resource Ownership. A low MAP compliance rate drags the overall grade — making MAP tagging visible to leadership in the same weekly review where they see cloud spend.
See the CFM ScoreboardWHERE IT RUNS
All of this happens inside your AWS account.
Your CUR data, your MAP tags, your credit history — none of it leaves your environment. The nightly pipeline runs in your Lambda. The Scoreboard data lives in your QuickSight SPICE. FinOps Center is a tenant in your account, not a pipeline to ours.
Ready to stop guessing what your MAP credits are worth?
FinOps Center deploys in minutes from the AWS Marketplace. Your MAP lifecycle tracking starts on the first CUR landing.