Atmos Profiles

DevOps & Security

atmos-profiles

Atmos Profiles is an Agent Skill for devops & security published in the cloudposse/atmos repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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

View on GitHub ↗

QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

Open your project in Codex.
Copy and paste the prompt below.
Review files and risks before approving any action.

Prompt to paste

Inspect the Agent Skill at https://github.com/cloudposse/atmos/blob/HEAD/agent-skills/skills/atmos-profiles/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/atmos-profiles, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Atmos Profiles

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

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

Need	Load
Profile activation, directory layout, merge behavior	stay in `atmos-profiles`
Auth providers, identities, OIDC, SSO, keyring in profiles	`atmos-auth`
CI use of `ATMOS_PROFILE`	`atmos-ci`
Tool versions or registries that differ by profile	`atmos-toolchain`
Base paths and profile-relative file layout	`atmos-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.