LATEST VERSION: 1.9 - CHANGELOG
Pivotal Cloud Foundry v1.7

Pivotal Cloud Foundry IaaS User Role Guidelines

This topic describes practices recommended by Pivotal for creating secure IaaS user roles.

Pivotal Cloud Foundry (PCF) is an automated platform that connects to IaaS providers such as AWS and OpenStack. This connectivity typically requires accounts with appropriate permissions to act on behalf of the operator to access IaaS functionality such as creating virtual machines (VMs), managing networks and storage, and other related services.

Ops Manager and Elastic Runtime 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.

Least Privileged Users (LPUs)

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 gets 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.

Configuring IaaS User Roles on AWS

Pivotal recommends using the CloudFormation templates for Pivotal Cloud Foundry to configure AWS deployments to create users with least privilege. Pivotal also recommends minimizing the use of master account credentials by creating an IAM role and instance profile with the minimum required EC2, VPC, and EBS credentials.

Note: If you choose not to use the CloudFormation templates, Pivotal encourages you to use the permissions determined by PcfIamPolicy section of the Ops Manager CloudFormation template to create users with appropriate permissions. Additionally, follow AWS account security best practices such as disabling root keys, multi-factor authentication on the root account, and CloudTrail for auditing API actions.

See the table below for more information on the two CloudFormation templates.

Template Source Location User(s) Created User Purpose Uses IAM Role Additional Documentation
Elastic Runtime Pivotal Network Elastic Runtime Download ERT S3 user Blob storage No Deploying Elastic Runtime on AWS
Ops Manager Referenced in the ERT template Ops Manager VM and Ops Manager Director EC2, VPC, EBS, S3, ELB Yes Director User Config

For more Amazon-specific best practices, refer to the following Amazon documentation:

Configuring IaaS User Roles on vSphere

See the vCenter permissions recommendations in vSphere/vCenter Requirements.

Configuring IaaS User Roles on vCloud

See the installation instructions and follow the least privilege user configuration for accounts.

Configuring IaaS User Roles on OpenStack

See the installation instructions and follow the least privilege user configuration for tenants and identity.

Was this helpful?
What can we do to improve?
View the source for this page in GitHub