Update an existing cluster
For the complete documentation index see: llms.txt
All documentation pages available in markdown.
PATCH /database/clusters/{clusterId}
Update an existing cluster.
Authorizations
Parameters
Path Parameters
A cluster ID.
Request Body required
Update cluster request
object
object
The bucket the logs reside in. On AWS this is an S3 bucket ARN; on GCP a Cloud Storage bucket reference (gs://bucket-name or projects/{project}/buckets/{bucket}).
A list of principals authorized to read the log bucket. On AWS these are IAM role ARNs or account IDs; on GCP they are IAM members (user:, serviceAccount:, group: or domain:). The principal must match the cloud provider the cluster runs on.
object
Cloud provider for the infrastructure
Instance type for vertical scaling. An EC2 instance type on AWS (i4i.large), a machine type on GCP (n2-standard-4).
Region where resources will be deployed. AWS regions are named us-east-1, GCP regions us-central1.
Number of availability zones (AWS) or zones (GCP) to spread resources across
Zones for aerospike nodes. Availability zone IDs on AWS (use1-az1), zone names on GCP (us-central1-a).
IPv4 CIDR block for the database VPC. GCP requires /16; AWS requires /19.
The network ID of the database. A VPC ID on AWS (vpc-01234567890123456), a network URL on GCP (projects/{project}/global/networks/{network}).
The account the database is deployed into. An AWS account ID when provider is aws, a GCP project ID when provider is gcp.
object
AWS General Purpose SSD (gp2)
Size of the EBS volume in gigabytes
object
AWS General Purpose SSD (gp3)
IOPS for gp3 (min 3000, max 16000). Max 500 IOPS per GB (not enforced by schema).
Size of the EBS volume in gigabytes
object
AWS Provisioned IOPS SSD (io1)
IOPS for io1 (min 100, max 64000). Max 50 IOPS per GB (not enforced by schema).
Size of the EBS volume in gigabytes (min 4 for io1)
object
AWS Provisioned IOPS SSD (io2)
IOPS for io2 (min 100, max 64000). Max 1000 IOPS per GB (not enforced by schema).
Size of the EBS volume in gigabytes (min 4 for io2)
object
GCP Standard Persistent Disk (pd-standard)
Size of the persistent disk in gigabytes (min 10)
object
GCP Balanced Persistent Disk (pd-balanced)
Size of the persistent disk in gigabytes (min 10)
object
GCP SSD Persistent Disk (pd-ssd)
Size of the persistent disk in gigabytes (min 10)
The private DNS zone for the database. A Route 53 hosted zone ID on AWS, a Cloud DNS managed zone name on GCP.
object
Number of nodes in the cluster (horizontal scaling)
Persist data using local disks or network storage. If omitted, data is stored in-memory without persistence.
object
Number of nodes in the cluster (horizontal scaling)
Persist data using network storage. If omitted, data is stored only on local SSDs without additional persistence.
object
Number of nodes in the cluster (horizontal scaling)
Aerospike server configuration
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
The address, port and TLS name of the node. The TLS name is optional.
object
Example
Example:Responses
202
A cluster creation, modification, or deletion request has been successfully processed and the current state of applying the requested change is returned.
Response Headers
ID uniquely identifying the request/response cycle.
Response Schema
object
Unique identifier for this resource within Aerospike Cloud
The infrastructure data plane version of the cluster.
The app data plane version of the cluster.
The addons data plane version of the cluster.
object
Host name that clients will use to connect to the cluster. Correlates to the AEROSPIKE_CLOUD_HOST
variable in documentation and code samples.
PEM encoded TLS certificate for the cluster.
object
The bucket the logs reside in. On AWS this is an S3 bucket ARN; on GCP a Cloud Storage bucket reference (gs://bucket-name or projects/{project}/buckets/{bucket}).
A list of principals authorized to read the log bucket. On AWS these are IAM role ARNs or account IDs; on GCP they are IAM members (user:, serviceAccount:, group: or domain:). The principal must match the cloud provider the cluster runs on.
object
Cloud provider for the infrastructure
Instance type for vertical scaling. An EC2 instance type on AWS (i4i.large), a machine type on GCP (n2-standard-4).
Region where resources will be deployed. AWS regions are named us-east-1, GCP regions us-central1.
Number of availability zones (AWS) or zones (GCP) to spread resources across
Zones for aerospike nodes. Availability zone IDs on AWS (use1-az1), zone names on GCP (us-central1-a).
IPv4 CIDR block for the database VPC. GCP requires /16; AWS requires /19.
The network ID of the database. A VPC ID on AWS (vpc-01234567890123456), a network URL on GCP (projects/{project}/global/networks/{network}).
The account the database is deployed into. An AWS account ID when provider is aws, a GCP project ID when provider is gcp.
object
AWS General Purpose SSD (gp2)
Size of the EBS volume in gigabytes
object
AWS General Purpose SSD (gp3)
IOPS for gp3 (min 3000, max 16000). Max 500 IOPS per GB (not enforced by schema).
Size of the EBS volume in gigabytes
object
AWS Provisioned IOPS SSD (io1)
IOPS for io1 (min 100, max 64000). Max 50 IOPS per GB (not enforced by schema).
Size of the EBS volume in gigabytes (min 4 for io1)
object
AWS Provisioned IOPS SSD (io2)
IOPS for io2 (min 100, max 64000). Max 1000 IOPS per GB (not enforced by schema).
Size of the EBS volume in gigabytes (min 4 for io2)
object
GCP Standard Persistent Disk (pd-standard)
Size of the persistent disk in gigabytes (min 10)
object
GCP Balanced Persistent Disk (pd-balanced)
Size of the persistent disk in gigabytes (min 10)
object
GCP SSD Persistent Disk (pd-ssd)
Size of the persistent disk in gigabytes (min 10)
The private DNS zone for the database. A Route 53 hosted zone ID on AWS, a Cloud DNS managed zone name on GCP.
object
Number of nodes in the cluster (horizontal scaling)
Persist data using local disks or network storage. If omitted, data is stored in-memory without persistence.
object
Number of nodes in the cluster (horizontal scaling)
Persist data using network storage. If omitted, data is stored only on local SSDs without additional persistence.
object
Number of nodes in the cluster (horizontal scaling)
Aerospike server configuration
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
object
The address, port and TLS name of the node. The TLS name is optional.
object
object
Example
{
"connectionDetails": {
"logging": {
"authorizedRoles": [
"infrastructure": {
"zoneIds": [
"aerospikeCloud": {
"aerospikeServer": {
"service": {
"feature-key-files": [
"logging": [
{
"network": {
"tls": [
{
"namespaces": [
{
"geo2dsphere-within": {
"sets": [
{
"storage-engine": {
"devices": [
"files": [
"mod-lua": {
"security": {
"ldap": {
"role-query-patterns": [
"log": {
"report-data-op": [
"report-data-op-role": [
"report-data-op-user": [
"xdr": {
"dcs": [
{
"node-address-ports": [
"namespaces": [
{
"ignore-bins": [
"ignore-sets": [
"ship-bins": [
"ship-sets": [
"health": {
400
Invalid input
Response Headers
ID uniquely identifying the request/response cycle.
Response Schema
RFC 9457 Problem Details for HTTP APIs. Provides a standardized format for conveying error details in HTTP responses.
object
URN-based error type identifiers following the pattern: urn:aerospike:errors:{category}:{specific}
Resource information (cluster, database, organization, etc.) is provided in the ProblemDetails context field, not in the URN.
A short, human-readable summary of the problem type
The HTTP status code
A human-readable explanation specific to this occurrence
A URI reference that identifies the specific occurrence
Context for resource-related errors (not-found, already-exists)
object
Type of resource (e.g., cluster, database, organization)
Identifier of the resource
Structured context for validation errors
object
JSON Pointer paths to missing required fields
Details about invalid field values
object
JSON Pointer path to the invalid field
URN identifying the specific validation error type
An optional human-readable description of the validation error
object
Developer-friendly message explaining the error. Deprecated: Use ‘detail’ field instead.
Example
Example:401
Access token is missing or invalid
Response Headers
ID uniquely identifying the request/response cycle.
Response Schema
RFC 9457 Problem Details for HTTP APIs. Provides a standardized format for conveying error details in HTTP responses.
object
URN-based error type identifiers following the pattern: urn:aerospike:errors:{category}:{specific}
Resource information (cluster, database, organization, etc.) is provided in the ProblemDetails context field, not in the URN.
A short, human-readable summary of the problem type
The HTTP status code
A human-readable explanation specific to this occurrence
A URI reference that identifies the specific occurrence
Context for resource-related errors (not-found, already-exists)
object
Type of resource (e.g., cluster, database, organization)
Identifier of the resource
Structured context for validation errors
object
JSON Pointer paths to missing required fields
Details about invalid field values
object
JSON Pointer path to the invalid field
URN identifying the specific validation error type
An optional human-readable description of the validation error
object
Developer-friendly message explaining the error. Deprecated: Use ‘detail’ field instead.
Example
Example:403
Permission denied
Response Headers
ID uniquely identifying the request/response cycle.
Response Schema
RFC 9457 Problem Details for HTTP APIs. Provides a standardized format for conveying error details in HTTP responses.
object
URN-based error type identifiers following the pattern: urn:aerospike:errors:{category}:{specific}
Resource information (cluster, database, organization, etc.) is provided in the ProblemDetails context field, not in the URN.
A short, human-readable summary of the problem type
The HTTP status code
A human-readable explanation specific to this occurrence
A URI reference that identifies the specific occurrence
Context for resource-related errors (not-found, already-exists)
object
Type of resource (e.g., cluster, database, organization)
Identifier of the resource
Structured context for validation errors
object
JSON Pointer paths to missing required fields
Details about invalid field values
object
JSON Pointer path to the invalid field
URN identifying the specific validation error type
An optional human-readable description of the validation error
object
Developer-friendly message explaining the error. Deprecated: Use ‘detail’ field instead.
Example
Example:404
Resource not found
Response Headers
ID uniquely identifying the request/response cycle.
Response Schema
RFC 9457 Problem Details for HTTP APIs. Provides a standardized format for conveying error details in HTTP responses.
object
URN-based error type identifiers following the pattern: urn:aerospike:errors:{category}:{specific}
Resource information (cluster, database, organization, etc.) is provided in the ProblemDetails context field, not in the URN.
A short, human-readable summary of the problem type
The HTTP status code
A human-readable explanation specific to this occurrence
A URI reference that identifies the specific occurrence
Context for resource-related errors (not-found, already-exists)
object
Type of resource (e.g., cluster, database, organization)
Identifier of the resource
Structured context for validation errors
object
JSON Pointer paths to missing required fields
Details about invalid field values
object
JSON Pointer path to the invalid field
URN identifying the specific validation error type
An optional human-readable description of the validation error
object
Developer-friendly message explaining the error. Deprecated: Use ‘detail’ field instead.
Example
Example:409
Conflict error
Response Headers
ID uniquely identifying the request/response cycle.
Response Schema
RFC 9457 Problem Details for HTTP APIs. Provides a standardized format for conveying error details in HTTP responses.
object
URN-based error type identifiers following the pattern: urn:aerospike:errors:{category}:{specific}
Resource information (cluster, database, organization, etc.) is provided in the ProblemDetails context field, not in the URN.
A short, human-readable summary of the problem type
The HTTP status code
A human-readable explanation specific to this occurrence
A URI reference that identifies the specific occurrence
Context for resource-related errors (not-found, already-exists)
object
Type of resource (e.g., cluster, database, organization)
Identifier of the resource
Structured context for validation errors
object
JSON Pointer paths to missing required fields
Details about invalid field values
object
JSON Pointer path to the invalid field
URN identifying the specific validation error type
An optional human-readable description of the validation error
object
Developer-friendly message explaining the error. Deprecated: Use ‘detail’ field instead.
Example
Example:500
Internal Server Error
Response Headers
ID uniquely identifying the request/response cycle.
Response Schema
RFC 9457 Problem Details for HTTP APIs. Provides a standardized format for conveying error details in HTTP responses.
object
URN-based error type identifiers following the pattern: urn:aerospike:errors:{category}:{specific}
Resource information (cluster, database, organization, etc.) is provided in the ProblemDetails context field, not in the URN.
A short, human-readable summary of the problem type
The HTTP status code
A human-readable explanation specific to this occurrence
A URI reference that identifies the specific occurrence
Context for resource-related errors (not-found, already-exists)
object
Type of resource (e.g., cluster, database, organization)
Identifier of the resource
Structured context for validation errors
object
JSON Pointer paths to missing required fields
Details about invalid field values
object
JSON Pointer path to the invalid field
URN identifying the specific validation error type
An optional human-readable description of the validation error
object
Developer-friendly message explaining the error. Deprecated: Use ‘detail’ field instead.