What is PRM?

AWS Partner Revenue Measurement (PRM) is AWS's mechanism for measuring partner impact based on actual AWS infrastructure spend tied to your solutions. Starting July 31, 2026, PRM compliance is required to remain eligible for AWS funding benefits.

Instead of estimated metrics like ARR and TCV, AWS will now measure attributed revenue — real infrastructure spend tied to your solutions across partner and customer accounts. This is becoming one of the most heavily indexed metrics for how AWS evaluates and invests in partners.

Why This Matters

• Funding & incentives — AWS will use attributed revenue to inform investment payouts, co-sell opportunities, and program incentives.

• Growth visibility — Infrastructure spend trends are tangible, verifiable evidence of growth, stronger than self-reported ARR when requesting AWS investment.

• Competitive advantage — If you are growing but don't yet have scale, this is one of the best ways to get AWS's attention with hard data.

Three Steps to PRM Compliance

Prerequisites

Before your team begins resource tagging, confirm the following are in place:

• AWS Marketplace listing is live — Must be in public status (AWS is moving away from allowing limited listings)

• Partner Central account is migrated to 3.0 — This is a prerequisite for PRM compliance

• AWS account is linked to Partner Central — Verify on the Partner Central homepage

• You have your Marketplace product code — This is the unique identifier used in the tag value. You can check how to get this code by reading the doc here

The Tag Format

Every eligible AWS resource must be tagged with a single key-value pair:

Example

Key:   aws-apn-id
Value: pc:5ugbbrmu7ud3u5hsipfzug61p

Where to Apply Tags

Which Accounts

Tag resources in all accounts where your solution provisions or manages AWS infrastructure:

If your solution spans both partner-owned and customer-owned accounts, tag eligible resources in both.

Which Resources

Tag all resources under all eligible AWS services. AWS publishes a full list of included services in their documentation under "Included AWS Services."

Recommended approach:

1. Start with core infrastructure — The resources that form the backbone of your solution (compute, storage, databases)

2. Expand to supporting services — Networking, monitoring, queues, and other services your solution uses

3. Aim for comprehensive coverage — AWS uses attributed revenue as a primary metric. The more completely you tag, the more accurately your impact is measured

Read the doc here for more details.

Common Eligible Services

Step-by-Step Tagging Instructions

Option A: AWS Console (Manual)

Best for: Quick tagging of a small number of resources.

1. Navigate to the AWS service (e.g., EC2, S3, RDS)

2. Select the resource

3. Go to the Tags tab

4. Click Add tag (or Manage tags)

5. Enter the key and value:

Key:   aws-apn-id
Value: pc:<your-product-code>

1. Click Save

Option B: AWS CLI

Best for: Scripting tags across multiple resources.

Tag an EC2 instance

aws ec2 create-tags \\
  --resources i-0abcd1234efgh5678 \\
  --tags Key=aws-apn-id,Value=pc:<your-product-code>

Tag an S3 bucket

aws s3api put-bucket-tagging \\
  --bucket my-bucket-name \\
  --tagging 'TagSet=[{Key=aws-apn-id,Value=pc:<your-product-code>}]'

Tag an RDS instance

aws rds add-tags-to-resource \\
  --resource-name arn:aws:rds:us-east-1:123456789012:db:my-db \\
  --tags Key=aws-apn-id,Value=pc:<your-product-code>

Option C: Infrastructure as Code (Recommended for Scale)

Best for: Ensuring all current and future resources are automatically tagged.

Terraform

# Tag individual resources
resource "aws_instance" "example" {
  # ... other config ...
  tags = {
    aws-apn-id = "pc:<your-product-code>"
  }
}

# Or use default_tags on the provider (recommended)
provider "aws" {
  default_tags {
    tags = {
      aws-apn-id = "pc:<your-product-code>"
    }
  }
}

CloudFormation

Resources:
  MyInstance:
    Type: AWS::EC2::Instance
    Properties:
      # ... other config ...
      Tags:
        - Key: aws-apn-id
          Value: pc:<your-product-code>

