A Control Policy and the Attachments Without Which It Constrains Nobody

A Resource Management control policy and the folders or accounts it attaches to, which are separate resources: an unattached policy appears in the console list with a name and a document and constrains nobody. A control policy is a ceiling, so the module counts Deny statements and asks about Allow ones, which grant nothing. Attaching to the root reaches the management account.

This is the operations reference: version drift, dependants and neighbours. For what the module provisions, its inputs and outputs, and how to buy it, see the catalogue entry.

terraformAlibaba CloudLanding Zones & Foundationsv1.0.0static-validated

Provider drift

This artifact declares no Terraform provider requirements, so there is nothing to drift. Provider freshness applies to Terraform and OpenTofu modules.

What depends on this

No reference architecture names this module, so changing it affects only configurations that reference it directly.

Nearest alternatives

Same cloud, same category. These are what you would weigh against it without changing provider.

A Resource Directory Where Policy Can Attach and Accounts Can Be Deleted

The same job on other clouds

Organisation Guardrails on other providers. Useful when the cloud is still open, or when you are pricing a second one. How far a comparison like that can be trusted is covered in comparing clouds.

A Compartment where the Wrong Resource Cannot Be CreatedOracle Cloud A Constraint that Is Enforced rather than RehearsedGoogle Cloud A Policy Assignment that Actually DeniesAzure A Service Control Policy Whose Type Decides What Its Document Even MeansHuawei Cloud Organizations, OUs and Service Control PoliciesAWS

Installing it

module "alicloud_org_policy" {
  source  = "www.iac-bazaar.com/iac-bazaar/alicloud-org-policy/alicloud"
  version = "1.0.0"
}

A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.