From 5f2743a292828a17ea1eccb16a48007159177dcb Mon Sep 17 00:00:00 2001 From: Diego OJ Date: Mon, 19 Feb 2024 17:26:30 -0300 Subject: [PATCH] Fix credentials links --- docs/user-guide/ref-architecture-aws/credentials.md | 4 ++-- docs/user-guide/ref-architecture-eks/credentials.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/user-guide/ref-architecture-aws/credentials.md b/docs/user-guide/ref-architecture-aws/credentials.md index d4d81050..2b7af22b 100644 --- a/docs/user-guide/ref-architecture-aws/credentials.md +++ b/docs/user-guide/ref-architecture-aws/credentials.md @@ -3,8 +3,8 @@ ## Overview Currently the following two methods are supported: -1. [x] **AWS IAM:** this is essentially using on-disk, permanent programmatic credentials that are tied to a given IAM User. This method can optionally support MFA which is highly recommended since using permanent credentials is discouraged, so at least with MFA you can counter-balance that. [Keep reading...](./features/sso/configuration.md) -2. [x] **AWS IAM Identity Center (formerly known as AWS SSO):** this one is more recent and it's the method recommeded by AWS since it uses roles (managed by AWS) which in turn enforce the usage of temporary credentials. [Keep reading...](./features/identities/identities.md) +1. [x] **AWS IAM:** this is essentially using on-disk, permanent programmatic credentials that are tied to a given IAM User. This method can optionally support MFA which is highly recommended since using permanent credentials is discouraged, so at least with MFA you can counter-balance that. [Keep reading...](./features/identities/identities.md) +2. [x] **AWS IAM Identity Center (formerly known as AWS SSO):** this one is more recent and it's the method recommeded by AWS since it uses roles (managed by AWS) which in turn enforce the usage of temporary credentials. [Keep reading...](./features/sso/configuration.md) ## Next Steps If you are planning to choose SSO (highly recommended), check out [this section](./features/sso/overview.md). diff --git a/docs/user-guide/ref-architecture-eks/credentials.md b/docs/user-guide/ref-architecture-eks/credentials.md index 08db4d07..a2c7007c 100644 --- a/docs/user-guide/ref-architecture-eks/credentials.md +++ b/docs/user-guide/ref-architecture-eks/credentials.md @@ -1,7 +1,7 @@ # Credentials ## Overview -Access to EKS is usually achieved via IAM roles. These could be either custom IAM roles that you define, or SSO roles that AWS takes care of creating and managing. +Access to EKS is usually achieved via IAM roles. These could be either [custom IAM](/user-guide/ref-architecture-aws/features/identities/identities) roles that you define, or [SSO roles](/user-guide/ref-architecture-aws/features/sso/overview) that AWS takes care of creating and managing. ## Configuration Granting different kinds of access to IAM roles can be done as shown [here](https://github.com/binbashar/le-tf-infra-aws/blob/master/apps-devstg/us-east-1/k8s-eks/cluster/locals.tf#L33-L60) where you can define classic IAM roles or SSO roles. Note however that, since the latter are managed by AWS SSO, they could change if they are recreated or reassigned.