Skip to content
Cloud Governance Tools

Resource and cost guardrails restrict what can be built, and reject the request with a 403

7 guardrails in the library address resource and cost: 2 AWS, 3 Azure, 2 Google Cloud. The first in the list, "Restrict EC2 launches to approved instance types", denies ec2:RunInstances unless the instance type is in the approved list (t2.micro and t3.micro in the example).

All risk classes ยท Download the library

Guardrails in this class limit resource types, sizes and purchases. The library holds 7. They are the most direct form of a guardrail: the request is refused. In AWS, a list of approved EC2 instance types means a launch of any other type fails for every principal in the affected accounts, and the example list must be replaced with your own. Azure's allowed virtual machine size definition rejects other sizes with 403 at create or update time, and its allowed resource types definition affects only types that support tags and location unless the mode is changed. Google's load balancer constraint requires every type to be listed explicitly.

"Tested first" says whether the provider documents a way to see the guardrail's effect before enforcing it. Read 10 Nov 2026.
GuardrailCloudMechanismRisk classTested first
Restrict EC2 launches to approved instance typesAWSService control policies (SCPs)Resource and costdocumented
Restrict AWS Marketplace subscription changesAWSService control policies (SCPs)Resource and costdocumented
Allowed resource typesAzureAzure Policy (built-in definitions)Resource and costdocumented
Not allowed resource typesAzureAzure Policy (built-in definitions)Resource and costdocumented
Allowed virtual machine size SKUsAzureAzure Policy (built-in definitions)Resource and costdocumented
Shared reservations owner projectsGoogle CloudOrganization Policy Service (managed and legacy constraints)Resource and costnone found
Restrict load balancer creation based on load balancer typesGoogle CloudOrganization Policy Service (managed and legacy constraints)Resource and costnone found

What these guardrails break

  • Restrict EC2 launches to approved instance types (AWS): Launches of any instance type not in the list fail for every principal in the affected accounts; the example list must be replaced with the types you approve.
  • Restrict AWS Marketplace subscription changes (AWS): Teams cannot subscribe to or cancel Marketplace products on their own; the README says to restrict these changes to a privileged role.
  • Allowed resource types (Azure): Only resource types that support tags and location are affected unless you duplicate the definition and change its mode to All.
  • Not allowed resource types (Azure): A deny effect returns 403 for any create or update of a listed type, and compliance results are shown only for non-compliant resources.
  • Allowed virtual machine size SKUs (Azure): Requests for VM sizes outside the list are rejected with 403 at create or update time.
  • Shared reservations owner projects (Google Cloud): Google documents the required value format: projects/PROJECT_NUMBER or under:projects/PROJECT_NUMBER.
  • Restrict load balancer creation based on load balancer types (Google Cloud): Google documents that every load balancer type to be allowed or denied must be listed explicitly, from a fixed list of values.

Where Act is behind

Act writes guardrails in the provider's own mechanisms and hands them to your pipeline to enforce, so it is bounded by what those mechanisms can express in each cloud. It does not apply them itself, the boundary types it names are AWS's and Azure's, and exception and waiver handling after a guardrail ships was described as roadmap.

Sources

  1. Restrict EC2 launches to approved instance types, read 10 Nov 2026
  2. Restrict AWS Marketplace subscription changes, read 10 Nov 2026
  3. Allowed resource types, read 10 Nov 2026
  4. Not allowed resource types, read 10 Nov 2026
  5. Allowed virtual machine size SKUs, read 10 Nov 2026
  6. Shared reservations owner projects, read 10 Nov 2026
  7. Restrict load balancer creation based on load balancer types, read 10 Nov 2026

Last reviewed 16 Nov 2026.