AWS eks documentation change
Summary
Fixed typo: changed 'gudes' to 'guides' in Fargate profile setup instructions for Windows nodes.
Security assessment
This is a simple spelling correction in documentation about deploying sample applications. The change has no security implications as it doesn't address vulnerabilities, modify security configurations, or add security documentation. It only fixes a typo in general deployment instructions.
Diff
diff --git a/eks/latest/userguide/sample-deployment-win.md b/eks/latest/userguide/sample-deployment-win.md index 616ec0a17..761e9ec06 100644 --- a//eks/latest/userguide/sample-deployment-win.md +++ b//eks/latest/userguide/sample-deployment-win.md @@ -23 +23 @@ In this topic, you deploy a sample application to your cluster on Windows nodes. - * If you plan to deploy your sample workload to Fargate, then you must have an existing [Fargate profile](./fargate-profile.html) that includes the same namespace created in this tutorial, which is `eks-sample-app`, unless you change the name. If you created a cluster with one of the gudes in [Get started with Amazon EKS](./getting-started.html), then you’ll have to create a new profile, or add the namespace to your existing profile, because the profile created in the getting started guides doesn’t specify the namespace used in this tutorial. Your VPC must also have at least one private subnet. + * If you plan to deploy your sample workload to Fargate, then you must have an existing [Fargate profile](./fargate-profile.html) that includes the same namespace created in this tutorial, which is `eks-sample-app`, unless you change the name. If you created a cluster with one of the guides in [Get started with Amazon EKS](./getting-started.html), then you’ll have to create a new profile, or add the namespace to your existing profile, because the profile created in the getting started guides doesn’t specify the namespace used in this tutorial. Your VPC must also have at least one private subnet.