---
title: Resize deployment
description: Elasticsearch scales to whatever capacity you need and with as many nodes as the available resources can support. If you don’t have enough available resources,...
url: https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise/resize-deployment
products:
  - Elastic Cloud Enterprise
applies_to:
  - Elastic Cloud Enterprise: Generally available
---

# Resize deployment
Elasticsearch scales to whatever capacity you need and with as many nodes as the available resources can support. If you don’t have enough available resources, [add some capacity first](https://www.elastic.co/docs/deploy-manage/maintenance/ece/scale-out-installation).
<tip>
  You can also enable autoscaling on a deployment to have the available resources for components, such as [data tiers](https://www.elastic.co/docs/manage-data/lifecycle/data-tiers) and [machine learning](https://www.elastic.co/docs/explore-analyze/machine-learning) nodes, adjust automatically as the demands on the deployment change over time. Check [Deployment autoscaling](https://www.elastic.co/docs/deploy-manage/autoscaling/autoscaling-in-ece-and-ech) to learn more.
</tip>

To resize a deployment:
1. [Log into the Cloud UI](https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui).
2. On the **Deployments** page, select your deployment.
   Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
3. From your deployment menu, go to the **Edit** page.
4. Change the deployment configuration, keeping the following considerations in mind:
   <definitions>
   <definition term="Fault tolerance">
   If the initial deployment you created uses only one availability zone, it is not fault tolerant. On a production system, enable [high availability](https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise/ece-ha) by changing your deployment to use at least two availability zones, three for mission-critical deployments. The number of instances comes from the number of zones and the type of [template](https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise/deployment-templates). Having more nodes or instances lets you scale out horizontally by adding more processing capacity to your deployment.
   <warning>
   Deployments that use only one availability zone are not highly available and are at risk of data loss, if you do not [configure an external snapshot repository](https://www.elastic.co/docs/deploy-manage/tools/snapshot-and-restore/cloud-enterprise) to enable regular backups. To safeguard against data loss, you must use at least two data centers and configure an external repository for backups.
   </warning>
   </definition>
   </definitions>
   <definitions>
   <definition term="RAM per instance">
   Node and instance capacity should be sufficient to sustain your search workload, even if you lose an availability zone. For instances up to 64 GB of RAM, half the memory is assigned to the JVM heap. For instances larger than 64 GB, the heap size is capped at 32 GB. For example, on an Elasticsearch cluster node with 32 GB RAM, 16 GB would be allotted to heap, while on a 128 GB node, 32 GB would be allotted to heap. Up to 256 GB RAM and 1 TB storage per node are supported.
   </definition>
   </definitions>
   Before finalizing your changes, you can review the **Architecture** summary, which shows the total number of instances per zone, with each circle color representing a different type of instance.
5. Select **Save changes**.


## Example: From very small to very large

This example shows you how to change an existing, very basic deployment to use high availability and to add capacity.
To scale your deployment from very small to very large:
1. [Log into the Cloud UI](https://www.elastic.co/docs/deploy-manage/deploy/cloud-enterprise/log-into-cloud-ui).
2. On the **Deployments** page, select your deployment.
   Narrow the list by name, ID, or choose from several other filters. To further define the list, use a combination of filters.
3. From your deployment menu, go to the **Edit** page.
4. Under **Fault tolerance**, select **3 zones** for mission critical environments*.
5. Under **RAM per instance**, select **64 GB memory / 2 TB storage**.
6. Select **Save changes**.

There is no downtime when adding high availability. Deployments with high availability will continue to handle user requests, even if the configuration changes are applied.