Introduction
Atmos is a CLI and a powerful enterprise-grade workflow automation tool for DevOps.
It's also a framework that prescribes patterns and best practices to structure and organize components and stacks to design for organizational complexity and provision multi-account environments for complex organizations.
It allows you to very quickly configure and provision infrastructure into many environments (e.g. AWS accounts and regions), and make those configurations extremely DRY.
One of the main principles of Atmos is the separation of configuration from code, so the code is generic and can be deployed anywhere (in any Organization, Organizational Unit, region, account). This design principle is called separation of concerns.
Atmos separates the components (logic) and stacks (configuration of the components for diff environments) so they can be independently managed and evolved. In the case of using Terraform, the components are Terraform root modules.
In many cases, with enterprise-grade infrastructures (multi-org, multi-tenant, multi-account, multi-region, multi-team), the configuration is much more complicated than the code. That's what Atmos is trying to solve - to make the configuration manageable, reusable (by using Imports, Inheritance, and other Atmos features) and DRY, and to make the code completely generic.
In this Quick Start guide, we describe how to provision infrastructure managed by Terraform into different AWS environments. The configurations for the environments are managed by Atmos.
This Quick Start guide describes the steps to configure and provision the infrastructure from this Quick Start repository.
You can clone it and configure to your own needs. The repository should be a good start to get yourself familiar with Atmos.
The steps to configure and provision the infrastructure are as follows: