AWS batch documentation change
Summary
Corrected 'Internode' to 'Inter-node' for grammatical consistency
Security assessment
Change is a grammatical correction with no security implications
Diff
diff --git a/batch/latest/userguide/mnp-ce.md b/batch/latest/userguide/mnp-ce.md index 2854513c4..cdb992594 100644 --- a//batch/latest/userguide/mnp-ce.md +++ b//batch/latest/userguide/mnp-ce.md @@ -19 +19 @@ There are several things to consider when configuring compute environments to ru - * The `awsvpc` network mode doesn't provide the elastic network interfaces for multi-node parallel jobs with public IP addresses. To access the internet, your compute resources must be launched in a private subnet that is configured to use a NAT gateway. For more information, see [NAT Gateways](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-nat-gateway.html) in the _Amazon VPC User Guide_. Internode communication must use the private IP address or DNS hostname for the node. Multi-node parallel jobs that run on compute resources within public subnets don't have outbound network access. To create a VPC with private subnets and a NAT gateway, see [Create a virtual private cloud ](./create-public-private-vpc.html). + * The `awsvpc` network mode doesn't provide the elastic network interfaces for multi-node parallel jobs with public IP addresses. To access the internet, your compute resources must be launched in a private subnet that is configured to use a NAT gateway. For more information, see [NAT Gateways](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-nat-gateway.html) in the _Amazon VPC User Guide_. Inter-node communication must use the private IP address or DNS hostname for the node. Multi-node parallel jobs that run on compute resources within public subnets don't have outbound network access. To create a VPC with private subnets and a NAT gateway, see [Create a virtual private cloud ](./create-public-private-vpc.html).