Atmos Secrets

DevOps & Security

atmos-secrets

Atmos Secrets 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 Secrets: declarative secrets.vars, !secret, cloud/Vault/1Password/SOPS backends, init/set/get/import/push/pull/shell/exec/validate, masking, and CI validation

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-secrets/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/atmos-secrets, 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 Secrets

Use this skill for declared secrets, secret backends, and the atmos secret command family. Secrets must be declared before they can be set, read, injected, or resolved with !secret.

Related Skills

Need	Load
Store-backed non-secret values	atmos-stores
YAML `!secret` and `!store` functions	atmos-yaml-functions
Auth identity for secret backend access	atmos-auth
Local Vault/OpenBao testing	atmos-emulator

Declare Secrets

Declare secrets under component secrets.vars and keep Terraform inputs secret-aware:

components:
  terraform:
    app:
      secrets:
        vars:
          DATADOG_API_KEY:
            description: Datadog API key
            store: prod/ssm
            required: true
      vars:
        datadog_api_key: !secret DATADOG_API_KEY

Supported backend families include AWS SSM, AWS Secrets Manager, HashiCorp Vault, Azure Key Vault, GCP Secret Manager, 1Password, and SOPS-encrypted files.

Commands

Command	Purpose
`atmos secret list -s <stack> -c <component>`	List declared secrets and status
`atmos secret init -s <stack> -c <component>`	Provision/rotate declared secrets interactively
`atmos secret set <name> -s <stack> -c <component>`	Set a declared secret
`atmos secret get <name> -s <stack> -c <component>`	Retrieve a declared secret, masked by default
`atmos secret import -s <stack> -c <component>`	Bring existing backend secrets under management
`atmos secret pull -s <stack> -c <component>`	Download declared secrets to a local file
`atmos secret push -s <stack> -c <component>`	Upload declared secrets from a local file
`atmos secret shell -s <stack> -c <component>`	Start a shell with secrets in environment
`atmos secret exec -s <stack> -c <component> -- <cmd>`	Run one command with secrets injected
`atmos secret validate -s <stack> -c <component>`	CI gate for required initialized secrets
`atmos secret keygen ...`	Generate key material for supported vault backends

Use --identity when backend access needs an Atmos Auth identity. Use --type to disambiguate component kinds.

Safety Rules

Keep secrets declared, not scattered through raw !store calls.
Prefer !secret for sensitive values and !store/!store.get for non-sensitive shared data.
Leave --mask enabled for normal operations; masked inspection should not leak values.
Use atmos secret validate in CI before plan/apply workflows that require secrets.
Never commit pulled local secret files unless they are intentionally SOPS-encrypted and approved by repository policy.