atmos-auth

Automate AWS authentication for Atmos-managed multi-stack environments.

98|34|Updated Apr 27, 2018

Search Tags:#authentication #aws #cli #identity #sso #profile #atmos

Ready to run

npx skills add https://github.com/cloudposse/docs --skill atmos-auth

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: atmos-auth
Source: https://github.com/cloudposse/docs/tree/main/examples/snippets/.claude/skills/atmos-auth
Command: npx skills add https://github.com/cloudposse/docs --skill atmos-auth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AWS authentication across multiple Atmos-managed stacks is often manual and error-prone. This Skill simplifies configuring ATMOS_PROFILE, triggers SSO login flows, and ensures the correct identity is automatically used per stack.

Core Features & Use Cases

ATMOS_PROFILE setup: centralizes identity mapping for workflows.
SSO login flows: triggers a browser-based login to obtain tokens.
Per-stack identity resolution: automatically selects the right credentials for each target stack.

Quick Start

Set ATMOS_PROFILE to your profile and run atmos auth login to authenticate and enable Atmos to automatically assume the correct identity per stack.

Frequently Asked Questions about atmos-auth

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate AWS authentication across multiple Atmos stacks?▼

Automating AWS authentication across multiple Atmos stacks requires configuring ATMOS_PROFILE to centralize identity mapping, which then selects the correct credentials automatically for each target stack during routine operations.

How does SSO login work with Atmos CLI for development and production environments?▼

Atmos SSO login triggers a browser-based flow to obtain tokens, requiring per-stack identity mappings to automatically assume the correct identity across development, staging, and production environments.

Do I need ATMOS_PROFILE configured to use AWS SSO with Atmos?▼

Yes, ATMOS_PROFILE configuration is required to enable per-stack identity resolution and automatic credential selection during SSO login flows in Atmos-managed environments.

What's the best way to manage AWS identity resolution for multi-stack environments?▼

The best way to manage AWS identity resolution for multi-stack environments is centralizing identity mapping via ATMOS_PROFILE, which automates credential selection per stack and eliminates manual, error-prone configuration.

Why does Atmos pick the wrong AWS credentials for my target stack?▼

Atmos picks the wrong AWS credentials when per-stack identity mappings are missing or ATMOS_PROFILE is unset, preventing automatic identity resolution during your workflow.