You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: blog/2026-02-25-nextgen-component-migration.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -141,7 +141,7 @@ Before using Atmos Auth, ensure you have:
141
141
1.**Atmos >= v1.155.0** — Atmos Auth requires a recent version of the Atmos CLI. Run `atmos version` to check.
142
142
1.**AWS IAM Identity Center (SSO)** — For human users, Atmos Auth profiles authenticate via AWS SSO. You need IAM Identity Center configured in your `core-root` account with Permission Sets for Terraform access.
143
143
1.**IAM roles for CI/CD** — For machine users, deploy the `iam-role` component with GitHub OIDC (or your CI provider's equivalent) in each target account.
144
-
1.**Atmos Auth profiles configured** — Define profiles in your `atmos.yaml` that map to SSO Permission Sets or IAM roles. See [Atmos Auth](https://atmos.tools/cli/auth) for the configuration reference.
144
+
1.**Atmos Auth profiles configured** — Define profiles in your `atmos.yaml` that map to SSO Permission Sets or IAM roles. See [Atmos Auth](https://atmos.tools/cli/configuration/auth) for the configuration reference.
145
145
</Steps>
146
146
147
147
## How Provider Overrides Work
@@ -189,7 +189,7 @@ Configure Atmos Auth profiles in your `atmos.yaml`. This tells Atmos how to auth
189
189
atmos auth login
190
190
```
191
191
192
-
See [Atmos Auth](https://atmos.tools/cli/auth) for configuration details and the [prerequisites](#atmos-auth-prerequisites) section above.
192
+
See [Atmos Auth](https://atmos.tools/cli/configuration/auth) for configuration details and the [prerequisites](#atmos-auth-prerequisites) section above.
193
193
194
194
### 2. Add the Static Account Map
195
195
@@ -503,7 +503,7 @@ The net result: fewer components to manage, simpler authentication, no deploy or
503
503
<Steps>
504
504
1. [Deprecating Account-Map](/blog/deprecate-account-map/) — The full deprecation announcement
505
505
1. [Migrate from Account-Map](/layers/project/tutorials/migrate-from-account-map/) — Detailed step-by-step migration guide
Copy file name to clipboardExpand all lines: docs/layers/accounts/tutorials/legacy-account-map.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ import Intro from '@site/src/components/Intro';
8
8
importStepsfrom'@site/src/components/Steps';
9
9
10
10
<Intro>
11
-
The `account-map` component has been deprecated. The reference architecture now uses [Atmos Auth](https://atmos.tools/cli/auth) for authentication and [Atmos Functions](https://atmos.tools/core-concepts/stacks/templates/functions) for dynamic values, eliminating the need for `account-map` entirely.
11
+
The `account-map` component has been deprecated. The reference architecture now uses [Atmos Auth](https://atmos.tools/cli/configuration/auth) for authentication and [Atmos Functions](https://atmos.tools/core-concepts/stacks/templates/functions) for dynamic values, eliminating the need for `account-map` entirely.
12
12
</Intro>
13
13
14
14
## Why Deprecate Account Map?
@@ -55,7 +55,7 @@ If you have an existing deployment using the `account-map` component, see the mi
0 commit comments