AWS eks documentation change
Summary
Fixed broken hyperlink reference for 'Create add-on (AWS Console)' documentation
Security assessment
This change only addresses a documentation link formatting issue. While the content relates to IAM roles (a security construct), the modification itself doesn't introduce new security guidance or address a specific vulnerability - it merely fixes navigation to existing documentation.
Diff
diff --git a/eks/latest/userguide/create-cluster.md b/eks/latest/userguide/create-cluster.md index 46e7a5ba6..0a8f909a5 100644 --- a//eks/latest/userguide/create-cluster.md +++ b//eks/latest/userguide/create-cluster.md @@ -239 +239 @@ Some add-ons, such as Amazon VPC CNI, CoreDNS, and kube-proxy, are installed by -For add-ons that support EKS Pod Identities, you can use the console to automatically generate the role with the name, AWS managed policy, and trust policy prepopulated specifically for the add-on. You can re-use existing roles or create new roles for supported add-ons. For the steps to use the console to create roles for add-ons that support EKS Pod Identities, see [](./.html#_create_add_on_console). If an add-on does not support EKS Pod Identity, a message displays with instructions to use the wizard to create the IAM roles for service accounts (IRSA) after the cluster is created. +For add-ons that support EKS Pod Identities, you can use the console to automatically generate the role with the name, AWS managed policy, and trust policy prepopulated specifically for the add-on. You can re-use existing roles or create new roles for supported add-ons. For the steps to use the console to create roles for add-ons that support EKS Pod Identities, see [Create add-on (AWS Console)](./creating-an-add-on.html#create_add_on_console). If an add-on does not support EKS Pod Identity, a message displays with instructions to use the wizard to create the IAM roles for service accounts (IRSA) after the cluster is created.