Skip to main content

How to Apply the AWS PRM Tag Using AWS Tag Editor

Pawan Kumar
Updated

This guide explains how to apply the required PRM tag to your AWS resources using the AWS Tag Editor. Correct tagging helps ensure your partner-led workload is properly attributed for AWS reporting and programs.

 

Why This Is Important

AWS uses resource tags to identify and track partner-led workloads. Applying the PRM tag correctly ensures: - Accurate workload attribution - Smooth validation during AWS reviews - No delays in downstream reporting or program eligibility

 

Before You Start

Please make sure you have: - Access to the AWS Management Console - The AWS Region where your resources are deployed - Your AWS APN ID (this will be used as the tag value) - A list of AWS resources that belong to the eligible workload

 

Important Note

Tag one service at a time.

The option to apply tags will only appear if a single AWS service is selected in Tag Editor. If multiple services are selected, you won’t see the tagging option.

 

 


Step-by-Step Instructions

 

➡️  Step 1: Open AWS Tag Editor

  1. Log in to the AWS Management Console
  2. Navigate to Resource Groups & Tag Editor, or just search for it in the search bar in the top-left corner.
  3. Select Tag Editor from the left-hand menu

 

➡️  Step 2: Select the Region

  1. Under Regions, choose the AWS region where your workload is running

Example: us-east-1

 

➡️  Step 3: Select One Resource Type

  1. Under Resource types, select only one service

Examples: - EC2 instances - RDS databases - S3 buckets

⚠️  Do not select multiple services at once.

 

➡️  Step 4: Search for Resources

  1. Click Search resources
  2. Wait for the resource list to load

Once results appear, the Manage tags of selected resources option will be enabled.

 


Fig. 1
 

➡️  Step 5: Apply the PRM Tag

  1. Select the relevant resources
  2. Click Manage tags of selected resources
  3. Add the following tag:
  • Key: aws-apn-id
  • Value: pc:<product-code> 

    ​​Example: aws-apn-id = pc:5ugbbrmu7ud3u5hsipfzug61p
  1. Click Add tag
  2. Select Review and apply tag changes
  3. Confirm the update

 


Fig. 2


 

➡️  Step 6: Repeat for Other Services

Repeat Steps 3–5 for each additional AWS service used by your workload. Remember to tag one service at a time.

 


Fig. 3

 

Which Resources Should Be Tagged

Only tag resources that are actively used by the eligible solution.

 

Common Examples

  • EC2 instances (and attached EBS volumes)
  • RDS/DynamoDB used by the solution
  • S3 buckets used by the application
  • ECS / EKS Container compute resources

Avoid tagging shared infrastructure or unrelated environments, as this may cause incorrect attribution.

 

Troubleshooting

I don’t see the option to apply tags - Confirm only one resource type is selected - Ensure resources exist in the selected region - Click Search resources again

 

Need Help?

If you’re unsure which resources to tag or need help validating your setup, reach out to the Labra team, and we’ll be happy to assist.


 

Related articles