pcf-aws-manual-er-config.html.md.erb

---
title: Configuring Elastic Runtime for AWS
owner: Ops Manager
---
<% $this_IaaS = 'AWS' %>

This topic describes how to configure the Pivotal Elastic Runtime components
that you need to run <a
href="https://network.pivotal.io/products/pivotal-cf">Pivotal Cloud Foundry</a>
(PCF) on Amazon Web Services (AWS).

***<p class="tip">CAUTION: Pivotal strongly recommends installing Pivotal Cloud Foundry using AWS CloudFormation, as described in [Installing Pivotal Cloud Foundry&reg; on AWS](./cloudform.html), rather than configuring AWS manually as documented here.</p>***

## <a id='prerequisites'></a>Prerequisites ##

Before following this procedure, complete all of the steps in the [Configuring Ops Manager Director for AWS](./pcf-aws-manual-om-config.html) topics.

## <a id='om-add'></a>Step 1: Add Elastic Runtime to Ops Manager ##

1. Navigate to the Pivotal Cloud Foundry Operations Manager Installation
Dashboard.

1. 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](./add-delete.html) topic.

1. Click the Elastic Runtime tile in the Installation Dashboard.

    <%= image_tag("pcfaws/er_14_tile.png") %>

## <a id='az-networks'></a>Step 2: Assign Networks and Availability Zones ##

1. Select **Assign Network**.

1. Select the network that you created in the [Networks
Pages](./pcf-aws-manual-om-config.html#pcfaws-om-networks) section of the _Configuring
Ops Manager Director for AWS_ topic, and click **Save**.

    <p class="note"><strong>Note</strong>: When you save this form, a
	verification error displays because the PCF security group blocks ICMP. You
	can ignore this error.</p>

	<%= image_tag("pcfaws/er-network-error.png") %>

1. Select **Assign Availability Zones**.

1. Select the option button and checkbox to define the availability zone for
singleton jobs and job balancing.

1. Click **Save**.

    <%= image_tag("pcfaws/pcf_er_assign_az.png") %>

## <a id='db-config'></a>Step 3: Configure System Databases ##

Select **System Database Config**.

If you want to use PCF internal databases, select **Internal** and click **Save**.

If you want to use the external RDS instance for your Elastic Runtime databases, complete the following procedure.

First, create the databases that Elastic Runtime requires. The following instructions describe how to create those databases on your RDS instances. If you require help to create the RDS instances, contact [Pivotal Support](http://support.pivotal.io)

1. Add your key pair to your ssh profile so that you can access the machine:

	`ssh-add pcf.pem`

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

1. Log in to your RDS instance through the MySQL client, using the hostname from
the RDS console and the username that 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`

1. Create databases for each of the six Cloud Foundry components that require a database.
Run `CREATE database DB-NAME` for each of the following: `uaa`, `ccdb`,
`console`, `notifications`, `autoscale`, `app_usage_service`

1. You have now created the databases on the RDS instance.
Exit the mysql client and close your connection to the Ops Manager VM.

1. Navigate to the **System Database Config** page of the Elastic Runtime product tile.

1. Select **External Databases**.

1. Enter the RDS hostname, port (`3306`), username, and password.

1. Click **Save**.

    <%= image_tag("pcfaws/pcf_aws_er_db_config.png") %>

1. <%= partial 'mysql_proxy_config' %>

## <a id='file-store-config'></a>Step 4: Configure File Storage ##

Select **File Storage Config**.

To use the PCF internal filestore, select **Internal** and click **Save**.

To use an external S3-compatible filestore for your Elastic
Runtime file storage, complete the following procedure:

1. Select **External S3-Compatible Filestore**.

1. Enter the **URL Endpoint** for your filestore. If you manually configured Amazon Web Services for PCF, this is the value that you entered into the Director config page in [Configuring Ops Manager Director for AWS](./pcf-aws-manual-om-config.html#pcfaws-om-dirconfig#pcfaws-om-dirconfig).

1. Enter the **Bucket Name**. If you manually configured Amazon Web Services for PCF, this is the name that you chose.

1. Enter your **Access Key** and **Secret Key**. If you are using Amazon Web Services, retrieve your key information with the IAM credentials that you generated.

1. Click **Save**.

    <%= image_tag("pcfaws/external_filestore_url_endpoint.png") %>

## <a id='config-loggregator-port'></a>Step 5: Configure the Loggregator Port ##

1. Select **IPs and Ports**.

1. Leave the **Router IPs** and **HAProxy IPs** fields blank.

1. Set **Loggregator Port** to **4443**.

## <a id='security-config'></a>Step 6: Complete Security Configuration ##

<%= partial 'security_config' %>


## <a id='lb'></a>Step 7: Finalize the Load Balancer Setup ##

<%= partial 'configure_aws_elb' %>

## <a id='clocon'></a>Step 8: Configure the Cloud Controller ##

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.
    Doing so 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`.

1. Click **Save**.

    <%= image_tag("pcfaws/er_clocon.png") %>

## <a id='diego'></a>Step 9: Configure Diego ##

<%= partial 'diego_config' %>

## <a id='smtp'></a>Step 10: (Optional) Configure SMTP ##

Elastic Runtime uses SMTP to send invitations and confirmations to Apps Manager
users.
You must complete the Configuration for SMTP page if you want to enable end-user
self-registration and the [Notifications with UI](#notifications)
feature.

<p class="note"><strong>Note</strong>: If you do not configure the SMTP settings using this form, the administrator must create orgs and users using the cf CLI tool. See <a href="../adminguide/cli-user-management.html">Creating and Managing Users with the cf CLI</a> for more information.</p>

1. Select **SMTP Config**.

1. Enter your reply-to and SMTP email information

1. Verify your authentication requirements with your email administrator and use
the **SMTP Authentication Mechanism** drop-down menu to select `None`, `Plain`,
or `CRAMMD5`.
If you have no SMTP authentication requirements, select `None`.

1. Click **Save**.

    <%= image_tag("smtp.png") %>

## <a id='experimental'></a>Step 11: (Optional) Enable Experimental Features

<%= partial 'experimental-features' %>

## <a id='errands'></a>Step 12: Configure Errands ##

<%= partial 'errands' %>

## <a id='disable-resources'></a>Step 13: (Optional) Disable Unused Resources ##

<%= partial 'disable_resources' %>

## <a id='config-elb'></a>Step 14: Configure Router to Elastic Load Balancer ##

<%= partial 'resource_config_elb' %>

## <a id='complete'></a>Step 15: Complete the Elastic Runtime Installation ##

1. Click the **Installation Dashboard** link to return to the Installation
Dashboard.

1. Click **Apply Changes** to begin your installation of Elastic Runtime.
<br /><br />
    If an ICMP error message appears, click **Ignore errors and start the
	install**.

	<%= image_tag("pcfaws/er-install-error.png") %>

    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.

    <%= image_tag("aws/vpc-step16.png") %>

[Return to the Installing PCF Guide](../installing/index.html)