Please refer to the detailed AWS documentation on Resource tagging.

Important Rules and Constraints

Tagging in Customer Accounts

When your solution deploys resources into customer AWS accounts, here is what to communicate.

What Customers Should Know

• It's straightforward — Adding a single tag key-value pair to resources your solution provisions.

• They retain full control — Customers can add or remove tags at any time.

• Their data is protected — AWS does not share individual customer revenue with partners. Only aggregated data is shared, and only when minimum customer thresholds are met.

Benefits for Customers

• Map costs to specific partner solutions

• Better visibility into portfolio spending

• More informed resource allocation decisions

• Complete control over tags — can add or remove at any time

Customer Privacy Protections

AWS has strong privacy guardrails in place:

• AWS does not share revenue tied to an individual customer with partners

• Only aggregated data is shared, aggregated to the point that a partner cannot reverse-engineer individual customer usage

• Aggregated revenue data is shared monthly by partner product and AWS service when defined customer thresholds are met

• PRM data is not used to improve AWS products or develop competing offerings

• A partner's attributed revenue information is not shared with other partners, competitors, or industry analysts

Troubleshooting & Verification

Verification Checklist

• Marketplace listing is in public status

• Vendor management account for the listing is linked to Partner Central

• Tag key is exactly aws-apn-id (case-sensitive)

• Tag value follows the format pc:<product-code> with no extra spaces

• Tags are on the AWS resources, not the Marketplace listing ARN

• Resources in both partner and customer accounts are tagged (where applicable)

• All eligible service resources are tagged (not just core compute)

What to Collect for Troubleshooting

If attribution is not appearing as expected, collect the following three screenshots and share with the Clazar team. This minimises back-and-forth during troubleshooting:

Frequently Asked Questions

• Can tags be managed through the Marketplace UI?

  No. Tags must be applied directly on AWS resources via the Console, CLI, or Infrastructure as Code. No new Marketplace release is needed for tagging.

• Does tagging apply to the AMI or the listing?

  Neither. Tags go on the running AWS resources (e.g., the EC2 instance), not the AMI or the listing.

• Should we tag resources in our account, customer accounts, or both?

  Both. Tag all eligible resources in every account where your solution provisions infrastructure.

• Should we tag only core resources or everything?

  Aim for comprehensive coverage. AWS uses attributed revenue as a primary evaluation metric — broader tagging means more accurate measurement of your impact.

• How long does it take for attribution to appear?

  AWS shares aggregated revenue data monthly. Attribution begins once tags are applied and continues until tags are removed or resources are terminated.

• What if we can't create a Marketplace listing in our country?

  PRM only requires an unpaid (free) listing, which is not bound by the same country eligibility as paid listings. You can register a free listing from any AWS-supported country.

• Does the transaction need to occur through AWS Marketplace?

  No. AWS Marketplace transactions are optional. The product code is a self-service way to obtain the unique identifier. Revenue is attributed based on consumption regardless of procurement channel.

• Can multiple partners tag the same resource?

  No. Only one partner can tag a resource with one product code at a given time. If resource ownership changes, the new partner must remove the previous tag (with customer approval) and add their own.

• How does PRM handle multi-tenant SaaS solutions?

  PRM allows AWS to distinguish between a partner's consumption as an AWS customer and the impact driven as a partner through products used by joint end customers. No additional revenue information is shared beyond what AWS already sees.

• What about MAP or other contractual investments?

  Partners should adhere to tagging requirements as outlined by their current contractual agreements. PRM capabilities can be implemented for use cases outside of these contractual agreements.

Need Help?

AWS Reference Links

• Partner Revenue Measurement Overview

• Partner Onboarding Guide

• AWS Marketplace Listing Creation Guidance

• Account Linking Guidance

• Partner Central Migration Guide

• Subsidiary Account Connections Guide

• PRM FAQ

Last updated: April 10, 2026 · Compliance deadline: July 31, 2026