AWS eks documentation change
Summary
Updated documentation for creating Argo CD capability via CLI, including corrections to region placeholders, command syntax, and improved clarity in instructions.
Security assessment
Changes are grammatical improvements and placeholder corrections. No security vulnerabilities or security features are mentioned. The IAM role permissions note about Secrets Manager/CodeConnections existed previously.
Diff
diff --git a/eks/latest/userguide/argocd-create-cli.md b/eks/latest/userguide/argocd-create-cli.md index a6a3e171c..1e7942376 100644 --- a//eks/latest/userguide/argocd-create-cli.md +++ b//eks/latest/userguide/argocd-create-cli.md @@ -7 +7 @@ -PrerequisitesStep 1: Create an IAM Capability RoleStep 2: Create the Argo CD capabilityStep 3: Verify the capability is activeStep 4: Verify custom resources are availableNext steps +PrerequisitesStep 1: Create an IAM capability roleStep 2: Create the Argo CD capabilityStep 3: Verify the capability is activeStep 4: Verify custom resources are availableNext steps @@ -15 +15 @@ To contribute to this user guide, choose the **Edit this page on GitHub** link t -This topic describes how to create an Argo CD capability using the AWS CLI. +Create an Argo CD capability on your Amazon EKS cluster using the AWS CLI. This procedure walks you through creating an IAM role, configuring AWS Identity Center integration, and verifying the capability is active. @@ -28 +28 @@ This topic describes how to create an Argo CD capability using the AWS CLI. -## Step 1: Create an IAM Capability Role +## Step 1: Create an IAM capability role @@ -60 +60 @@ Create the IAM role: -If you plan to use the optional integrations with AWS Secrets Manager or AWS CodeConnections, you’ll need to add permissions to the role. For IAM policy examples and configuration guidance, see [Manage application secrets with AWS Secrets Manager](./integration-secrets-manager.html) and [Connect to Git repositories with AWS CodeConnections](./integration-codeconnections.html). +If you plan to use the optional integrations with AWS Secrets Manager or AWS CodeConnections, add permissions to the role. For IAM policy examples and configuration guidance, see [Manage application secrets with AWS Secrets Manager](./integration-secrets-manager.html) and [Connect to Git repositories with AWS CodeConnections](./integration-codeconnections.html). @@ -70 +70 @@ First, set environment variables for your Identity Center configuration: - export IDC_INSTANCE_ARN=$(aws sso-admin list-instances --region [.replaceable]`region` --query 'Instances[0].InstanceArn' --output text) + export IDC_INSTANCE_ARN=$(aws sso-admin list-instances --region region-code --query 'Instances[0].InstanceArn' --output text) @@ -74,3 +74,3 @@ First, set environment variables for your Identity Center configuration: - --region [.replaceable]`region` \ - --identity-store-id $(aws sso-admin list-instances --region [.replaceable]`region` --query 'Instances[0].IdentityStoreId' --output text) \ - --query 'Users[?UserName==`your-username`].UserId' --output text) + --region region-code \ + --identity-store-id $(aws sso-admin list-instances --region region-code --query 'Instances[0].IdentityStoreId' --output text) \ + --query 'Users[?UserName==your-username].UserId' --output text) @@ -81 +81 @@ First, set environment variables for your Identity Center configuration: -Create the capability with Identity Center integration. Replace `region-code` with the AWS Region where your cluster is located and `my-cluster` with your cluster name and `idc-region-code` with the region code where you IAM Identity Center has been configured: +Create the capability with Identity Center integration. Replace `region-code` with the AWS Region where your cluster is located, `my-cluster` with your cluster name, and `idc-region-code` with the region code where your Identity Center instance is located: @@ -107 +107 @@ Create the capability with Identity Center integration. Replace `region-code` wi -The command returns immediately, but the capability takes some time to become active as EKS creates the required capability infrastructure and components. EKS will install the Kubernetes Custom Resource Definitions related to this capability in your cluster as it is being created. +The command returns immediately, but the capability takes some time to become active as EKS creates the required capability infrastructure and components. EKS installs the Kubernetes Custom Resource Definitions (CRDs) in your cluster during capability creation. @@ -134 +134 @@ Wait for the capability to become active. Replace `region-code` with the AWS Reg -The capability is ready when the status shows `ACTIVE`. Don’t continue to the next step until the status is `ACTIVE`. +The capability is ready when the status shows `ACTIVE`. Wait until the status is `ACTIVE` before you continue to the next step.