Landing Zones
ScaleCloud resources classified by enterprise technology topic: Landing Zones.
Download: AWS Landing Zone Guardrail Pack
This download bundle helps Cloud Governance Lead teams treat account structure, identity, network, logging, and policy as a product using Guardrail catalog and test plan in AWS environments. It emphasizes version guardrails and exception paths and provides implementation decisions that can be reviewed without relying on vendor or customer claims.
Landing Zone Governance Readiness Assessment
This assessment helps Cloud Governance Lead teams treat account structure, identity, network, logging, and policy as a product using Hierarchy, identity, network, logging, policy in Multi-Cloud environments. It emphasizes version guardrails and exception paths and provides implementation decisions that can be reviewed without relying on vendor or customer claims.
Video Tutorial: Map AWS Accounts to Enterprise Guardrails
This video tutorial helps Cloud Engineer teams treat account structure, identity, network, logging, and policy as a product using AWS Organizations and service control policies in AWS environments. It emphasizes version guardrails and exception paths and provides implementation decisions that can be reviewed without relying on vendor or customer claims.
On-Demand Webinar: Designing Landing Zones as Products
This on-demand webinar helps Cloud Platform Leader teams treat account structure, identity, network, logging, and policy as a product using Landing zone product model and guardrails in Multi-Cloud environments. It emphasizes version guardrails and exception paths and provides implementation decisions that can be reviewed without relying on vendor or customer claims.
Landing Zone Guardrail Definition Template
This template helps Cloud Governance Lead teams treat account structure, identity, network, logging, and policy as a product using Control objective, policy, test, exception in AWS environments. It emphasizes version guardrails and exception paths and provides implementation decisions that can be reviewed without relying on vendor or customer claims.
Illustrative Case Study: Establishing a Healthcare Data Landing Zone
This illustrative case study helps Cloud Governance Lead teams treat account structure, identity, network, logging, and policy as a product using Policy, private connectivity, data controls in Microsoft Azure environments. It emphasizes version guardrails and exception paths and provides implementation decisions that can be reviewed without relying on vendor or customer claims.
The Enterprise Landing Zone Field Guide
This ebook helps Cloud Architect teams treat account structure, identity, network, logging, and policy as a product using Cloud hierarchy, identity, network, logging, policy in Multi-Cloud environments. It emphasizes version guardrails and exception paths and provides implementation decisions that can be reviewed without relying on vendor or customer claims.
Build a Policy-Tested AWS Landing Zone Baseline
This technical guide helps Cloud Platform Engineer teams treat account structure, identity, network, logging, and policy as a product using Terraform, AWS Organizations, policy tests in AWS environments. It emphasizes version guardrails and exception paths and provides implementation decisions that can be reviewed without relying on vendor or customer claims.
How to Structure Cloud Account and Subscription Naming
This knowledge base article helps Cloud Administrator teams treat account structure, identity, network, logging, and policy as a product using Resource hierarchy and naming standards in Multi-Cloud environments. It emphasizes version guardrails and exception paths and provides implementation decisions that can be reviewed without relying on vendor or customer claims.
Governed Multi-Account AWS Landing Zone
This reference architecture helps Cloud Architect teams treat account structure, identity, network, logging, and policy as a product using AWS Organizations, IAM Identity Center, CloudTrail in AWS environments. It emphasizes version guardrails and exception paths and provides implementation decisions that can be reviewed without relying on vendor or customer claims.