AWS b2bi documentation change
Summary
Updated 'AWS Direct Connect' to 'Direct Connect' in VPC interface endpoint documentation.
Security assessment
Terminology standardization without security impact. The PrivateLink security benefits described remain unchanged.
Diff
diff --git a/b2bi/latest/userguide/vpc-interface-endpoints.md b/b2bi/latest/userguide/vpc-interface-endpoints.md index 9d1015319..bc1056ab0 100644 --- a//b2bi/latest/userguide/vpc-interface-endpoints.md +++ b//b2bi/latest/userguide/vpc-interface-endpoints.md @@ -9 +9 @@ ConsiderationsCreate an interface endpointCreate an endpoint policy -You can use AWS PrivateLink to create a private connection between your VPC and AWS B2B Data Interchange. You can access AWS B2B Data Interchange 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 B2B Data Interchange. +You can use AWS PrivateLink to create a private connection between your VPC and AWS B2B Data Interchange. You can access AWS B2B Data Interchange 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 B2B Data Interchange.