Skip to content
Nubent

/Multi-account governance

AWS landing zone with Control Tower and a multi-account strategy

We design and implement your AWS landing zone: a governed multi-account foundation with AWS Control Tower and Organizations, centralized access through IAM Identity Center, SCPs, centralized logging and security, and automated account creation in Terraform. Every new account is born with the controls already in place.

/Diagnosis

Signs it is time

Everything lives in one account

Production, staging, development and testing share the same AWS account, and a mistake in one environment can hit the others or customer data.

IAM users and keys everywhere

There are IAM users with long-lived access keys and broad permissions, and nobody knows for sure who can do what in each account.

An audit or certification is coming

An enterprise customer, SOC 2 or ISO 27001 requires environment separation, centralized logging and preventive controls that do not exist today.

Accounts created by hand

Every new account is configured differently, with no security baseline, no tags and no integration with billing or logging.

/What we deliver

Concrete deliverables, in your repository

  • Multi-account design

    An organizational unit and account structure by environment, workload and function, aligned with AWS guidance for organizations.

  • Control Tower configured

    An AWS Control Tower landing zone with log archive and audit accounts, and preventive, detective and proactive controls enabled.

  • Access with IAM Identity Center

    Single sign-on with your identity provider, permission sets per role and removal of IAM users with permanent keys.

  • SCPs and guardrails

    Service control policies that restrict regions, protect security services and block high-risk actions.

  • Centralized logging and security

    Organization-wide CloudTrail, AWS Config, Security Hub and GuardDuty with delegated administration, and immutable logs in a dedicated account.

  • Account Factory in Terraform

    Account creation through pull requests with Account Factory for Terraform, networking, tags and security baseline included.

/How we work

Our process

  1. Discovery

    We inventory current accounts, access, networks and workloads with read-only access, and gather business and compliance requirements.

  2. Landing zone design

    We define organizational units, accounts, the access model, networking, controls and logging strategy, validated with your team.

  3. Implementation in Terraform

    We deploy Control Tower, IAM Identity Center, SCPs, security services and Account Factory, all versioned in your repository.

  4. Workload migration

    We move existing environments and workloads into the new accounts gradually and hand over runbooks and operating documentation.

What an AWS landing zone is, and why multi-account

A landing zone is a preconfigured, secure and scalable multi-account AWS environment that serves as the starting point for all your workloads. It defines how accounts are organized, how people get access, which controls apply and where logs are centralized. Changing it later, with workloads in production, costs far more than getting it right at the start.

AWS recommends using multiple accounts because the account is the strongest isolation boundary on the platform. Separating production from development, and workloads from one another, reduces the blast radius of a mistake or a compromised credential, simplifies cost attribution and makes audit requirements easier to meet. Moving resources between accounts later means migrating data, networks and permissions.

AWS Control Tower and AWS Organizations

AWS Organizations lets you manage multiple accounts centrally, grouped into organizational units, with consolidated billing and shared policies. AWS Control Tower builds on Organizations to deploy a landing zone that follows best practices: it creates dedicated log archive and audit accounts, configures CloudTrail and AWS Config at the organization level and enables predefined controls.

Control Tower controls can be preventive, implemented with SCPs; detective, implemented with AWS Config rules; or proactive, validating resources before they are deployed. We pick the ones that make sense for your context and add custom controls when the business or regulation requires it.

SCPs and IAM Identity Center: clear access and clear limits

Service control policies define the maximum permissions possible within each account or organizational unit, regardless of what local IAM policies say. We use them to restrict allowed regions, prevent CloudTrail or GuardDuty from being turned off, protect platform roles and block high-risk actions.

For people, IAM Identity Center centralizes access with single sign-on from your identity provider, such as Microsoft Entra ID, Okta or Google Workspace. Each role receives specific permission sets per account, with temporary credentials instead of permanent keys. That way onboarding or offboarding someone is handled in a single place.

Centralized logging and Account Factory for Terraform

All of the organization's audit logs, such as CloudTrail, AWS Config and VPC flow logs, are sent to a log archive account with S3 buckets protected against deletion and encrypted with KMS. Security Hub and GuardDuty are administered through delegation from a security account, giving you a single view of findings across the entire organization.

To create new accounts we use Account Factory for Terraform. Each account is requested through a pull request and created with its networking, tags, roles and security baseline already configured. If you already have an organization, we design the transition: we enroll accounts in Control Tower, reorganize organizational units and migrate workloads gradually.

/FAQ

AWS Landing Zone: frequently asked questions

Another question? Write to hello@nubent.com and an engineer will answer.

What is an AWS landing zone?

It is a well-designed multi-account AWS environment, with an account structure, centralized access, security controls, logging and networking preconfigured, that serves as the foundation for deploying workloads. It can be implemented with AWS Control Tower, which automates much of the setup, or as a custom build with Organizations and Terraform.

What is the difference between AWS Control Tower and AWS Organizations?

Organizations is the core service for grouping and managing multiple accounts, with consolidated billing and policies such as SCPs. Control Tower is built on top of Organizations and automates the creation of a landing zone with best practices: log and audit accounts, predefined controls, a compliance dashboard and an account factory.

How many AWS accounts does a startup need?

A reasonable starting point is a management account, a log archive account, an audit or security account, and separate accounts for production, staging and development. As teams or products grow, you add accounts per workload. The cost of having more accounts is low and the isolation benefit is high.

Can Control Tower be set up on an existing organization?

Yes. Control Tower can be deployed into an existing organization and then enroll the accounts and organizational units you already have. Beforehand we review existing SCPs, CloudTrail trails and AWS Config setups to avoid conflicts, and we plan the transition in stages so production workloads are not affected.

What are service control policies in AWS?

They are AWS Organizations policies that define the maximum permissions available in the accounts of an organizational unit. On their own they do not grant permissions; they set the ceiling for what any user or role can do, even one with broad IAM permissions. They are used to restrict regions, protect security services and block risky actions.

Next step

Let's talk about your AWS Landing Zone project

30 minutes with an engineer. Concrete next steps, whether or not you work with us.