# \[RELEASE\] ScyllaDB Cloud Terraform Provider 1.10.2

**URL:** <https://forum.scylladb.com/t/release-scylladb-cloud-terraform-provider-1-10-2/5334>\
**Category:** Release Notes\
**Tags:** cloud, cloud-release, terraform\
**Created:** [March 30, 2026, 4:14pm UTC](https://forum.scylladb.com/t/release-scylladb-cloud-terraform-provider-1-10-2/5334 "2026-03-30T16:14:02Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Buff](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.scylladb.com/buff/32/1948_2.png) [@Buff](https://forum.scylladb.com/u/Buff)\
**Post date:** [March 30, 2026, 4:14pm UTC](https://forum.scylladb.com/t/release-scylladb-cloud-terraform-provider-1-10-2/5334/1 "2026-03-30T16:14:02Z")

</div>

![ScyllaDB](https://us1.discourse-cdn.com/flex016/uploads/scylladb/original/2X/1/17b4911a4f5dfff075e6bfef7250fc0ba11cfe06.png)

Hello,

The ScyllaDB team is pleased to announce the new version of our ScyllaDB Cloud Terraform provider 1.10.2.  
Highlights of the release:

### Ability to scale standard clusters

We switched from expressing the exact node count (`node_count`) to expressing the minimum number of nodes (`min_nodes`). This better reflects reality because the Cloud automatically scales out clusters when the storage threshold is reached.

To scale out the cluster, simply increase `min_nodes`. Scale-out occurs immediately when `terraform apply` is called and is blocked until it succeeds. To scale it down, reduce `min_nodes`. The behaviour is the same as for the scale-out. Changing `min_nodes` won’t force cluster recreation.

Note that **this is a breaking change**! To upgrade to v1.10, you must update your Terraform configuration by renaming `node_count` to `min_nodes`.

### Availability zones

In v1.10, you can express the desired availability zone IDs in the cluster configuration using the `availability_zone_ids` field. This field is optional and computed. After upgrading the ScyllaDB Terraform Provider and refreshing the state with `terraform refresh`, you can output the AZ IDs where the nodes are provisioned.

You should provide 3 separate availability zones by their IDs.

### Example

Create a three-node cluster using specific AZ IDs.

```hcl
resource "scylladbcloud_cluster" "test" {
    name = "test-aws"
    cloud = "AWS"
    region = "us-east-1"
    node_type = "i3.large"
    min_nodes = 3 # <-- three-node cluster
    cidr_block = "10.0.1.0/24"
    availability_zone_ids = ["use1-az1", "use1-az4", "use1-az5"] # <-- exact AZ IDs
}

```

To scale out, simply update `min_nodes = 6`.

The documentation is available at the [Terraform Registry for ScyllaDB](https://registry.terraform.io/providers/scylladb/scylladbcloud/latest/docs)