Skip to content

Commit e4685cc

Browse files
milldrclaude
andcommitted
docs: add Identity layer CTA in account deployment flow
Add call-to-action after account ID placeholder updates directing users to deploy the Identity layer before continuing with account settings, CloudTrail, and ECR. Includes a note explaining this is a temporary measure while documentation flow and SuperAdmin profile are being improved. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
1 parent 1c860b4 commit e4685cc

1 file changed

Lines changed: 9 additions & 0 deletions

File tree

docs/layers/accounts/deploy-accounts.mdx

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -155,6 +155,15 @@ This guide walks through deploying AWS accounts using `atmos` workflows. Before
155155
:::
156156

157157
As you continue through the setup process, keep an eye out for other placeholder values in your stack configurations and replace them with actual values as needed.
158+
159+
:::note Stopgap: Deploy the Identity Layer Before Continuing
160+
Before proceeding with the remaining account steps, you need to deploy the Identity layer. The Identity layer provisions permission sets with AWS Identity Center that allow you to access each member account, which is required for deploying account settings, CloudTrail, and ECR. We're working on improving this documentation flow and the SuperAdmin profile, but for now, the Identity layer must be deployed at this point.
161+
:::
162+
163+
<ActionCard title="Deploy the Identity Layer">
164+
Deploy the Identity layer to provision permission sets for accessing each member account. Return here to finish account settings, CloudTrail, and ECR after the Identity layer is deployed.
165+
<PrimaryCTA to="/layers/identity">Deploy Identity Layer</PrimaryCTA>
166+
</ActionCard>
158167
</Step>
159168

160169
<Step>

0 commit comments

Comments
 (0)