Installing Pivotal Cloud Foundry on AWS
Page last updated:
This topic describes how to install Pivotal Cloud Foundry (PCF) on Amazon Web Services (AWS) using the PCF CloudFormation template.
Note: If you are performing an upgrade to PCF 1.9, see Upgrading Pivotal Cloud Foundry for critical upgrade information.
The CloudFormation template for PCF describes the set of necessary AWS resources and properties. When you create an AWS stack using the PCF template, CloudFormation provisions all the infrastructure that you need to deploy PCF on AWS.
Pivotal strongly recommends using CloudFormation to install PCF on AWS. If you cannot use CloudFormation for your installation, contact Pivotal Support.
Note: The CloudFormation template for Elastic Runtime includes a reference to another CloudFormation template for Ops Manager. For more information about how IaaS user roles are configured for each template, see the Pivotal Cloud Foundry IaaS User Role Guidelines topic.
The following sections describe general requirements for running PCF and specific requirements for running PCF on AWS.
The following are general requirements for deploying and managing a PCF deployment with Ops Manager and Elastic Runtime:
(Recommended) Ability to create a wildcard DNS record to point to your router or load balancer. Alternatively, you can use a service such as xip.io. For example,
Elastic Runtime gives each application its own hostname in your app domain. With a wildcard DNS record, every hostname in your domain resolves to the IP address of your router or load balancer, and you do not need to configure an A record for each app hostname. For example, if you create a DNS record
*.example.compointing to your router, every application deployed to the
example.comdomain resolves to the IP address of your router.
(Recommended) A network without DHCP available for deploying the Elastic Runtime VMs
Note: If you have DHCP, refer to the Troubleshooting Guide to avoid issues with your installation.
Sufficient IP allocation:
- One IP address for each VM instance
- An additional IP address for each instance that requires static IPs
- An additional IP address for each errand
- An additional IP address for each compilation worker:
IPs needed = VM instances + static IPs + errands + compilation workers
Note: BOSH requires that you allocate a sufficient number of additional dynamic IP addresses when configuring a reserved IP range during installation. BOSH uses these IPs during installation to compile and deploy VMs, install Elastic Runtime, and connect to services. We recommend that you allocate at least 36 dynamic IP addresses when deploying Ops Manager and Elastic Runtime.
The most recent version of the Cloud Foundry Command Line Interface (cf CLI)
One or more NTP servers
The following are the minimum resource requirements for maintaining a Pivotal Cloud Foundry (PCF) deployment with Ops Manager and Elastic Runtime on Amazon Web Services infrastructure:
- 1 Elastic Load Balancer
- 1 Relational Database Service. We recommend at least a db.m3.xlarge instance with 100 GB of allocated storage.
- 5 S3 Buckets
- EC2 Instances:
- 13 t2.micro
- 15 t2.small
- 2 m3.medium
- 6 m3.xlarge
- 3 m3.2xlarge
You must have the following to install PCF on AWS:
- An AWS account that can accommodate the minimum resource requirements for a PCF installation.
- The appropriate region selected within your AWS account. For help selecting the correct region for your deployment, see the AWS documentation about regions and availability zones.
- The AWS CLI installed on your machine and configured with user credentials that have admin access to your AWS account.
- Sufficiently high instance limits, or no instance limits, on your AWS account. Installing PCF requires more than the default 20 concurrent instances.
- A key pair to use with your PCF deployment. For more information, see the AWS documentation about creating a key pair.
- A registered wildcard domain for your PCF installation. You need this registered domain when configuring your SSL certificate and Cloud Controller. For more information, see the AWS documentation about Creating a Server Certificate.
- An SSL certificate for your PCF domain. This can be a self-signed certificate, but Pivotal recommends using a self-signed certificate for testing and development. You should obtain a certificate from your Certificate Authority for use in production. For more information, see the AWS documentation about SSL certificates.
Complete the following procedures to install PCF using CloudFormation:
You can use the AWS console to remove an installation of all components, but retain the objects in your bucket for a future deployment:
See the following topics for additional AWS configuration information: