A Valkey Replication deployment — one primary, one replica and one Sentinel — plus the shared Parameter Set that owns its tuning. Needs a provider that ships kvindo_valkey_replication (v5.6.0 or newer); an older provider answers Invalid resource type. Assumes the Networking example's resources are in the same configuration.

The final output block surfaces status.connection_uri so you can see how a client would actually reach the deployment.

Note what is absent from spec: no maxmemory_*, io_threads, appendfsync or AOF fields. Those belong to the shared parameter set, which is why parameters_set_id is the only tuning knob here. volume_size_gib has a floor of 20 — the boot volume holds the OS, the data and a fork/COW copy during BGSAVE. Every node, Sentinels included, shares one subnet.

Related pages

Resource docs

• Valkey Replication resource docs
• Parameter Set resource docs
• Valkey User resource docs
• VPC Subnet resource docs

More in this section

• IAM
• Networking
• VMs
• VPN
• Load Balancing
• Kubernetes
• S3
• Valkey
• PostgreSQL
• Kafka
• ClickHouse
• OpenSearch
• GitLab
• Examples

Reference

• Kvindo provider on the Terraform Registry