Skip to main content

How to Tag AWS Resources for Marketplace (PRM Implementation)

Ana Medina
Updated

Overview

In this guide, you’ll learn how to tag your AWS resources using your APN ID and product code.

This step is required to ensure that AWS can correctly track your Marketplace workloads, which is important for:

  • Workload attribution
  • Program eligibility (e.g., funding opportunities)
  • Avoiding delays in AWS validation and reporting

📒  Note: This process must be completed across multiple resource types. While repetitive, it ensures all relevant infrastructure is properly tracked by AWS.

 

 

Before You Start

Make sure you have:

  • Access to your AWS Console with permissions to manage resources (AWS Admin)
  • Your Product Code (AMMP - Build - [Product Type] - Choose Product from list)

📒  Note: To view your Partner Scorecard and locate your APN ID, you’ll need to log in to the Legacy APN experience, as this information is not currently available in the new Partner Central interface.

 

 

Step-by-Step Instructions

 

Step 1: Log in to AWS Console

  • Open your AWS Console
  • If you run into login issues, try using an incognito/private window to avoid session conflicts

 

 

Step 2: Open Tag Editor

  • In the top search bar, type: Tag Editor
  • Click on Resource Groups & Tag Editor feature


    Fig. 1

 

 

Step 3: Select Scope

  • Set Regions to: All regions


    Fig. 2
     
  • Under Resource Types, you will search and tag resources one by one
    • Example: S3


      Fig. 3

 

 

🔁 Repeat the following steps for each resource type

You will go through:

  • S3
  • ECS
  • EKS
  • RDS
  • DynamoDB
  • EC2

For each resource type:

  • Click Search resources
  • If no resources are found → skip to the next resource type
  • If resources are found → apply the tags as outlined below

 

 

Step 4: Search for Resources

For each resource type:

  • Select the resource (e.g., S3)
  • Click Search resources


    Fig. 4
     

📒  Note: If no resources appear, you can skip to the next type.

 

 

Step 5: Apply Tags

If resources are found:

  • Select the resources
  • Click Manage tags of selected resources


    Fig. 5
     
  • Click Add tag to enable input fields


    Fig. 6

Enter the following:

  • Tag Key: aws-apn-id
  • Tag Value: pc: + <product-code> 
    • Example: pc:5ugbbrmu7ud3u5hsip99961p 

📒  Note:

  • The tag key  identifies your partner account
  • The Product Code links the resource to your Marketplace listing

 

 

Step 6: Apply Changes

  • Click Review and apply tag changes
  • Confirm the update

 

 

💡 Bulk Tagging

If multiple resources appear for a given resource type:

  • Select all resources of the same type (use the checkbox at the top)
  • If needed, use the settings (gear icon) to load more results
  • Apply the tag once to update all selected resources

 

📒  Note: Bulk tagging can be used for any resource type where multiple resources are returned

 

 

Step 7: Repeat for All Resource Types

Repeat Steps 4–6 for each:

  • ECS
  • EKS
  • RDS
  • DynamoDB
  • EC2

 

 

Validation / Expected Outcome

Once completed:

  • Tags should be successfully applied across all existing resources
  • You should see a confirmation message in AWS

 

 

What Happens Next

  • Your Labra team will confirm tagging with AWS
  • AWS will validate the setup on their end

 

 

Common Notes

  • This process is manual and repetitive (AWS does not currently support bulk tagging across all services at once)
  • Not all resource types will apply to every account — this is expected
  • If tagging is incomplete, it may impact reporting or program eligibility

 

 

✅ Summary

You’ve now:

  • Tagged your AWS resources using your APN ID and product code
  • Enabled AWS to track your Marketplace workloads correctly

Related to