This topic describes how to configure the Pivotal Elastic Runtime components that you need to run Pivotal Cloud Foundry (PCF) on Amazon Web Services (AWS).
Before following this procedure, complete all steps in the Configuring AWS for PCF and Configuring Ops Manager Director for AWS topics.
Step 1: Add Elastic Runtime to Ops Manager
1. Navigate to the Pivotal CF Ops Manager Installation Dashboard.2. Click the Pivotal Network link on the left to add Elastic Runtime to Ops Manager. For more information, refer to the Adding and Deleting Products topic.
3. Click the Elastic Runtime tile in the Installation Dashboard.
Step 2: Assign Networks and Availability Zones
1. Click Assign Network.2. Select the network you created in the Networks Pages section of the Configuring Ops Manager Director for AWS topic, and click Save.
3. Click Assign Availability Zones.
4. Select the option button and checkbox to define the availability zone for singleton jobs and job balancing.
5. Click Save.
Step 3: Configure System Databases
Complete the following procedure if you want to use the external RDS instance for your Elastic Runtime databases.
Note: PCF for AWS functionality works only in the us-east-1 region. You cannot deploy PCF to any other region.
First, create the databases that Elastic Runtime requires. These instructions create those databases on the same RDS instance you created in Configuring AWS for PCF.
1. Add your key pair to your ssh profile so that you can access the machine:
ssh-add pcf.pem
2. SSH into your Ops Manager VM using its IP address and the username ubuntu: ssh ubuntu@OPS_MANAGER_IP
You can find the IP address for the Ops Manager VM on the AWS EC2 console.
3. Login to your RDS instance through the mysql client, using the hostname from the RDS console and the username you created the RDS instance with. This command prompts you to enter the password for your RDS user:
mysql -h RDS-HOSTNAME -u RDS-USERNAME -p
4. Create databases for each of the six CF components that require a database. Run CREATE database DB-NAME for each of the following: uaa, ccdb, console , notifications , autoscale, app_usage_service
5. You have now created the databases on the RDS instance. Exit the mysql client and close your connection to the Ops Manager VM.
6. Navigate to the System Database Config page of the Elastic Runtime product tile.
7. Select External Databases.
8. Enter the RDS hostname, port ( 3306), username, and password.
Step 4: Configure File Storage
Complete the following procedure if you want to use Amazon S3 for your Elastic Runtime file storage.
1. Navigate to the File Storage Config page of the Elastic Runtime product tile.
2. Select Amazon S3.
3. Enter the Elastic Runtime bucket name you chose in Create S3 Buckets.
4. Enter your Access Key and Secret Key. To retrieve your AWS key information, use the IAM credentials that you generated in Create an IAM User for PCF.
Step 5: Generate a Self-Signed Certificate
1. Select IPs and Ports.2. Leave the Router IPs and HAProxy IPs fields blank.
3. Ensure that the Loggregator Port field is set to 4443.
4. Click the Generate Self-Signed RSA Certificate link to launch the RSA certificate wizard.
5. On the Generate Self-Signed RSA Certificate window, select a wildcard domain that you own and click
Generate. The example in the image uses *.example.com.
6. Elastic Runtime populates the SSL Certificate fields with RSA certificate and private key information.
8. Click Save.
Step 6: Finalize the Load Balancer Setup
In this step, you complete your load balancer configuration that you began when setting up AWS components for PCF. For more information, see the Prepare a Load Balancer and Wildcard DNS Record section in the Configure AWS for PCF topic.
1. On the EC2 Dashboard, click Load Balancers.
2. Select the load balancer you created in the Prepare a Load Balancer and Wildcard DNS Record section of the
Configuring AWS for PCF topic. The Load balancer detail tabs display at the bottom of the page.
3. Select Listeners.
Load Balancer Port: 443
Instance Protocol: HTTP Instance Port: 80
5. Click Edit to define a third listener with the following values for use with websockets:
Load Balancer Protocol: SSL (Secure TCP) Load Balancer Port: 4443
Instance Protocol: TCP Instance Port: 80
When you click Save, AWS prompts you to enter SSL certificates for these listeners.
6. Click Change in the SSL Certificate column of the second listener.
7. On the Select Certificate page, click Upload a new SSL Certificate and complete the following information: Enter a Certificate Name.
Private Key and Public Key Certificate: Paste the RSA certificate and private key information from the SSL Certificate fields of the IP and Ports page to the appropriate field.
Click Save.
8. Click Change in the SSL Certificate column of the third listener.
9. Select Choose an existing SSL certificate and select the certificate that you previously uploaded for the second listener.
The image shows the completed listener information.
10. Click Save to complete the load balancer configuration.
Step 7: Configure the Cloud Controller
Note: There might be a brief delay before the certificate you uploaded for the second listener appears. If you
do not see the certificate you uploaded, try refreshing the page.
1. Select Cloud Controller and enter your system and application domains.
The System Domain defines your target when you push apps to Elastic Runtime. The Apps Domain defines where Elastic Runtime should serve your apps.
Pivotal recommends that you use the same domain name, but different subdomain names, for your system domain and your app domain. This allows you to use a single wildcard certificate for the domain while preventing apps from creating routes that overlap with system routes.
For example, name your system domain system.MYDOMAIN.COM and your apps domain apps.MYDOMAIN.COM.
2. Click Save.
Step 8: Configure Resources
Because you are using RDS, S3, and ELBs, you can turn off certain VMs that you do not need.
1. Click Resource Config and edit the following fields:
NFS Server: Enter 0 in Instances.
Cloud Controller Database: Enter 0 in Instances.
UAA Database: Enter 0 in Instances.
Console Database: Enter 0 in Instances.
HAProxy: Enter 0 in Instances.
MySQL Proxy: Enter 0 in Instances.
MySQL Server: Enter 0 in Instances.
2. On the same page:
Router: Enter the load balancer name in ELB Name that you created in the Prepare a Load Balancer and Wildcard DNS Record section of the Configuring AWS for PCF topic.
3. Click Save.
Step 7: Complete the Elastic Runtime Installation
1. Click the Installation Dashboard link to return to the Installation Dashboard.2. Click Apply Changes to begin your installation of Elastic Runtime.
The install process generally requires a minimum of 90 minutes to complete. The image shows the Changes
Applied window that displays when the installation process successfully completes.