AWS managed-flink documentation change
Summary
Replaced 'AWS Direct Connect' with 'Direct Connect' in VPC endpoint explanation.
Security assessment
Editorial update to service naming. No impact on VPC security architecture or private connectivity principles.
Diff
diff --git a/managed-flink/latest/java/vpc.md b/managed-flink/latest/java/vpc.md index 344652764..1fb54dc20 100644 --- a//managed-flink/latest/java/vpc.md +++ b//managed-flink/latest/java/vpc.md @@ -42 +42 @@ The following are the key concepts for VPCs: - * A _VPC endpoint_ enables you to privately connect your VPC to supported AWS services and VPC endpoint services powered by PrivateLink without requiring an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. Instances in your VPC do not require public IP addresses to communicate with resources in the service. Traffic between your VPC and the other service does not leave the Amazon network. + * A _VPC endpoint_ enables you to privately connect your VPC to supported AWS services and VPC endpoint services powered by PrivateLink without requiring an internet gateway, NAT device, VPN connection, or Direct Connect connection. Instances in your VPC do not require public IP addresses to communicate with resources in the service. Traffic between your VPC and the other service does not leave the Amazon network.