Managed policy mappings
The following table shows the managed policies that must be associated with IAM identities (users/roles) for each scenario.
| Scenario | User role | Required managed policies | Notes |
|---|---|---|---|
| Full access to all AWS Partner Central and AWS Marketplace features | Alliance Lead + Marketplace |
|
|
| Access parity to Partner Central 2.0 Alliance Lead and Alliance Team | Alliance Lead |
|
AWSMarketplaceSellerProductsFullAccess gives access to solution management which is moved to AWS Marketplace |
| Access parity to Partner Central 2.0 ACE user and ACE manager | ACE manager | AWSPartnerCentralOpportunityManagement |
|
| Access parity to Partner Central 2.0 Marketing staff | Marketing staff | AWSPartnerCentralMarketingManagement |
|
| Access parity to Partner Central 2.0 Channel user | Channel user | There are 2 options here:
|
AWSPartnerCentralChannelManagement - for full access. AWSPartnerCentralChannelHandshakeApprovalManagement - for channel handshake approvals (subset of full access, ideally should be used by recipient AWS account that receives Channel handshake) |
| Technical staff | Access parity to Partner Central 2.0 Technical staff | AWSMarketplaceSellerProductsFullAccess |
|
| Full access to all AWS Partner Central features | AWSPartnerCentralFullAccess |
As solution have moved to AWS Marketplace, solution management is not part of this access | |
| Access parity to Partner Central 2.0 Cloud admin | Not applicable | Depending on which access control service is used by partners, they should use managed policies from IAM, Identity Center, or other mechanisms from external identity providers | |
| Access parity to Partner Central 2.0 Standard user | Not applicable | Standard user did not grant access to Partner Central 2.0 features. |
For more information about IAM managed policies, see Managing IAM policies. For information about attaching policies to users and groups, see Attaching a policy to an IAM user group.
