forked from pivotal-cf/docs-pcf-install
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathcloudform.html.md.erb
56 lines (33 loc) · 4.21 KB
/
cloudform.html.md.erb
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
---
title: Installing Pivotal Cloud Foundry® on AWS
owner: Ops Manager
---
<strong><%= modified_date %></strong>
This guide describes how to install [Pivotal Cloud Foundry®](https://network.pivotal.io/products/pivotal-cf) (PCF) on Amazon Web Services (AWS) using the PCF CloudFormation template.
The CloudFormation template for Pivotal Cloud Foundry® 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. Contact [Pivotal Support](http://support.pivotal.io) if you cannot use CloudFormation for your installation.
<p class="note"><strong>Note</strong>: The CloudFormation template for Elastic Runtime includes a reference to another CloudFormation template for Ops Manager. For more information on how IaaS user roles are configured for each template, refer to the <a href="iaas-user-roles.html">Pivotal Cloud Foundry® IaaS User Role Guidelines</a> topic.</p>
<p class="note"><b>Note</b>: If you are performing an upgrade from PCF 1.6 to 1.7, please review <a href="upgrading-pcf.html#pcf16upgrade">Upgrading Ops Manager</a> for critical upgrade information.</p>
## Prerequisites ##
You must have the following in order to follow the procedure described here:
* An AWS account that can accommodate the [minimum resource requirements](requirements.html#aws) for a PCF installation.
* The appropriate region selected within your AWS account. See the [Amazon documentation on regions and availability zones](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html#concepts-regions-availability-zones) for help selecting the correct region for your deployment.
* The [AWS CLI](https://aws.amazon.com/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 Pivotal Cloud Foundry® requires more than the default 20 concurrent instances.
* A key pair to use with your Pivotal Cloud Foundry® deployment. [Create a key pair in AWS](http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-console-create-keypair.html).
* A registered wildcard domain for your PCF installation. You will need this registered domain when configuring your SSL certificate and Cloud Controller. See the [AWS docs on Creating a Server Certificate](http://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/ssl-server-cert.html#create-cert) for more information.
* An SSL certificate for your PCF domain. This can be a self-signed certificate, but Pivotal only recommends using a self-signed certificate for testing and development. You should obtain a certificate from your Certificate Authority for use in production. See the [AWS docs on SSL certificates](http://docs.aws.amazon.com/ElasticLoadBalancing/latest/DeveloperGuide/ssl-server-cert.html) for more information.
## Install PCF on AWS ##
Complete the following procedures to install PCF using CloudFormation:
1. <a class="subnav" href="./cloudform-template.html">Deploying the CloudFormation Template for PCF on AWS</a>
1. <a class="subnav" href="./cloudform-om-deploy.html">Launching an Ops Manager Director Instance on AWS</a>
1. <a class="subnav" href="./cloudform-om-config.html">Configuring Ops Manager Director on AWS</a>
1. <a href="http://docs.pivotal.io/addon-ipsec/installing.html">(Optional) Installing the PCF IPSec Add-On</a>
1. <a class="subnav" href="./cloudform-er-config.html">Deploying Elastic Runtime on AWS</a>
## Delete PCF on AWS ##
You can use the AWS console to remove an installation of all components, but retain the objects in your bucket for a future deployment:
* <a class="subnav" href="./deleting-aws-install.html">Deleting an AWS Installation from the Console</a>
## Additional AWS Configuration ##
See the following topics for additional AWS configuration information:
* <a class="subnav" href="./cloudform-om-ebs-config.html">Configuring Amazon EBS Encryption</a>
* <a class="subnav" href="./cloudform_elb_ssh_proxy.html">Creating a Proxy ELB for Diego SSH without CloudFormation</a>