- Newest
- Most votes
- Most comments
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:
- Keep the
aws-apn-id=pc:<product-code>tags in place. - Validate with a supported production-like workload rather than relying only on a few-hour test stack.
- Allow the documented 7-day window.
- 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
Relevant content
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 7 months ago
