AWS Organizations and AWS Partner Network accounts

To ensure that all eligible activities in your AWS Organization's member accounts contribute to your AWS Partner Network (APN) points and programs, each project account must be individually linked to your APN Partner Central account. Linking the management/organization account alone does not automatically include member accounts:

1. APN Account Linking Requirements:

• AWS Partner Network (APN) tracks usage per linked AWS account. Only activities in accounts explicitly linked to your APN Partner Central account count toward partner points.
• The management account in AWS Organizations does not automatically propagate its APN linkage to member accounts. Each member account must be linked separately.

2. When to Link Member Accounts:

• If your project accounts (member accounts) are used for APN-related activities (e.g., customer engagements, SaaS solutions, Marketplace products, or workloads that qualify for APN programs like the Solution Provider Program), they must be linked individually.
• If only the management account is used for partner activities, linking it alone suffices. However, this is rare in multi-account setups.

3. How to Link Accounts:

• Use the APN Partner Central Portal to link each AWS account (including member accounts) to your APN account.
• Ensure the IAM user/role performing the linkage has sufficient permissions in both the AWS account and Partner Central.

4. AWS Organizations & Consolidated Billing:

• While AWS Organizations enables consolidated billing, APN linkage and usage tracking are separate from billing. Consolidated billing does not aggregate APN points.

Best practice look like:

APN Partner Central Account │ ├── Linked AWS Management Account (Organization Root) │ └── AWS Organization │ ├── Member Project Account 1 (Linked to APN) │ ├── Member Project Account 2 (Linked to APN) │ └── Member Project Account 3 (Not Linked → No APN Points) └── Other Non-Org Accounts (Linked as Needed)