docs: replace Leapp and aws-teams references with Atmos Auth

milldr · milldr · commit 9f1b2aa883a8 · 2025-12-11T15:59:31.000-05:00
diff --git a/docs/layers/data/setup.mdx b/docs/layers/data/setup.mdx
@@ -25,7 +25,7 @@ In order to deploy Data layer components, Networking must be fully deployed and
 All deployment steps below assume that the environment has been successfully set up with the following steps.
 
 <Steps>
-  1. Sign into AWS via Leapp
+  1. Sign into AWS via [Atmos Auth](/layers/identity/how-to-log-into-aws/)
   2. Connect to the VPN
   3. Open Geodesic
 </Steps>
diff --git a/docs/layers/ecs/deploy-clusters.mdx b/docs/layers/ecs/deploy-clusters.mdx
@@ -26,7 +26,7 @@ In order to deploy ECS, Networking must be fully deployed and functional. In par
 All deployment steps below assume that the environment has been successfully set up with the following steps.
 
 <Steps>
-  1. Sign into AWS via Leapp
+  1. Sign into AWS via [Atmos Auth](/layers/identity/how-to-log-into-aws/)
   1. Connect to the VPN
   1. Open Geodesic
 </Steps>
diff --git a/docs/layers/eks/deploy-clusters.mdx b/docs/layers/eks/deploy-clusters.mdx
@@ -33,7 +33,7 @@ must have a working VPN connection to the targeted account. See [the network doc
 All deployment steps below assume that the environment has been successfully set up with the following steps.
 
 <Steps>
-1. Sign into AWS via Leapp
+1. Sign into AWS via [Atmos Auth](/layers/identity/how-to-log-into-aws/)
 1. Connect to the VPN
 1. Open Geodesic
 </Steps>
diff --git a/docs/layers/foundation.mdx b/docs/layers/foundation.mdx
@@ -52,7 +52,7 @@ import ReactPlayer from 'react-player';
   <Step>
     ## <StepNumber/> Rollout Identity & Authentication
 
-    Learn how Cloud Posse sets up fine-grained access control for an entire organization using IAM roles, AWS SAML, and AWS IAM Identity Center (SSO). It addresses the challenges of using various login methods and tools and introduces a solution involving Teams and Team Roles to manage access across multiple AWS accounts. This approach ensures precise control, easy role switching, and compatibility with different identity providers. Additionally, we provide a solution optimized for cross-account Terraform access, programmatic access for GitHub OIDC, and a user-friendly login experience with AWS Identity Center (AWS SSO), using tools like Leapp to facilitate seamless authentication and access management.
+    Learn how Cloud Posse sets up fine-grained access control for an entire organization using Permission Sets, IAM roles, and AWS IAM Identity Center (SSO). It addresses the challenges of managing access across multiple AWS accounts with a solution that ensures precise control, easy role switching, and compatibility with different identity providers. This approach provides seamless authentication via Atmos Auth for CLI access, programmatic access for GitHub Actions via OIDC, and a user-friendly login experience with AWS Identity Center.
 
     <figure>
       <ReactPlayer controls url="https://docs.cloudposse.com/assets/refarch/handoffs/identity-and-authentication.mp4" />
diff --git a/docs/layers/security-and-compliance/faq.mdx b/docs/layers/security-and-compliance/faq.mdx
@@ -106,4 +106,4 @@ console for the `root` account within the given Organization, go to Security Hub
 │   42: resource "aws_config_config_rule" "rules" {│
 ```
 
-A: The `support` role may not be deployed into the given account. Check `aws-team-roles` for the `support` role.
+A: The `support` role may not be deployed into the given account. Check your IAM role configuration for the `support` role.
diff --git a/docs/layers/security-and-compliance/setup.mdx b/docs/layers/security-and-compliance/setup.mdx
@@ -118,8 +118,7 @@ The following steps are required to set up Security and Compliance in your AWS O
     [CIS Benchmark 1.20](https://docs.aws.amazon.com/securityhub/latest/userguide/securityhub-cis-controls.html#securityhub-cis-controls-1.20)
     and [IAM.18](https://docs.aws.amazon.com/securityhub/latest/userguide/iam-controls.html#iam-18).
 
-    These roles are managed from the [Identity Workflow](/layers/identity/deploy/)
-    using `aws-teams` and `aws-team-roles` components.
+    These roles are managed from the [Identity layer](/layers/identity/).
   </Step>
 </Steps>
 
diff --git a/docs/layers/software-delivery/eks-argocd/setup.mdx b/docs/layers/software-delivery/eks-argocd/setup.mdx
@@ -30,7 +30,7 @@ All deployment steps below assume that the environment has been successfully set
 ### Authentication
 
 <Steps>
-  1. Sign into AWS via Leapp
+  1. Sign into AWS via [Atmos Auth](/layers/identity/how-to-log-into-aws/)
   1. Connect to the VPN
   1. Open Geodesic
 </Steps>
