Skip to main content

What's Next

You've completed the Learn Atmos path! You understand components, stacks, YAML configuration, imports, inheritance, organization, and how to connect components. Now let's explore what's next.

What You've Learned​

Over the last 8 pages, you've built a solid foundation in Atmos:

✅ Why Atmos exists - Solving configuration complexity for enterprise infrastructure ✅ Core concepts - Components, stacks, and separation of configuration from code ✅ Your first stack - A working example from scratch ✅ YAML in Atmos - Scope, deep merge, tags vs templates ✅ Imports - Reusing configuration across stacks ✅ Inheritance - Creating component variations without duplication ✅ Organization - Structuring stacks for maintainability and scale ✅ Connecting components - Sharing data via remote state

This is enough to build real infrastructure with Atmos. Everything else is refinement.

Learn Advanced Techniques​

Ready to level up? Explore advanced Atmos features:

Ready to learn this topic?

Advanced Stack Configuration​

Go deeper into stack mechanics:

Explore Stack Configuration

Ready to learn this topic?

Templates & Functions​

Learn Atmos templating:

Explore Functions

Ready to learn this topic?

Workflows​

Automate complex deployments:

Learn Workflows

Ready to learn this topic?

Validation & Policy​

Enforce standards and prevent errors:

Learn Validation

Ready to learn this topic?

Vendoring​

Manage external components:

Learn Vendoring

Best Practices & Patterns​

Learn from real-world experience:

Migrate from Other Tools​

Coming from another tool? We have migration guides:

Get Help & Connect​

You're not alone! Join the community:

Quick Reference​

Bookmark these for quick lookups:

Real-World Examples​

See Atmos in action:

Keep Learning​

Atmos is actively developed. Stay up to date:

What to Build​

Here are some projects to solidify your learning:

Beginner Projects​

  1. Multi-environment VPC - Deploy the same VPC to dev, staging, prod with different CIDR blocks
  2. Shared services architecture - Central account with shared RDS, accessed by app accounts
  3. Component library - Create abstract base components for your team to inherit from

Intermediate Projects​

  1. Multi-region deployment - Same stack across multiple AWS regions
  2. Custom workflow - Automate deployment of 5+ dependent components in order
  3. Validation policies - OPA policies enforcing naming conventions and tagging

Advanced Projects​

  1. Multi-cloud architecture - AWS and GCP components in the same stack
  2. GitOps pipeline - Automated Atmos deployment via GitHub Actions
  3. Component vendoring - Pull and customize external component libraries

You're Ready​

You have everything you need to build production infrastructure with Atmos. The rest is practice and refinement.

Start small. Deploy a VPC. Add an EKS cluster. Connect them. Build from there.

Keep it simple. Use advanced features when you need them, not before.

Ask for help. The community is friendly and responsive.

Welcome to the Atmos community. We're excited to see what you build! 🚀

Best PracticesStack ReferenceCLI CommandsJoin Slack