Cloud Transformation

AWS Multi-Account Landing Zone

Core accounts for security, logs, network and shared services; product accounts per environment; sandboxes kept apart.

The structure from NGT's AWS landing-zone service: AWS Organizations and Control Tower at the root, core accounts every workload depends on, product accounts per environment, and developer sandboxes on a branch of their own. The data centre joins through one network account, and every account's audit trail lands in a log archive no workload can change.

private linkspokesaudit trailOn premisesAWS CloudManagement account · AWS OrganizationsCore accounts · Security and Infrastructure OUsNetwork accountSecurity and audit accountLog archive accountShared services accountProduct accounts · Workloads OUDev accountPre-prod accountProd accountDeveloper accounts · Sandbox OUData centreAWS OrganizationsAWS Control TowerAWS Config & SCPsIAM Identity CenterTerraformlanding zone as codeAWS Budgetsbilling toolingAmazon CloudWatchAWS Direct ConnectAWS Transit GatewayAWS Network FirewallAWS Security HubAWS CloudTrailAWS ManagedMicrosoft ADAmazon EKSDevAmazon EKSPre-prodAmazon EKSProdAmazon Aurora / RDSfor PostgreSQLProdDeveloper sandbox

Point at a component to light its links; select it for what it does here and the practice that makes it right on AWS.

When to use it

  • A first move to AWS, before the pilot workload
  • One shared AWS account that has grown by hand
  • Business units or products that must stay apart but share a network and a directory

How NGT delivers it

Built from code, reviewed at a gate by an NGT architect, and handed over with runbooks your team can run.

Cloud Transformation