Organizations
  • What is Takomo Organizations?
  • Organization configuration
    • Introduction
    • Directory structure
    • Master account
    • Organizational units
    • Accounts
    • Policies
    • Deploying organization
  • Accounts
    • Creating accounts
    • Account aliases
    • Listing accounts
  • Account stacks
    • Config sets
    • Bootstrap config sets
    • Variables
    • Deploying config sets
    • Removing config sets
  • Command-line usage
    • Organization
      • Create organization
      • Describe organization
      • Deploy organization
    • Account
      • Create account
      • Create account alias
      • Delete account alias
      • List accounts
    • Account stacks
      • List accounts stacks
      • Deploy accounts
      • Undeploy accounts
      • Bootstrap accounts
      • Tear down accounts
Powered by GitBook
On this page

Was this helpful?

  1. Organization configuration

Organizational units

You define the hierarchy for your organizational units (OUs) with the organziationalUnits property at the top level of the organization.yml file. It's an object whose keys are OU paths, and values are configuration for the corresponding OUs.

The root OU of the hierarchy is always Root, and all other OUs are its children.

Examples

This is the minimum hierarchy. As you can see, you must have the Root OU but you don't have to provide configuration for it.

organization/organization.yml
masterAccountId: "098765432100"

organizationalUnits:
  Root: {}

Here we have a more complex hierarchy with some nested OUs.

organization/organization.yml
masterAccountId: "098765432100"

organizationalUnits:
  Root/Workloads/Dev: {}
  Root/Workloads/Test: {}
  Root/Workloads/Prod: {}
  Root/Sandbox: {}

The above configuration is flat but represents this kind of hierarchy:

Root
├─ Workloads
│  ├─ Dev
│  ├─ Test
│  └─ Prod
└─ Sandbox
PreviousMaster accountNextAccounts

Last updated 3 years ago

Was this helpful?