Getting started with Partner Revenue Measurement - AWS Partner Revenue Measurement
Partner Revenue Measurement Architecture PatternsImplementation Steps

Getting started with Partner Revenue Measurement

Partner Revenue Measurement measures AWS service consumption driven by partner products. This enables AWS to attribute revenue to partner solutions and provide aggregated consumption data back to partners.

Partner Revenue Measurement supports three implementation methods:

  • AWS Marketplace Metering — Zero-touch revenue attribution for Amazon Machine Image (AMI) and Machine Learning (ML) products listed on AWS Marketplace

  • Resource Tagging — Tag AWS resources with your product code for revenue attribution

  • User Agent String — Include a User Agent string in regular AWS API/CLI calls for revenue attribution

To implement Partner Revenue Measurement, consider the following requirements:

  • What AWS services does your product use (Amazon EC2, Amazon S3, Amazon ECS, Amazon RDS)?

  • Do you have a SaaS, AMI, ML, or Professional Services product listed on AWS Marketplace?

  • Which architecture pattern does your solution follow (Partner account, Customer account, or Hybrid)?

Note

Partner Revenue Measurement requires implementation of one or more methods to enable revenue attribution for supported AWS services.

Partner Revenue Measurement Architecture Patterns

Pattern #1 - Partner Account: All components reside within the partner's AWS account or VPC.

Pattern #2 - Customer Account: All components are deployed in the customer's AWS account and VPC.

Pattern #3 - Hybrid: Components are distributed across both partner and customer AWS accounts and VPCs.

Partner Revenue Measurement architecture patterns showing partner account, customer account, and hybrid deployment models

Implementation Steps

Partner Revenue Measurement Implementation Process

  1. Step 1: Complete Prerequisites

    Review Prerequisites

  2. Step 2: Retrieve Product Code

    Retrieve your product code from AWS Marketplace Management Portal

  3. Step 3: Choose Implementation Method

    Select one or more implementation methods based on your product type and architecture

  4. Step 4: Complete Method-Specific Requirements and Implement

    Review the method-specific requirements for your chosen method, then follow the implementation guide. For a low-effort approach at scale, consider using automation where available.