Atmos Profiles

SkillDev tools

Atmos profiles: profile directories, --profile and ATMOS_PROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Atmos Profiles skill

What this skill tells your AI

The instructions your AI receives, as published by cloudposse/atmos in agent-skills/skills/atmos-profiles/SKILL.md and read by ahel’s review.

Use this skill when configuring or troubleshooting Atmos profiles: named configuration overlays selected with --profile or ATMOS_PROFILE.

Purpose

Profiles let teams switch configuration contexts without changing the base project config. Use them for developer, CI, tenant, cloud account, or environment-specific overrides.

atmos --profile developer terraform plan vpc -s dev
ATMOS_PROFILE=ci atmos terraform deploy vpc -s prod

Use --profile with no value in an interactive terminal to open a multi-select picker of every discovered profile. Non-interactive contexts (CI, scripts) must pass --profile=<name> or ATMOS_PROFILE explicitly.

Profile Layout

Keep profile files focused and aligned with the sections they override:

profiles/
  developer/
    atmos.yaml
    auth.yaml
  ci/
    atmos.yaml
    auth.yaml

Profile configuration is merged into the active Atmos configuration. Put shared defaults in the base config, then keep each profile to the smallest override needed.

Profile Config

Configure the profile search location in root config when the default location is not sufficient:

profiles:
  base_path: profiles

Example profiles/ci/auth.yaml override:

auth:
  providers:
    github-oidc:
      kind: github/oidc
      region: us-east-1
  identities:
    deploy:
      kind: aws/assume-role
      via:
        provider: github-oidc

Routing

NeedLoad
Profile activation, directory layout, merge behaviorstay in atmos-profiles
Auth providers, identities, OIDC, SSO, keyring in profilesatmos-auth
CI use of ATMOS_PROFILEatmos-ci
Tool versions or registries that differ by profileatmos-toolchain
Base paths and profile-relative file layoutatmos-project-layout

Guardrails

  • Keep profile overrides small and predictable; avoid duplicating the whole base atmos.yaml.
  • Use the same provider and identity names across profiles when callers should not care which profile is active.
  • Prefer ATMOS_PROFILE in CI and --profile for one-off local commands.
  • Verify the active merged configuration with atmos describe config or the relevant atmos describe component command.

Signals

GitHub stars
1k
Forks
175
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
atmos-profiles
Source
github.com/cloudposse/atmos