17 posts tagged with "Documentation"

Copying the same resource tags into every component makes ownership changes tedious and lets environments drift. Two focused examples now show how to define shared tags once and inherit them across stacks: one uses AWS provider default tags, and the other passes tags to Null Label. Each includes a terminal recording and commands you can run locally.

Infrastructure written with AWS CDK or CDK Terrain needs a synthesis step before it can be deployed. Keeping that step connected to the right environment, inputs, and deployment command is part of managing the application. Our new CDK tutorial shows how Atmos hooks run synthesis while Atmos stacks supply deployment configuration.

Reading about a feature should lead directly to trying it. Finding its example directory, installing Atmos, and assembling the first commands adds unnecessary work. Changelog posts with runnable examples, command documentation, and individual example pages now include a quick start with installation instructions and copyable commands.

The official Atmos Media Kit is now available with downloadable logo assets, usage guidance, brand colors, and product language for teams writing about or building integrations with Atmos.

A common question from the community is: how do I use Atmos with Packer to build AMIs, and automate the whole build → approve → share process? We've published a new gist that shows exactly that — a reference recipe combining several Atmos features into one production-shaped workflow.

Every page on atmos.tools is now available as raw Markdown. Append .md to any docs URL and you'll get a clean, MDX-component-aware Markdown file ready to paste into an LLM, a ticket, or another doc.

Atmos has always been cloud agnostic, but our documentation hasn't always reflected that. This release adds comprehensive multi-cloud documentation including a new design pattern for organizing stacks across different cloud providers.

Fixed an issue where retrieving values from Artifactory stores would fail when using nested paths, and corrected store documentation to accurately reflect supported backends.

Finding information in documentation shouldn't require knowing the exact terminology or page structure. With Ask AI, you can now ask natural language questions about Atmos and get intelligent, contextual answers—powered by Algolia DocSearch v4 and ChatGPT.

We're sharing the Atmos Product Roadmap—a transparent view of where we've been, where we're headed, and what's coming next. Infrastructure teams evaluating Atmos often ask "What's the long-term vision?" The roadmap answers that question openly.

We've reorganized the Atmos documentation to better serve both newcomers and experienced users. Here's what changed and why.

We've added comprehensive migration guides to help teams adopt Atmos regardless of their starting point.

This release brings documentation improvements to Atmos, making it easier to understand and use Terraform commands. We've focused on comprehensive command documentation and automated screengrab generation.

We've added comprehensive documentation for all 35 Terraform commands in Atmos, making it easier to understand how to orchestrate Terraform with stack-based configurations. Each command now has dedicated documentation with usage examples, arguments, flags, and integration details.

When you deploy infrastructure across multiple environments—dev, staging, production—you need a way to manage which version of each component runs where. Maybe your VPC module in dev is testing new CIDR ranges, while production stays on the stable version until you're confident the changes work.

That's version management: deciding how different versions of your infrastructure components flow through your environments.

The obvious answer—pin every version in every environment—turns out to optimize for the wrong thing. Strict pinning creates divergence by default: environments drift apart unless you constantly update pins. It weakens feedback loops because lower environments stay on old versions, hiding cross-environment impacts. And at scale, you face PR storms from automated dependency updates.

So what's the right approach? It depends. We've documented these strategies as design patterns—proven approaches that optimize for different goals. Some prioritize convergence and fast feedback; others prioritize control and reproducibility. The best choice depends on your organization's culture, team size, and how you already think about software delivery.

We've published two comprehensive guides to help you adopt and integrate atmos auth into your workflows: migrating from Leapp and configuring Geodesic for seamless authentication.

We're excited to launch the Atmos Changelog—your go-to source for feature announcements, technical deep dives, and best practices for managing cloud infrastructure at scale.