AWS batch documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' for terminology consistency
Security assessment
Minor branding adjustment with no impact on security content. The PrivateLink configuration guidance remains unchanged.
Diff
diff --git a/batch/latest/userguide/vpc-interface-endpoints.md b/batch/latest/userguide/vpc-interface-endpoints.md index 737bf0554..d19d08427 100644 --- a//batch/latest/userguide/vpc-interface-endpoints.md +++ b//batch/latest/userguide/vpc-interface-endpoints.md @@ -7 +7 @@ -You can use AWS PrivateLink to create a private connection between your VPC and AWS Batch. You can access AWS Batch as if it were in your VPC, without the use of an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. Instances in your VPC don't need public IP addresses to access AWS Batch. +You can use AWS PrivateLink to create a private connection between your VPC and AWS Batch. You can access AWS Batch as if it were in your VPC, without the use of an internet gateway, NAT device, VPN connection, or Direct Connect connection. Instances in your VPC don't need public IP addresses to access AWS Batch.