---
title: "Modify an Aerospike Cloud database cluster"
description: "Learn how to scale, configure, and decommission an Aerospike Cloud database cluster via the Console or APIs."
---

# Modify an Aerospike Cloud database cluster

> For the complete documentation index see: [llms.txt](https://aerospike.com/docs/llms.txt)
> 
> All documentation pages available in markdown.

You can change a database cluster after it has been provisioned using any of the following operations in the Cloud Console or using the APIs.

-   [Scale the database cluster](#scale-a-database-cluster) – change the number of nodes in the cluster or modify the instance type of the nodes.
-   [Modify the database cluster configuration](#modify-the-database-cluster-configuration) – use the [advanced configuration](https://aerospike.com/docs/cloud/manage/advanced-config) page to tune performance or modify the behavior of your database cluster.
-   [Decommission the database cluster](#decommission-the-database-cluster) – delete the cluster and the AWS resources it is consuming.

### Scale a database cluster

-   [Console](#tab-panel-2092)
-   [API](#tab-panel-2093)

1.  Navigate to the database clusters page.
    
    Click **Scale cluster** (crossed arrows icon) to open a page where you can change the instance type and node count of the database cluster.
    
2.  Set your new cluster size. The size can only be changed in increments that balance evenly across the number of zones in the cluster.
    
3.  Review and submit the change
    
    Finalize your selections and submit the modification. Scaling operations take time to implement and are done sequentially. It may take some time before your cluster matches the state you have requested. The Console will show the desired state and a status of `Updating` to reflect that a change is being made to reach the state you have requested.
    
    ::: caution
    Submitting more than one scaling request at a time is strongly discouraged as it may cause thrashing on your cluster.
    :::
    

1.  Create a Cloud API Key and retrieve a bearer token
    
    See [Use Cloud APIs](https://aerospike.com/docs/cloud/manage-apis/cloud-api-use) to learn about creating a key to use with the API.
    
2.  Make a PATCH request with the desired database spec.
    
    The following example is a general command to modify your cluster:
    
    Terminal window
    
    ```bash
    curl -X PATCH "https://api.aerospike.com/v1/database/clusters/<CLUSTER_ID>" \
    
        -H "Authorization: Bearer <BEARER_TOKEN>" \
    
        -H "Content-Type: application/merge-patch+json" \
    
        --data '{"aerospikeCloud":{"clusterSize":4}}'
    ```
    

### Modify the database cluster configuration

-   [Console](#tab-panel-2094)
-   [API](#tab-panel-2095)

1.  Navigate to the clusters page.
    
    Click **Edit server config** (pencil icon) to open the advanced configuration page.
    
2.  Enter new advanced configuration options.
    
    See [advanced configuration](https://aerospike.com/docs/cloud/manage/advanced-config) for information about what you can change. Some operations are risky, and combining different operations can severely degrade or halt your cluster. Be careful when making changes that are not recommended.
    
3.  Review and submit the change.
    
    Finalize your selections and submit the modification. It may take some time before your cluster matches the state you have requested. The Console will show the desired state and a status of `Updating` to reflect that a change is being made to reach the state you have requested.
    
    ::: caution
    For some advanced configuration changes, the database cluster may be in a temporary state between updating and active, and you may need to intervene. In most cases, if you have made a healthy configuration change, this state resolves itself after a few minutes.
    :::
    

1.  Create a Cloud API Key and retrieve a bearer token.
    
    See [Use Cloud APIs](https://aerospike.com/docs/cloud/manage-apis/cloud-api-use) to learn about creating a key to use with the API.
    
2.  Make a PATCH request with the desired database spec.
    
    The following example is a general command to patch your cluster:
    
    Terminal window
    
    ```bash
    curl -X PATCH "https://api.aerospike.com/v1/database/clusters/<CLUSTER_ID>" \
    
        -H "Authorization: Bearer <BEARER_TOKEN>" \
    
        -H "Content-Type: application/merge-patch+json" \
    
        --data '{"aerospikeServer":{"namespaces":[{"name":"<NAMESPACE_NAME>","default-ttl":30,"nsup-period":60}]}}'
    ```
    
    Replace `<NAMESPACE_NAME>` with the name of the namespace you specified when provisioning the cluster. Aerospike Cloud supports a single namespace per cluster, and the namespace name is fixed at provisioning time.
    

### Decommission the database cluster

-   [Console](#tab-panel-2096)
-   [API](#tab-panel-2097)

1.  Navigate to the database clusters page.
    
    Click **Decommission cluster** (trash can icon). The cluster name disappears immediately from the list of active clusters. To retrieve metadata about a decommissioned database cluster, use the toggle to display decommissioned clusters.
    

1.  Create a Cloud API Key and retrieve a bearer token.
    
    See [Use Cloud APIs](https://aerospike.com/docs/cloud/manage-apis/cloud-api-use) to learn about creating a key to use with the API.
    
2.  Make a DELETE request with the desired database cluster ID. For example:
    
    Terminal window
    
    ```bash
    curl -X DELETE "https://api.aerospike.com/v1/database/clusters/<CLUSTER_ID>" \
    
        -H "Authorization: Bearer <BEARER_TOKEN>"
    ```