A Terraform and DevOps orchestration tool that manages DRY configurations with hierarchical imports and inheritance.
Atmos is a framework for orchestrating and operating infrastructure workflows across multiple cloud and DevOps toolchains. It centralizes cloud automation into a robust CLI, streamlining complex environments and workflows into straightforward commands. Its core strength lies in managing DRY configurations at scale for tools like Terraform, using hierarchical stacks and reusable components.
DevOps engineers, cloud architects, and platform teams managing large-scale, multi-account, or multi-region cloud infrastructure, particularly those using Terraform. It is also suited for SaaS companies building multi-tenant systems and organizations in regulated industries needing compliant infrastructure.
Developers choose Atmos for its powerful abstraction layer (Stacks and Components) that enforces DRY principles and clear separation of configuration from code, enabling consistent management of complex infrastructures. It offers native Terraform support, extensibility to any tooling, and built-in features like vendoring, custom commands, and workflow orchestration out of the box.
👽 Terraform Orchestration Tool for DevOps. Keep environment configuration DRY with hierarchical imports of configurations, inheritance, and WAY more. Native support for Terraform and Helmfile.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Uses YAML-based stacks and components to enforce DRY principles, enabling reuse and inheritance across environments, which simplifies managing large infrastructures as highlighted in the philosophy.
Provides native support for Terraform orchestration, including backend generation and varfile management, ensuring compatibility while adding powerful abstractions, as detailed in the core features.
Supports custom commands and workflows, allowing integration with any DevOps toolchain and cloud platform, evidenced by its use with Kubernetes and other tools in the documentation.
Includes vendoring for dependencies, OPA policies for compliance, and a terminal UI, offering out-of-the-box capabilities for enterprise-scale operations, as listed in the core features.
The hierarchical configuration model and numerous features require significant time to master, especially for teams new to such abstractions or coming from simpler setups, despite the documentation.
Enforces specific project structures and naming conventions, which can be restrictive and require adaptation of existing codebases or workflows, as mentioned in the patterns section.
Collects anonymous usage data by default, requiring explicit opt-out, which might raise privacy concerns or compliance issues in sensitive environments, as noted in the telemetry section.