The time has come! This section will guide you through running the first several Substrate commands to configure your Substrate-managed AWS organization.
All Substrate commands should be run from the same directory. Many commands will read and write files there to save your input and pass configuration and state from one command to another.
The most natural options are, in no particular order:
(Git is by no means required - you’re free to choose any version control software.)
You can always change your mind on this simply by moving
substrate.* into another directory or repository.
Decide and change to that directory before proceeding.
If you like, now or later, you can set
SUBSTRATE_ROOT in your environment to a fully-qualified directory pathname. Substrate will change to this directory at the beginning of every command so you don’t have to micromanage your working directory.
When you run this program, you’ll be prompted several times for input. As much as is possible, this input is all saved to the local filesystem and referenced on subsequent runs.
The first of these inputs is an access key from the root of your new AWS account. It is never saved to disk (for security reasons) so keep it handy until later in this guide when it you’re told it’s safe to delete it. To create a root access key:
This program creates your AWS organization, creates the audit account and enables CloudTrail, creates the deploy and network accounts, configures a basic service control policy, and creates the necessary roles and policies to allow your administrators to move relatively freely.
When this program exits, you should add
.substrate.* to your version control system’s ignore list (e.g.
.gitignore) and commit
substrate.* to version control. Do not forget your root access key yet. It is safe to re-run this program at any time.
While you’re logged into your management account using the root credentials, follow these steps to delegate access to billing data to people and tools assuming IAM roles.
The previous step created the three special AWS accounts - audit, deploy, and network - but neglected to complete the configuration of the deploy and network accounts. The reason for this is because both of these accounts are managed by Terraform code. The bootstrapping steps generate some code while leaving room for you to add more later.
Here, too, during your first run you’ll be prompted for your root access key.
This program additionally asks for the names of your environments, the release qualities you want to use, and the specific combinations that are valid. You may want to peek ahead at domains, environments, and qualities to see how these pieces fit together. Environments typically have names like “development” and “production” — they identify a set of data and all the infrastructure that may access it. Qualities are names given to independent copies of your infrastructure within an environment that make it possible to incrementally change AWS resources. If you’re unsure, defining a single quality called “default” is good.
It also asks which AWS regions you want to use. Your answers inform how it lays out your networks to strike a balance between security, reliability, ergonomics, and cost. Substrate recommends starting with 2-4 regions that make geographic sense to your customers.
This program may attempt to programmatically raise the limit on some specific AWS service quotas. Depending on the regions you chose, how many environments and qualities you specified, and how the AWS support staff are feeling, this may block you for a long time. It’s recommended to start slow by, for instance, only specifying “admin” and “production” environments, expecting to add more later.
When this program exits, you should commit
root-modules/network/ to version control. It is safe to re-run this program at any time and during those runs you can add additional environments and qualities if you so choose.
This program doesn’t need any input except during its first run in which you’ll be prompted for your root access key.
When this program exits, you should commit
root-modules/deploy/ to version control. It is safe to re-run this program at any time.
Configuring Substrate shell completion
Integrating your identity provider to control access to AWS