Skip to content

FTR prerequisite "PRM enabled" still Incomplete for a Container product after Resource Tagging. Do short-lived tagged stacks in the partner's own account count, and depend on Partner Central migration

0

The FTR Validation prerequisite "AWS Marketplace product is Partner Revenue Measurement (PRM) enabled" is still Incomplete in AWS Partner Central. It is the only incomplete item. The other four are Complete.

Setup

Product: AWS Marketplace Container product, Contract pricing, visibility Limited. Delivery: a CloudFormation template that customers deploy into their own account (ECS Fargate, RDS SQL Server, ALB). Accounts: we have a single Marketplace seller account, and Partner Central is linked to that same account. Cost Explorer: enabled. aws ce get-cost-and-usage returns real data.

What I implemented (Resource Tagging)

I added aws-apn-id = pc:<product-code> to the RDS instance, ECS cluster, task definition and ECS service. The service sets PropagateTags: TASK_DEFINITION. I checked the tag with the CLI on the RDS instance, cluster, task definition, service and the running Fargate task. The product code matches the Product Summary in AMMP. The key and value format follows the PRM onboarding guide.

What happened

I ran two test stacks from the template for a few hours each, in our own linked seller account. I tore both down and they are no longer running. The prerequisite is still Incomplete a few days later. The FTR page says the check completes when the product appears in the Attributed Revenue dashboard as an onboarded product, which can take up to 7 days. I can't open that dashboard. It isn't in the Analytics dashboard dropdown, and our Partner Central 3.0 migration wizard is stuck. The Verification status page shows both checks Complete, but the wizard still shows that step as Not started.

What the docs say

The Method-Specific Requirements page says tagging in your own account or a customer's account is acceptable. The Partner FAQ lists the Partner Account pattern as supported. The Prerequisites page lists migration only for partners with multiple Marketplace accounts, not for a single-account partner. The Attributed Revenue documentation says the dashboard is accessible after migrating. I found no documented minimum runtime or spend for a tagged resource to register. Sources disagree on timing: 7 days after enabling, versus a monthly cycle with a lag after month end.

Questions

Does a tagged stack that runs only a few hours in the partner's own linked account register as "onboarded"? Or does it need sustained or production consumption? Is there a minimum runtime or spend? Which timing applies to this FTR check: the 7 days after enabling, or a monthly cycle that only surfaces data after the billing month closes? Does this check depend on completing the Partner Central 3.0 migration, or is it evaluated independently of whether I can open the dashboard? Has anyone cleared this prerequisite for a Container product? What exactly did you deploy, and how long did it take?

1 Answer
0

From the current AWS documentation, resource tagging in the partner's own account is supported, so a customer account is not required. However, AWS states that PRM is intended to measure production workloads; dev/test/staging stacks can be used for validation. I couldn't find any documented minimum runtime or minimum spend requirement.

For the FTR prerequisite specifically, AWS says that after enabling PRM, the check can take up to 7 days, and it becomes complete when the product appears as onboarded in the Attributed Revenue dashboard.

One important distinction: the Attributed Revenue dashboard itself requires Partner Central migration, so not being able to access the dashboard may be related to the migration. However, the FTR documentation does not explicitly state that completing the migration is a prerequisite for PRM measurement itself.

I would therefore:

  1. Keep the aws-apn-id=pc:<product-code> tags in place.
  2. Validate with a supported production-like workload rather than relying only on a few-hour test stack.
  3. Allow the documented 7-day window.
  4. If it remains incomplete after that, raise an AWS Partner Central support case and provide the product ID, product code, linked account ID, tag examples, and exact timestamps of the test workloads.

Official docs:

answered a month ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.