AWS b2bi documentation change
Summary
Updated VPC interface endpoint documentation to support dualstack DNS names and clarify Regional DNS endpoints
Security assessment
The change improves network configuration documentation but doesn't address security vulnerabilities or introduce new security features. Dualstack support relates to IPv6 compatibility rather than security.
Diff
diff --git a/b2bi/latest/userguide/vpc-interface-endpoints.md b/b2bi/latest/userguide/vpc-interface-endpoints.md index 6b0a670c9..5202781f5 100644 --- a//b2bi/latest/userguide/vpc-interface-endpoints.md +++ b//b2bi/latest/userguide/vpc-interface-endpoints.md @@ -27 +27 @@ You can create an interface endpoint for AWS B2B Data Interchange using either t -Create an interface endpoint for AWS B2B Data Interchange using the following service name: +Create an interface endpoint for AWS B2B Data Interchange using either of the following service names: @@ -32 +32 @@ Create an interface endpoint for AWS B2B Data Interchange using the following se -If you enable private DNS for the interface endpoint, you can make API requests to AWS B2B Data Interchange using its default Regional DNS name. For example, `b2bi.us-east-1.amazonaws.com`. +If you enable private DNS for the interface endpoint, you can make dualstack API requests to AWS B2B Data Interchange using either Regional DNS name. For example, `b2bi.us-east-1.amazonaws.com` or `b2bi.us-east-1.api.aws`.