# Config Sets

Config sets specify configuration that should be deployed to organization accounts. You can attach config sets to organizational units and to individual accounts. Organizational units inherit config sets from their parent, and accounts inherit config sets from the organizational unit they belong to.

# Command Paths

Each config set can have one or more command paths. The command paths are launched in the order they are specified when the account is deployed.

# Configuration

Config sets are defined under the configSets property:

configSets:
  MyNetwork:
    description: Network configuration
    commandPaths:
      - /networking
  Logs:
    description: Application and access logs 
    commandPaths:
      - /logs/application.yml
      - /logs/access.yml

In this example, we have two config sets: MyNetwork and Logs. We can then reference to these config sets from our organizational units and accounts configuration like so:

organizationalUnits:
  Root:
    configSets:
      - Logs
    accounts:
      - "555555555555"
  Root/SandboxAccounts:
    accounts:
      - id: "888888888888"
        configSets:
          - MyNetwork

The account 555555555555 would have only Logs config set it inherited from its organizational unit, whereas the account 888888888888 would also have MyNetwork config set.

# Deploying Config Sets

Config sets are deployed with deploy accounts command.

Last Updated: 5/4/2020, 3:54:44 PM