Aeon Scale Cluster
A 3-step recipe with YugabyteDB. We can help you get access.
Recipe · 3 steps
Aeon Scale Cluster
with YugabyteDB
Apply an updated cluster specification and wait for the cluster to settle.
- Read the current cluster to capture its existing state before applying the scaling change.
- Submit the updated cluster specification to scale node count, disk size, or fault tolerance. The cluster transitions into the UPDATING state.
- Poll the cluster until the update completes and it returns to the ACTIVE state. The cluster passes through UPDATING before settling.
What you'll need to have ready
- accountId: The unique identifier of the YugabyteDB Aeon account.
- projectId: The unique identifier of the project within the account.
- clusterId: The unique identifier of the cluster to scale.
- name: The cluster name (carried through in the updated spec).
- cloudInfo: Cloud provider and region placement (code and region).
- clusterInfo: The updated node count, fault tolerance, tier, sizing, and version.
For your developer
Arazzo workflow yugabytedb:scale-cluster, 3 operations: getCluster → updateCluster → getCluster. Specs on APIs.io.