AWS Partner Central permissions best practices

When assigning AWS Partner Central roles, use the following guidelines.

Assign roles according to the principle of least privilege

Users should have permissions to access only those resources that they need to perform their jobs. For example, if one of your team members is responsible only for updating and reporting on opportunities across your pipeline in the APN Customer Engagements (ACE) Pipeline Manager they should have the ACE manager role, not the alliance team role. For more information, refer to https://docs.aws.amazon.com/IAM/latest/UserGuide/best-practices.html#grant-least-privilege.

Audit role assignments

Periodically audit your role assignments and adjust permissions as people change roles at your organization. Audit your user list to ensure you have deactivated users who have left your organization or moved to roles that no longer require access to AWS Partner Central.

Use unique credentials

Ensure that users log in to AWS Partner Central with unique login credentials. Sharing user credentials violates the AWS Partner Network and AWS Partner Network Customer Engagements (ACE) terms and conditions and creates security risks.

Avoid generic logins

Avoid keeping a generic login (for example, APN_Admin@company.com) assigned to the alliance lead role. Follow best practices for managing permissions and avoid having multiple users sign in to AWS Partner Central with the same generic credentials. Instead, reassign an individual user to the alliance lead role, assign other users to the roles they require, and deactivate the generic account.