_disable_resources.html.md.erb

By default, Elastic Runtime uses an internal filestore and internal databases.
If you configure Elastic Runtime to use external resources, you can disable the
corresponding system-provided resources in Ops Manager to reduce costs and
administrative overhead.

For more information regarding scaling instances, see the [Zero Downtime Deployment and Scaling in CF](http://docs.pivotal.io/pivotalcf/concepts/high-availability.html) and the [Scaling Instances in Elastic Runtime](./../opsguide/scaling-ert-components.html) topics.

Complete the following procedures to disable specific VMs in Ops Manager:

1. Click **Resource Config**.

1. If you configure Elastic Runtime to use an external S3-compatible filestore,
edit the following fields:
    * **NFS Server**: Enter `0` in **Instances**.

1. If you configure Elastic Runtime to use an external Relational Database
Service (RDS), edit the following fields:
    * **MySQL Proxy**: Enter `0` in **Instances**.
    * **MySQL Server**: Enter `0` in **Instances**.
    * **Cloud Controller Database**: Enter `0` in **Instances**.
    * **UAA Database**: Enter `0` in **Instances**.
    * **Apps Manager Database**: Enter `0` in **Instances**.

1. If you are using an External Load Balancer instead of HAProxy, enter 0 in the **Instances** field for **HAProxy**.

1. Click **Save**.