Can I use this for cross-account access?

Yes, the skill supports AWS STS AssumeRole (with separate read and write roles) and identity-based authentication for secure cross-account and cross-region access.

How do I write data to an Atmos store?

Data is typically written automatically using Atmos hooks configured to trigger 'after-terraform-apply', which maps Terraform outputs to specific keys in your chosen store.

When should I use a store instead of terraform.state?

Use stores for sharing data not managed by Terraform, accessing external systems, or when you need faster cross-component reads via write-back hooks that bypass state lookups.

What backends does the atmos-stores skill support?

It supports AWS SSM Parameter Store, Azure Key Vault, Google Secret Manager (GSM), Redis, and JFrog Artifactory.

What is the difference between !store and !store.get?

!store follows the standard Atmos stack/component/key naming convention for automated path construction, while !store.get allows you to fetch any arbitrary key path from a store.

Atmos External Stores Configuration

Name: Atmos External Stores Configuration
Author: cloudposse

bycloudposse

•

1,293

•

Cloud Infrastructure

Configures and manages external key-value backends for sharing data across Atmos-managed Terraform components.

This skill empowers Claude to configure and utilize external storage backends within the Atmos ecosystem, enabling seamless data sharing between infrastructure components without relying solely on Terraform state. It provides comprehensive support for AWS SSM, Azure Key Vault, Google Secret Manager, Redis, and Artifactory, allowing users to implement cross-account configuration, integrate CI/CD pipelines, and establish write-back mechanisms via post-apply hooks for faster, more flexible infrastructure management.

Key Features

011,293 GitHub stars

02Enables dynamic data retrieval using Go templates and YQ-style queries

03Configures multiple provider backends including AWS, Azure, GCP, Redis, and Artifactory

04Supports identity-based authentication and cross-account/cross-region role assumption

05Implements !store and !store.get YAML functions for component-aware or arbitrary key access

06Sets up automated data persistence using lifecycle hooks after Terraform apply or deploy

Use Cases

01Speeding up cross-component data retrieval in complex multi-stack environments using write-back hooks

02Integrating Terraform configurations with external secret managers or configuration caches

03Sharing common infrastructure data (like VPC IDs) across different accounts or regions without state lookups

Key Features

011,293 GitHub stars

02Enables dynamic data retrieval using Go templates and YQ-style queries

03Configures multiple provider backends including AWS, Azure, GCP, Redis, and Artifactory

04Supports identity-based authentication and cross-account/cross-region role assumption

05Implements !store and !store.get YAML functions for component-aware or arbitrary key access

06Sets up automated data persistence using lifecycle hooks after Terraform apply or deploy

Use Cases

01Speeding up cross-component data retrieval in complex multi-stack environments using write-back hooks

02Integrating Terraform configurations with external secret managers or configuration caches

03Sharing common infrastructure data (like VPC IDs) across different accounts or regions without state lookups