AWS Control Tower
Orchestrates a governed multi-account landing zone with preventive, detective and proactive controls.
- Provider
- aws
- Kind
- Policy engine
- Category
- Operations
| property | type | values | required | kind default | this component |
|---|---|---|---|---|---|
| accountFactory | boolean | — | no | true | inherited |
| controlBehavior | enum | preventive | detective | proactive | no | — | inherited |
| controlGuidance | enum | mandatory | strongly-recommended | elective | no | — | inherited |
| effect | enum | audit | deny | modify | deploy-if-not-exists | no | — | inherited |
| enforcementMode | enum | enforced | disabled | no | — | inherited |
| managed | boolean | — | no | false | ▸ true |
| mandatoryControlsApplied | boolean | — | no | false | inherited |
| policyCount | integer | — | no | — | inherited |
| remediation | boolean | — | no | false | ▸ false |
| scope | enum | resource | group | account | organization | no | — | ▸ organization |
Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.
No rule reads this kind yet. That is a gap, not a guarantee.
nodes:
- { id: "control-tower", component: "aws-control-tower" }Cloud Configalibaba-cloud-configData Security Centeralibaba-data-security-centerAmazon CodeGuru Revieweraws-codeguru-reviewerAWS Configaws-configIAM Access Analyzeraws-iam-access-analyzerAWS Lake Formationaws-lake-formationAWS License Manageraws-license-managerAWS Organizationsaws-organizationsAWS Resource Access Manageraws-ramAmazon Verified Permissionsaws-verified-permissionsMicrosoft Entra Conditional Accessazure-conditional-accessAzure Policyazure-policyMicrosoft Entra Privileged Identity Managementazure-privileged-identity-managementCloudflare Data Loss Preventioncloudflare-dlpCalypsoAIcalypsoaiCerboscerbosOPA GatekeepergatekeeperGuardrails AIguardrails-aiHiddenLayer AI Security PlatformhiddenlayerKubeArmorkubearmorKubewardenkubewardenKyvernokyvernoLakera Guardlakera-guardLLM Guardllm-guardNeMo Guardrailsnemo-guardrailsOpen Policy AgentopaPermit.iopermit-ioGeneric policy enginepolicy-enginePrompt Securityprompt-securityProtect AIprotect-aiRebuffrebuffRobust Intelligencerobust-intelligenceSonarQube ServersonarqubeDigitalOcean CSPMdigitalocean-cspmAccess Context Managergoogle-access-context-managerAssured Workloadsgoogle-assured-workloadsBinary Authorizationgoogle-binary-authorizationIdentity and Access Managementgoogle-cloud-iamFirebase App Checkgoogle-firebase-app-checkModel Armorgoogle-model-armor
and 16 more → Policy engine page# yaml-language-server: $schema=../../schema/component.schema.json # AWS Control Tower: orchestrates a governed multi-account landing zone over Organizations, Service Catalog # and IAM Identity Center. Per "Control behavior and guidance", preventive controls are SCPs, RCPs and # declarative policies, detective controls are Config rules, proactive controls are CloudFormation hooks, # and from landing zone version 4.0 mandatory controls are no longer applied by default. schemaVersion: "1" type: "component" id: "aws-control-tower" kind: "policy-engine" provider: "aws" docs: "https://docs.aws.amazon.com/controltower/latest/userguide/what-is-control-tower.html" defaults: scope: "organization" remediation: false managed: true properties: controlBehavior: type: "enum" values: ["preventive", "detective", "proactive"] controlGuidance: type: "enum" values: ["mandatory", "strongly-recommended", "elective"] mandatoryControlsApplied: type: "boolean" default: false accountFactory: type: "boolean" default: true