# Atmos Secrets

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

- Skill: `cloudposse/atmos-secrets` (Agent Skill)
- Install (CLI): `npx skillmds@latest add cloudposse/atmos-secrets`
- Raw SKILL.md: https://api.skillmd.com/api/skills/cloudposse/atmos-secrets/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: cloudposse (https://skillmd.com/u/cloudposse)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/cloudposse/atmos-secrets

---


# 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](../atmos-stores/SKILL.md) |
| YAML `!secret` and `!store` functions | [atmos-yaml-functions](../atmos-yaml-functions/SKILL.md) |
| Auth identity for secret backend access | [atmos-auth](../atmos-auth/SKILL.md) |
| Local Vault/OpenBao testing | [atmos-emulator](../atmos-emulator/SKILL.md) |

## Declare Secrets

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

```yaml
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.