Aerospike Cloud limitations

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

Known limitations

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

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

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

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

Single namespace per cluster - Each Aerospike Cloud cluster supports only one namespace. To isolate workloads or data, use sets or provision separate clusters for complete isolation.

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 for more information