Reference architectures / landing zones

Why important?

Reference architectures speed up secure standardisation (network, IAM, logging, guardrails). Without these patterns, implementation risk rises.

How measured?

• 0 = No reference architectures/landing zones
• 1 = Generic high-level guidance
• 2 = Simple references, little depth/automation
• 3 = Usable landing zones/blueprints for the core scope
• 4 = Comprehensive references (security, networking, IAM) + IaC templates
• 5 = Very comprehensive + validated (best practices) + broadly evidenced
• N/A = no reliable evidence

Sources / Evidence

• https://aws.amazon.com/solutions/implementations/landing-zone-accelerator-on-aws/
• https://docs.aws.amazon.com/solutions/latest/landing-zone-accelerator-on-aws/concepts-and-definitions.html
• https://www.ovhcloud.com/en/architecture-center/
• https://www.ovhcloud.com/asia/architecture-center/reference/
• https://learn.microsoft.com/azure/cloud-adoption-framework/ready/landing-zone/
• https://www.noris.de/wp-content/uploads/noris-Sovereign-Cloud-Product-Sheet.pdf
• https://www.syseleven.de/produkte-services/openstack-cloud/

Validation questions (RFP)

• Are there landing-zone blueprints including logging, IAM, network and key management? Are there audited references for regulated sectors (public sector, finance, critical infrastructure)?

Scores comparison