Business decision. Mechanical execution.
MAP, Credits, Savings Plans, and negotiated discounts are AWS commercial constructs the business team manages. Each generates a decision the owner makes and a task the owner can trigger. The business approves. Engineering executes the pre-specified action or it runs automatically. The business owner never writes a CLI command.
THE EXECUTION PRINCIPLE
Every approved action becomes a clean, pre-specified task.
When a business owner approves a program action — claiming a MAP workload, allocating a credit, approving a Savings Plan purchase — FinOps Center converts that approval into a pre-specified execution task. The task is routed to the Cloud Engineer with the account, resource, and required values already filled in, or it runs automatically where no discretion is required. The business owner sees the outcome. Engineering does not make the business decision.
MIGRATION ACCELERATION PROGRAM
MAP: Derived eligibility, tracked lifecycle, no credit left on the table.
MAP credits accrue based on eligible spend against resources tagged with the MAP cost allocation tag. If a resource is missing the tag, that spend does not count and the credit does not arrive. Most teams do not find out until the milestone report lands short. FinOps Center derives eligibility and tracks every billing entity through a defined lifecycle so no migration dollar goes unclaimed.
Infrastructure resources (standard MAP)
Resource ARNs are identified as MAP-eligible from your CUR. FinOps Center tracks the lifecycle from first CUR confirmation through credit receipt. Tagging tasks are queued automatically and routed to the Cloud Engineer with account, resource ID, and required tag values pre-populated. Drift detection runs nightly and flags any STALE_TAG resources before the credit window closes.
AI workloads (MAP AI, inference profiles)
Bedrock workloads have no taggable resource ARN — the tag lives on an Application Inference Profile. FinOps Center manages three task types for MAP AI: Create Profile, Add to Profile, and Tag Profile. These run as Cloud Engineer tasks when a Product Owner's AI workload is approved for MAP participation. The inference profile is the billing entity, and FinOps Center ensures it is created, tagged, and tracked through the same lifecycle as infrastructure resources.
AWS CREDITS
Credits show up in your CUR. They do not show up on anyone's radar.
AWS credits are applied at the master payer level — pooled across every linked account. When a product owner has a workload with eligible credits, those credits do not appear against their budget. They have already been applied across the consolidated bill. Someone has to go find them, back them out of the master total, and manually apply them to the right budget owner. FinOps Center automates that process end to end.
Automatic detection from CUR
Every promotion code that appears in your Cost and Usage Report is surfaced automatically. No manual scan, no month-end surprise.
Four-level hierarchy allocation
Credits are allocated through the Business Unit, Department, Portfolio, and Product Owner hierarchy. Each owner sees only the credits that apply to their scope.
Expiry-first pooling
Credits are drawn down in expiry order — the credit expiring soonest is consumed first. No credit expires unused because a lower-priority code was applied first.
Current-month impact visibility
Product Owners see the credit impact against their current-month spending in real time, not as a retrospective line item after the bill is processed.
Unallocated credit flag
Any credit that cannot be matched to a budget owner in the hierarchy is flagged immediately. The FinOps Lead sees the gap before the credit expires.
SAVINGS PLANS
Recommendations tied to workloads. Purchase decisions owned by the business.
FinOps Center surfaces Savings Plans recommendations from the Cost Optimization Hub tied to specific workloads, so the business owner who benefits from the commitment sees the recommendation alongside their own spending context. The responsible owner approves the purchase decision. The approved action is routed to execution — either as a Cloud Engineer task or automated where the parameters are fully specified. Status is tracked against the approved decision.
NEGOTIATED DISCOUNTS
EDP and PPA terms surfaced. Realization confirmed.
Enterprise Discount Program and Private Pricing Agreement terms are surfaced in FinOps Center so the FinOps Lead can confirm whether negotiated discounts are being realized against actual spending. When spend is not drawing down an EDP commitment at the expected rate, or when a PPA term is not being applied, FinOps Center flags the gap before the contract period closes.
Make every AWS program a business-owned decision.
support@finopscenter.com