Takomo can be used to manage any existing AWS organization. You can also create a new organization using CLI.
Getting Started with a New Organization
If you don't have an existing organization, you can create one using create organization command:
This command uses the credentials found from the current terminal session to create a new organization and make the AWS account bound to the credentials as the master account of the organization. It will also create an organization directory, and inside it, a file named organization.yml containing the minimum configuration needed to manage the organization.
After running the command, you will have the following file structure:
Contents of the generated organization.yml file will look like this:
Getting Started with an Existing Organization
If you have an existing organization, you will need to create the required configuration files manually. You can start by copy-pasting the contents of the organization.yml file shown above and setting the masterAccountId with your organization master account's id.
Next, you will need to make your local configuration to match with the current organization state. You need to describe all organizational units, policies and member accounts in the organization.yml file, which can be quite an effort, but deploy organization command will show you differences between your local configuration and the actual organization state. Once there are no changes to be executed, your configuration is completed.
Organization Feature Set
AWS Organizations allows you to choose what features you want to have enabled. There are two options: ALL and CONSOLIDATED_BILLING. In most cases, ALL should be chosen because it enables many useful features such as authorization and management policies. The feature set is chosen when the organization is created and can be changed at any time.
If you create a new organization using create organization command, you can specify which feature set to use. Once the organization is created, you can change the feature set from AWS console or using AWS CLI.
Master Account Id
The organization master account needs to be defined in the organization configuration. Takomo uses this information to ensure that organization management operations target the correct AWS organization. Use masterAccountId property to specify the master account.
Example: Setting the master account id
When managing the AWS organization, you need to have credentials with sufficient permissions to manage the organization itself and assume the administrative role to all accounts that belong to the organization. In other words, Takomo's organization management commands need to be run with an IAM user's credentials located in the organization master account.
Organization Admin Role
By default, Takomo uses the credentials currently available in the terminal session to execute operations that query information from the organization and alter its state. It is also possible to tell Takomo to use a specific IAM role to perform these organization management operations by setting the organizationAdminRoleName property in the organization configuration file.
Example: Setting the organization admin role name
Please note that organizationAdminRoleName accepts a role name and not full role ARN.