Alibaba CloudStatic-verified

Alibaba Cloud ACK Cluster

Managed ACK Kubernetes with node pools, VPC integration, and RAM roles.

terraformAlt & Specialty Cloudsalicloud

Compare Managed Kubernetes across clouds →

alicloud-ack-clustervizier v1.2.0

Verification

Static-verified

Passed: validated and lint-clean (provider-schema-validated for AWS/Azure/GCP; Terraform-language lint elsewhere).

Conformance

  • Static validation (fmt · validate · tflint)
  • No applicable security policies for this provider
  • Plan tests (mocked: validation rules · outputs)

Provenance

Functional

  • Live test pending (no cloud run yet)

Last verified 2026-06-28 · how we verify

Verify this download

cosign · sha-256

Don't take our word for it. Every release is signed with cosign - check the bytes against our pinned public key before you trust them.

# 1. Our pinned public key - fetch once, trust out-of-band
curl -O https://www.iac-bazaar.com/cosign.pub

# 2. This module's Sigstore bundle
curl -o alicloud-ack-cluster-1.0.0.sigstore.json \
  https://www.iac-bazaar.com/api/artifacts/alicloud-ack-cluster/signature

# 3. Verify the tarball you downloaded
cosign verify-blob \
  --key cosign.pub \
  --bundle alicloud-ack-cluster-1.0.0.sigstore.json \
  alicloud-ack-cluster-1.0.0.tar.gz
# → Verified OK

# 4. (optional) confirm the checksum too
echo "f57521239690dabe55283c5a56d142504955bfd092569a8c57cbaf9dd69d08cf  alicloud-ack-cluster-1.0.0.tar.gz" | sha256sum -c

Use it from the registry

terraform · opentofu
module "ack_cluster" {
  source  = "www.iac-bazaar.com/iac-bazaar/alicloud-ack-cluster/alicloud"
  version = "1.0.0"
}

Needs a registry token from /account/tokens. The module itself is free; the account is what identifies you. Full setup: registry docs.

Cite it in your README

badge · attribution

Paste this beside the module in the repository that uses it. The badge is rendered from this artifact's verification record, so it reads static-verified because the record says so, and the link lands on this page.

README.md, GitLab, Gitea
[![IaC Bazaar: static-verified](https://www.iac-bazaar.com/api/artifacts/alicloud-ack-cluster/badge)](https://www.iac-bazaar.com/catalog/alicloud-ack-cluster?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)

Terraform module 1.0.0, static-verified on IaC Bazaar: [Alibaba Cloud ACK Cluster](https://www.iac-bazaar.com/catalog/alicloud-ack-cluster?utm_source=syndication&utm_medium=readme&utm_campaign=artifact)

```hcl
module "ack_cluster" {
  source  = "www.iac-bazaar.com/iac-bazaar/alicloud-ack-cluster/alicloud"
  version = "1.0.0"
}
```

Preview:IaC Bazaar: static-verified

Inputs & outputs

Create a free account to read this module's contract

The declared contract - every input name, type, default and description, plus every output - is shown to signed-in accounts, not to anonymous visitors.

A free account sees the contract of every module in the catalogue. There is no subscription and nothing to buy - the modules are free to download, and they run under Vizier.

Documentation

alicloud-ack-cluster

A production-ready Alibaba Cloud ACK managed Kubernetes cluster (Pro tier) wired into an existing VPC, with autoscaling worker node pools. Designed to sit on top of a network foundation such as alicloud-vpc-foundation: you bring the private vSwitches, this module brings a hardened cluster.

Status: static-validated, live-test pending. Validated with tofu validate + tflint + checkov against the aliyun/alicloud provider. Not yet applied against a live Alibaba Cloud account (no sandbox subscription, and ACK clusters take ~15 min to create and bill a per-cluster fee), so it ships under live-test quarantine.

Design & secure defaults

  • Private API server. slb_internet_enabled = false by default — the Kubernetes API server is reachable only from inside the VPC (use a bastion, VPN, or Cloud Enterprise Network). Opt into a public endpoint explicitly.
  • Pod-scoped RAM identity (RRSA). enable_rrsa = true turns on RAM Roles for Service Accounts: pods assume narrowly-scoped RAM roles via OIDC instead of sharing the node's instance role — least privilege for workloads. (Pro only.)
  • Deletion protection on. Accidental cluster deletion is blocked; a Terraform destroy requires flipping deletion_protection = false first.
  • Secrets envelope encryption. Pass encryption_provider_key (a KMS key id) to encrypt Kubernetes Secrets at rest in etcd. (Pro only.)
  • Advanced security group (is_enterprise_security_group = true), the recommended type with a higher rule ceiling.
  • Encrypted worker disks. Node-pool system disks default to encrypted cloud_essd (PL1); supply system_disk_kms_key for a customer-managed key.
  • Control-plane audit logging. apiserver/kcm/scheduler/ccm logs ship to Log Service (SLS) with a 30-day retention by default.
  • Managed node pools. Auto-repair and auto-upgrade are on so unhealthy nodes self-heal and patch upgrades roll out within the maintenance window.
  • No NAT by default. new_nat_gateway = false — reuse the egress your VPC foundation already provides instead of spawning a second NAT gateway/EIP.

Cross-field invariants (Terway needs pod vSwitches; RRSA and Secrets encryption need a Pro cluster; autoscaling needs min_size <= max_size) are enforced with precondition blocks, so misconfigurations fail at plan time, not mid-apply.

Provider

aliyun/alicloud >= 1.241.0, < 2.0 (floor raised so the non-deprecated vswitch_ids argument is available). Requires Terraform/OpenTofu >= 1.6.

License

Commercial — LicenseRef-IaCBazaar-Commercial. See the IaC Bazaar terms.

Usage code & full reference need an account

The complete copy-paste usage, the full input/output reference, and operational notes are free with an account - shown here and bundled in the download. Sign in and this section fills in.

  • Usage
  • Key inputs
  • Outputs

Related modules