Configure AWS Partner Revenue Measurement (PRM) with Resource Tagging

AWS Partner Revenue Measurement (PRM) allows AWS Partners to demonstrate how their products drive AWS service consumption and revenue.

With Resource Tagging, you associate your AWS Marketplace product with the AWS resources used by your solution. AWS uses these tags to attribute eligible AWS service consumption to your product.

This guide explains how to configure PRM Resource Tagging yourself and provides guidance on choosing the best way to apply the required tag to your AWS resources.

Who is this guide for?

This guide is intended for AWS Partners who want to configure PRM Resource Tagging directly in their AWS account or, where applicable, a customer AWS account.

Resource Tagging can be used for resources deployed in your AWS account, a customer's AWS account, or a combination of both.

🚀 Before you begin

Make sure you have:

• An active AWS Marketplace product listing.
   
• The AWS Marketplace product code for the product you want to attribute.
   
• Access to the AWS production account containing the resources used by your solution.
   
• Resources running on AWS services supported by PRM Resource Tagging.
   
• Cost Explorer enabled in the relevant AWS account.

SaaS and Professional Services

Resource Tagging is commonly used for SaaS and Professional Services solutions, particularly when the AWS resources generating consumption can be identified and tagged.

➡️ Step 1: Find your AWS Marketplace product code

Your product code uniquely identifies your AWS Marketplace product and is required for PRM Resource Tagging.

To find it:

1. Sign in to the AWS Marketplace Management Portal.
2. Open Products.
3. Select the product you want to configure.
4. Locate the Product Code in the Product Summary section.

Your product code will look similar to:

5ugbbrmu7ud3u5hsipfzug61p

Fig. 1

➡️ Step 2: Prepare the PRM tag

PRM requires a specific tag key and value format.

Tag key

aws-apn-id

Tag value

pc:<your-product-code>

For example:

aws-apn-id = pc:5ugbbrmu7ud3u5hsipfzug61p

Make sure the format is exact

• Use lowercase aws-apn-id for the tag key.
• Include the pc: prefix in the tag value.
• Replace <your-product-code> with your actual AWS Marketplace product code.
• Do not use your APN ID as the tag value.

AWS requires this exact format for Resource Tagging.

➡️ Step 3: Open AWS Tag Editor

AWS Tag Editor allows you to find and tag multiple AWS resources from the AWS Management Console.

To open Tag Editor:

1. Sign in to the AWS Management Console.
2. Open Resource Groups & Tag Editor.
3. Select Tag Editor.

Fig. 2

➡️ Step 4: Select the resources used by your solution

In Tag Editor:

1. Select the AWS Region(s) where your resources are running.
2. Select the AWS service/resource types used by your solution.
3. Select Search resources.

Select only the resource types that are actively used by your product and generate AWS consumption.

For example, depending on your architecture, these may include:

• Amazon EC2
• Amazon EBS volumes
• Amazon RDS
• Amazon DynamoDB
• Amazon ECS
• Amazon EKS
• Amazon S3

Fig. 3

➡️  Step 5: Select the resources to tag

After you search, Tag Editor displays the resources that match your selection.

1. Review the results.
2. Select the resources associated with your solution.
3. Select Manage tags of selected resources.

➡️ Step 6: Add the PRM tag

Add the following tag:

Tag key

aws-apn-id

Tag value

pc:<your-product-code>

For example:

aws-apn-id = pc:5ugbbrmu7ud3u5hsipfzug61p

Then review and apply the tag changes.

➡️ Step 7: Repeat for all applicable resources

Repeat the process for the AWS resources that contribute to your product's AWS service consumption.

For example, if your solution uses EC2 instances and their associated EBS volumes, make sure the applicable resources are tagged.

AWS notes that PRM attribution applies to supported AWS services and resources.

If your resources are managed through Infrastructure as Code

If your resources are created or managed through CloudFormation, AWS CDK, or Terraform, AWS recommends applying the PRM tag through your infrastructure-as-code configuration rather than manually through Tag Editor.

This helps prevent configuration drift when your infrastructure is updated.

⚙️ PRM Tagging Checklist

Before considering your implementation complete, verify that:

✅  The correct AWS Marketplace product code is being used.

✅  The tag key is exactly aws-apn-id.

✅  The tag value starts with pc:.

✅  The product code in the tag matches the AWS Marketplace product.

✅  The tag has been applied to the relevant supported AWS resources.

✅  The tagged resources are actively generating AWS service consumption.

✅  All relevant Regions have been considered.

✅  Cost Explorer is enabled.

🛠️ Troubleshooting

If your tagged resources are not generating PRM attribution, first verify:

1. The tag key is exactly aws-apn-id.
2. The tag value follows the format pc:<product-code>.
3. The product code matches the product in AWS Marketplace.
4. The resources belong to an AWS service supported by PRM.
5. The resources are actively consuming AWS services and generating charges.

AWS recommends providing your AWS account ID, Region, product code, sample resource ARN, and evidence of the tag configuration when contacting AWS Support about attribution issues.

💬 Need help?

If you have completed the tagging steps but need help validating your PRM implementation, contact your Labra Customer Success representative.