AWS eks documentation change
Summary
Updated ALB configuration steps: Added explicit workload creation step, renumbered subsequent steps, added concrete examples with service-2048, specified YAML filenames, and expanded cleanup instructions
Security assessment
The changes are procedural improvements adding implementation details and examples. While the documentation mentions security-related configurations like SSL/TLS certificates, these were already present in previous steps. No specific vulnerabilities or new security controls are introduced.
Diff
diff --git a/eks/latest/userguide/auto-configure-alb.md b/eks/latest/userguide/auto-configure-alb.md index ccbfeeb22..d057b2a29 100644 --- a//eks/latest/userguide/auto-configure-alb.md +++ b//eks/latest/userguide/auto-configure-alb.md @@ -5 +5 @@ -PrerequisitesStep 1: Create IngressClassParamsStep 2: Create IngressClassStep 3: Create IngressStep 4: Check StatusStep 5: CleanupIngressClassParams ReferenceConsiderations +PrerequisitesStep 1: Create a workloadStep 2: Create IngressClassParamsStep 3: Create IngressClassStep 4: Create IngressStep 5: Check StatusStep 6: CleanupIngressClassParams ReferenceConsiderations @@ -21 +21 @@ EKS Auto Mode creates and configures Application Load Balancers (ALBs). For exam - 1. Create an `IngressClassParams` resource, specifying AWS specific configuration values such as the certificate to use for SSL/TLS and VPC Subnets. + 1. Create a workload that you want to expose to the internet. @@ -23 +23 @@ EKS Auto Mode creates and configures Application Load Balancers (ALBs). For exam - 2. Create an `IngressClass` resource, specifying that EKS Auto Mode will be the controller for the resource. + 2. Create an `IngressClassParams` resource, specifying AWS specific configuration values such as the certificate to use for SSL/TLS and VPC Subnets. @@ -25 +25 @@ EKS Auto Mode creates and configures Application Load Balancers (ALBs). For exam - 3. Create an `Ingress` resource that associates a HTTP path and port with a cluster workload. + 3. Create an `IngressClass` resource, specifying that EKS Auto Mode will be the controller for the resource. @@ -27 +27 @@ EKS Auto Mode creates and configures Application Load Balancers (ALBs). For exam - 4. EKS Auto Mode will create an Application Load Balancer that points to the workload specified in the `Ingress` resource, using the load balancer configuration specified in the `IngressClassParams` resource. + 4. Create an `Ingress` resource that associates a HTTP path and port with a cluster workload. @@ -31,0 +32,2 @@ EKS Auto Mode creates and configures Application Load Balancers (ALBs). For exam +EKS Auto Mode will create an Application Load Balancer that points to the workload specified in the `Ingress` resource, using the load balancer configuration specified in the `IngressClassParams` resource. + @@ -51 +53,3 @@ Learn how to [Tag subnets for EKS Auto Mode](./tag-subnets-auto.html). -## Step 1: Create IngressClassParams +## Step 1: Create a workload + +Create a workload that you want to expose to the internet. This can be any Kubernetes resource that serves HTTP traffic, such as a Deployment or a Service. For this example, we use a simple HTTP service called `service-2048` that serves HTTP traffic on port 80. @@ -53 +57 @@ Learn how to [Tag subnets for EKS Auto Mode](./tag-subnets-auto.html). -Create an `IngressClassParams` object to specify AWS specific configuration options for the Application Load Balancer. Use the reference below to update the sample YAML file. +## Step 2: Create IngressClassParams @@ -55 +59 @@ Create an `IngressClassParams` object to specify AWS specific configuration opti -Note the name you set for the `IngressClassParams` resource, you will need it in the next step. +Create an `IngressClassParams` object to specify AWS specific configuration options for the Application Load Balancer. In this example, we create an `IngressClassParams` resource named `alb` (which you will use in the next step) that specifies the load balancer scheme as `internet-facing` in a file called `alb-ingressclassparams.yaml`. @@ -65 +69,2 @@ Note the name you set for the `IngressClassParams` resource, you will need it in -## Step 2: Create IngressClass +Apply the configuration to your cluster: + @@ -67 +72,5 @@ Note the name you set for the `IngressClassParams` resource, you will need it in -Create an `IngressClass` that references the AWS specific configuration values set in the `IngressClassParams` resource. Note the name of the `IngressClass` . In this example, both the `IngressClass` and `IngressClassParams` are named `alb`. + kubectl apply -f alb-ingressclassparams.yaml + +## Step 3: Create IngressClass + +Create an `IngressClass` that references the AWS specific configuration values set in the `IngressClassParams` resource in a file named `alb-ingressclass.yaml`. Note the name of the `IngressClass`. In this example, both the `IngressClass` and `IngressClassParams` are named `alb`. @@ -91 +100,2 @@ For more information on configuration options, see IngressClassParams Reference. -## Step 3: Create Ingress +Apply the configuration to your cluster: + @@ -93 +103,5 @@ For more information on configuration options, see IngressClassParams Reference. -Create an `Ingress` resource. The purpose of this resource is to associate paths and ports on the Application Load Balancer with workloads in your cluster. + kubectl apply -f alb-ingressclass.yaml + +## Step 4: Create Ingress + +Create an `Ingress` resource in a file named `alb-ingress.yaml`. The purpose of this resource is to associate paths and ports on the Application Load Balancer with workloads in your cluster. For this example, we create an `Ingress` resource named `2048-ingress` that routes traffic to a service named `service-2048` on port 80. @@ -113 +127 @@ For more information about configuring this resource, see [Ingress](https://kube - name: <your-service> + name: service-2048 @@ -117 +131,6 @@ For more information about configuring this resource, see [Ingress](https://kube -## Step 4: Check Status +Apply the configuration to your cluster: + + + kubectl apply -f alb-ingress.yaml + +## Step 5: Check Status @@ -121 +140 @@ Use `kubectl` to find the status of the `Ingress`. It can take a few minutes for -Use the name of the `Ingress` resource you set in the previous step. +Use the name of the `Ingress` resource you set in the previous step. For example: @@ -124 +143 @@ Use the name of the `Ingress` resource you set in the previous step. - kubectl get ingress <ingress-name> + kubectl get ingress 2048-ingress @@ -129 +148 @@ Once the resource is ready, retrieve the domain name of the load balancer. - kubectl get ingress api-ingress -o jsonpath='{.status.loadBalancer.ingress[0].hostname}' + kubectl get ingress 2048-ingress -o jsonpath='{.status.loadBalancer.ingress[0].hostname}' @@ -133 +152 @@ To view the service in a web browser, review the port and path specified in the -## Step 5: Cleanup +## Step 6: Cleanup @@ -138 +157,3 @@ To clean up the load balancer, use the following command: - kubectl delete ingress <ingress-name> + kubectl delete ingress 2048-ingress + kubectl delete ingressclass alb + kubectl delete ingressclassparams alb