AWS Security ChangesHomeSearch

AWS batch documentation change

Service: batch · 2025-04-11 · Documentation low

File: batch/latest/userguide/getting-started-eks-privateclusters.md

Summary

Minor grammatical and formatting corrections including hyphen removal in 'fully-private' to 'fully private', 'route-tables' to 'route tables', and 'job-definition' to 'job definition'

Security assessment

Changes are typo fixes and grammatical improvements without any security context or references to vulnerabilities

Diff

diff --git a/batch/latest/userguide/getting-started-eks-privateclusters.md b/batch/latest/userguide/getting-started-eks-privateclusters.md
index 9a1414888..7a83f016f 100644
--- a//batch/latest/userguide/getting-started-eks-privateclusters.md
+++ b//batch/latest/userguide/getting-started-eks-privateclusters.md
@@ -11 +11 @@ AWS Batch is a managed service that orchestrates batch workloads in your Amazon
-[Amazon EKS private only clusters](https://docs.aws.amazon.com/eks/latest/userguide/cluster-endpoint.html#private-access) have no inbound/outbound internet access, and only have private subnets. Amazon VPC endpoints are used to enable private access to other AWS services. `eksctl` supports creating fully-private clusters using a pre-existing Amazon VPC and subnets. ``eksctl`` also creates Amazon VPC endpoints in the supplied Amazon VPC and modifies route tables for the supplied subnets.
+[Amazon EKS private only clusters](https://docs.aws.amazon.com/eks/latest/userguide/cluster-endpoint.html#private-access) have no inbound/outbound internet access, and only have private subnets. Amazon VPC endpoints are used to enable private access to other AWS services. `eksctl` supports creating fully private clusters using a pre-existing Amazon VPC and subnets. ``eksctl`` also creates Amazon VPC endpoints in the supplied Amazon VPC and modifies route tables for the supplied subnets.
@@ -40 +40 @@ You can optionally create a [pull through cache rule](https://docs.aws.amazon.co
-Before starting this tutorial, you must install and configure the following tools and resources that you need to create and manage both AWS Batch and Amazon EKS resources. You also need to create all the necessary resources including VPC, subnets, route-tables, VPC endpoints, and Amazon EKS cluster. You need to use the AWS CLI.
+Before starting this tutorial, you must install and configure the following tools and resources that you need to create and manage both AWS Batch and Amazon EKS resources. You also need to create all the necessary resources including VPC, subnets, route tables, VPC endpoints, and Amazon EKS cluster. You need to use the AWS CLI.
@@ -56 +56 @@ After installing the AWS CLI, we recommend that you configure it. For more infor
-AWS Batch doesn't provide managed-node orchestration for CoreDNS or other deployment pods. If you need CoreDNS, see [Adding the CoreDNS Amazon EKS add-on](https://docs.aws.amazon.com/eks/latest/userguide/managing-coredns.html#adding-coredns-eks-add-on) in the __Amazon EKS User Guide__. Or, use `eksctl create cluster create` to create the cluster, it includes CoreDNS by default.
+AWS Batch doesn't provide managed node orchestration for CoreDNS or other deployment pods. If you need CoreDNS, see [Adding the CoreDNS Amazon EKS add-on](https://docs.aws.amazon.com/eks/latest/userguide/managing-coredns.html#adding-coredns-eks-add-on) in the __Amazon EKS User Guide__. Or, use `eksctl create cluster create` to create the cluster, it includes CoreDNS by default.
@@ -316 +316 @@ Jobs submitted to this new job queue are run as pods on AWS Batch managed nodes
-In the image field of the job definition, instead of providing a link to image in a public ECR repository, provide the link to the image stored in our private ECR repository. See the following sample job-definition:
+In the image field of the job definition, instead of providing a link to image in a public ECR repository, provide the link to the image stored in our private ECR repository. See the following sample job definition:
@@ -423 +423 @@ If nodes launched by AWS Batch don't have access to the Amazon ECR repository (o
-For other common troubleshooting scenarios, see [Troubleshooting AWS Batch](batch/latest/userguide/troubleshooting.html#batch-eks-troubleshooting). For troubleshooting bases on pod-status, see [_How do I troubleshoot the pod status in Amazon EKS?_](https://repost.aws/knowledge-center/eks-pod-status-troubleshooting).
+For other common troubleshooting scenarios, see [Troubleshooting AWS Batch](batch/latest/userguide/troubleshooting.html#batch-eks-troubleshooting). For troubleshooting based on pod status, see [_How do I troubleshoot the pod status in Amazon EKS?_](https://repost.aws/knowledge-center/eks-pod-status-troubleshooting).