AWS codepipeline documentation change
Summary
Updated step references, added subnet attachment details, and modified Helm chart configuration instructions
Security assessment
Procedural clarifications for EKS deployment workflow without security implications
Diff
diff --git a/codepipeline/latest/userguide/tutorials-eks-deploy.md index ef1b64d83..a20baaebf 100644 --- a/codepipeline/latest/userguide/tutorials-eks-deploy.md +++ b/codepipeline/latest/userguide/tutorials-eks-deploy.md @@ -35 +35 @@ All of these resources should be created within the same AWS Region. - * You must use an existing CodePipeline service role that you will update with the permissions for this action using Step 4 below. The permissions needed are based on the type of cluster you create. For more information, see [Service role policy permissions](./action-reference-EKS.html#action-reference-EKS-service-role). + * You must use an existing CodePipeline service role that you will update with the permissions for this action using Step 3: Update the CodePipeline service role policy in IAM below. The permissions needed are based on the type of cluster you create. For more information, see [Service role policy permissions](./action-reference-EKS.html#action-reference-EKS-service-role). @@ -148 +148 @@ This step is applicable only if you have created a private cluster. This step is - 1. Attach private subnets only in the EKS cluster under the **Networking** tab. + 1. Attach private subnets only in the EKS cluster under the **Networking** tab. Attach the private subnets captured in the **Determine the private subnets in your VPC** section under Step 1: (Optional) Create a cluster in Amazon EKS. @@ -306 +306 @@ This is the policy that the CodePipeline action uses to talk to Kubernetes. As a -In this step, you create a config file that is appropriate for your action (Kubernetes manifest files or Helm templates) and store the config file in your source repository. Use the appropriate file as follows. For more information, see [https://kubernetes.io/docs/reference/kubectl/quick-reference/](https://kubernetes.io/docs/reference/kubectl/quick-reference/) or [https://helm.sh/docs/topics/charts/](https://helm.sh/docs/topics/charts/). +In this step, you create a config file that is appropriate for your action (Kubernetes manifest files or Helm chart) and store the config file in your source repository. Use the appropriate file for your configuration. For more information, see [https://kubernetes.io/docs/reference/kubectl/quick-reference/](https://kubernetes.io/docs/reference/kubectl/quick-reference/) or [https://helm.sh/docs/topics/charts/](https://helm.sh/docs/topics/charts/). @@ -317 +317 @@ In this step, you create a config file that is appropriate for your action (Kube - 2. Create a new structure in your repository for your helm chart files as shown in the example below. For an example, see https://docs.bitnami.com/kubernetes/faq/administration/understand-helm-chart/. + 2. Create a new structure in your repository for your helm chart files as shown in the example below. @@ -366 +366 @@ Use the CodePipeline wizard to create your pipeline stages and connect your sour - 2. For **Helm chart location** , enter the path and file name for your helm chart files, such as `deployment.yaml`. + 2. In **Helm chart location** , enter the release name, such as `my-release`. For **Helm chart location** , enter the path for your helm chart files, such as `mychart`.