Skip to main content

Validate authentication for a stack or component

· 2 min read
Erik Osterman
Erik Osterman
Founder @ Cloud Posse

Shared authentication configuration can leave account and role values for stacks to supply. Validating only the global configuration rejects those incomplete definitions before their component overrides are considered. The auth validation command can now check the merged configuration for a selected stack or component.

Scoped authentication validation options
00:00.0 / 00:00.0

The Problem​

A global identity can provide the shared settings while a stack or component supplies its principal. Global validation alone cannot determine whether that final configuration is valid.

The Fix​

Select a stack to validate every concrete component's merged authentication configuration independently. Add a component selector to narrow the check. Errors identify the stack, component type, and component involved.

Unscoped validation remains strict. Validation checks configuration without authenticating or executing dynamic stack expressions; required values that remain dynamic are reported as not fully validated.

How to Use It​

atmos auth validate --stack dev
atmos auth validate --stack dev --component app
atmos auth validate

The component selector requires a stack. See the command reference for selection and validation details.

Get Involved​

Report reproducible configuration problems in Atmos issues, with credentials removed from examples.