IaaS Permissions Guidelines
Page last updated:
This topic describes practices recommended by Pivotal for creating secure IaaS user roles.
The connection between Ops Manager and IaaS providers requires IaaS accounts with appropriate permissions. These accounts act on behalf of the operator to access IaaS functionality, such as creating VMs, managing networks and storage, and other related services.
Pivotal Operations Manager and Pivotal Application Service (PAS) can be configured with IaaS users in different ways depending on your IaaS. Other product tiles and services might also use their own IaaS credentials. Refer to the documentation for those product tiles or services to configure them securely.
Pivotal recommends following the principle of least privilege by scoping privileges to the most restrictive permissions possible for a given role. In the event that someone gains access to credentials by mistake or through malicious intent, LPUs limit the scope of the breach. Pivotal recommends following best practices for the particular IaaS you are deploying.
See the recommendations detailed in AWS Permissions Guidelines.
See the permissions recommendations in Preparing to Deploy Ops Manager on Azure, and use the minimum permissions necessary when creating your service principal.
For GCP, Pivotal recommends using two different accounts with the least privilege.
Use one account with the minimum permissions required to create desired GCP resources in your GCP project, then create a separate service account with the minimum permissions required to deploy PAS and other tiles. For more information about creating the service account, see Step 1: Set up IAM Service Accounts in Preparing to Deploy Ops Manager on GCP.
Pivotal recommends following the principle of least privilege by scoping privileges to the most restrictive permissions possible for a given role.
See the vCenter permissions recommendations in Installing Ops Manager on vSphere.