fieldnotes
PRM lands with a thud
2026-02-06
What’s this one all about then ?
So overnight, an AWS proclamation was issued regarding PRM - Partner Revenue Measurement. We’ll take a first look (and probably a few more) here.
The broadcast
Dear AWS Partner,
We’re launching Partner Revenue Measurement capabilities to enable AWS Partners to gain visibility into how
their solutions impact AWS service consumption across Partner-managed or customer-managed accounts.
As Partner Revenue Measurement becomes foundational for Partner collaboration and performance discussions, Partners
must complete the following requirements by July 31, 2026, to maintain eligibility for AWS Partner Funding Benefits.
* Have a listing in AWS Marketplace (public or limited);
* Link an AWS account to your AWS Partner Central account (this will serve as the primary account for managing all
APN-related activities). Review detailed guidance on which AWS account to select in Partner Central (login required); and
* Tag AWS resources using the product code from your AWS Marketplace listing to track the revenue driven by at least one
* of your solutions with Tag Key: aws-apn-id and Tag Value: pc:<AWS Marketplace product-code>. Note: AMI, ML, Containers
* should be in customer-managed account, Professional Services and SaaS can be in either Partner-managed or customer-managed
accounts.
Benefits:
* Automated revenue insights based on actual AWS usage attribution – Validate estimates and commitments with data on AWS
service consumption patterns and revenue impact.
* Stronger influence in AWS engagements – Leverage performance data to drive business reviews, roadmap discussions, and
GTM planning, while ensuring recognition based on actual revenue generation.
* Enhanced co-selling capabilities – Build stronger business cases for AWS investments with attributed revenue data.
* Customer visibility and cost management – Enable customers to identify and track Partner-provisioned resources and map
costs for better spend management.
Next steps:
* Review updated Funding Policy in Partner Central (login required)
* Apply AWS resource tags in your account or end-customer account using the product code in your AWS Marketplace listing.
For step-by-step guidance, refer to the Partner Revenue Measurement documentation.
* Apply AWS resource tags to at least one of your solutions and validate the tag with Tag Editor by July 31, 2026.
Our take
Its not unreasonable, but it sure feels a bit like a stick rather than a carrot.
- Funding eligibility will require PRM after a certain date (31 Jul 26).
- Partner Central 3.0 (in Console) migration is required before PRM works - thats a pull forward of the previously advertised date of 30 Sep 26). We get it, backporting new features from PC 3.0 into legacy PC is extra work (but maybe the backstory here is also that PC 3.0 migrations are not happening fast enough … ?)
- A marketplace listing is required before PRM works - the listing gives you the product code. Partners not on Marketplace just got a hurry up - list something and get a code for PRM and then tag something before 31 Jul.
Besides the stick vs carrot piece there are a couple of problems we can see up front:
- Not all services take resource tags. Maybe there will be a release later with a user agent string or something similar.
- Tags are not durable. Customers hate them in production, and routinely remove them, plus there are no policy level protections for tags (you can create a policy to find untagged resources/out of policy compliance but you can’t prevent someone from adding/removing tags)
- No way to view PRM data as a partner yet. So you are limited to proving things were in place by one of Resource Explorer or Cost Explorer with activated tags.
- Customer benefits about visibility aren’t accompanied by any tooling as yet.
There also appears to be a low bar initially: tag something, anything by 31 Jul to remain funding eligible. Is that really enough ?
The wrap up
This feels very “Day 1” in terms of functionality but its a clear signal that AWS are setting some new foundations to build on.
Of course you can ignore all of this if you don’t care about AWS funding benefits after 31 Jul. But reading between the lines, its going to be about more than funding, so probably wise to do the basics. We’ll look at the practicalities in a couple of future posts.