---
title: "Aerospike Cloud limitations"
description: "Known limitations, cluster configuration rules, and workarounds for Aerospike Cloud deployments on AWS."
---

# Aerospike Cloud limitations

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

This page describes the limitations in Aerospike Cloud. Limitations are organized by category and include workarounds where available.

## Known limitations

### Features in development

-   **Limited regions and instance types**: May not have optimal placement
    -   **Workaround**: Request additional regions via support
    -   **Status**: Ongoing expansion

### Architecture constraints

-   **Bring your own account (BYOA) is not available**: Aerospike-managed AWS accounts only
    -   **Workaround**: Use VPC peering for connectivity to your infrastructure
-   **Single cloud provider**: AWS only
    -   **Timeline**: Multi-cloud support planned for 2026

## Cluster configuration limits

The following limits are enforced to ensure stability and optimal performance:

### Sizing constraints

| Rule | Reason | Example |
| --- | --- | --- |
| **Cluster size ÷ zone count = whole number** | Even distribution across zones | 6 nodes ÷ 3 zones = 2 nodes/zone ✅ |
| **Cluster size ÷ replication factor = whole number** | Balanced replication | 9 nodes ÷ 3 replicas = 3 sets ✅ |
| **Max 15 nodes default** | Resource management | Contact support for higher limits |

### Namespace constraints

-   **Single namespace per cluster** - Each Aerospike Cloud cluster supports only one namespace. To isolate workloads or data, use [sets](https://aerospike.com/docs/database/manage/namespace/sets/) or provision separate clusters for complete isolation.
-   **Set indexes (Database 8.1.2+)** - You can create and delete [set indexes](https://aerospike.com/docs/database/learn/architecture/data-storage/set-index) using the **sindex-admin** privilege with [`sindex-create`](https://aerospike.com/docs/database/reference/info/#sindex-create) and [`sindex-delete`](https://aerospike.com/docs/database/reference/info/#sindex-delete). The `sys-admin` role is not required. See [Managing set indexes](https://aerospike.com/docs/database/manage/namespace/sets#managing-set-indexes).

### Immutable settings

After their initial configuration, the following settings cannot be changed:

-   **Replication factor** - Plan carefully for your durability needs
-   **Zone count** - Consider growth when selecting zones
-   **Strong consistency + Memory storage** - Choose one consistency model
-   **Not all Aerospike server settings are available through the cloud** - See [advanced config](https://aerospike.com/docs/cloud/manage/advanced-config) for more information

::: tip
-   **For high availability**: Use replication factor ≥ 2
-   **For strong consistency**: Use disk storage mode
-   **For growth**: Plan zone distribution for future scaling
:::

## Getting Help

### When you hit a limit

1.  **Check workarounds** in the tables above
2.  **Review [best practices](https://aerospike.com/docs/cloud/manage)** for optimal configurations
3.  **Contact support** for limit increases or timeline questions
4.  **Join community** for peer discussions and updates

### Support escalation

-   **Technical limits**: Contact your technical account manager
-   **Billing limits**: Discuss with your sales engineer
-   **Timeline questions**: We plan to publish a public roadmap for 2026 features

## Related topics

-   [Cluster planning best practices](https://aerospike.com/docs/cloud/manage/create)
-   [API usage patterns](https://aerospike.com/docs/cloud/manage-apis/cloud-api-use)
-   [Monitoring and alerting](https://aerospike.com/docs/cloud/observe/metrics)