AWS m2 documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in VPC interface endpoints documentation
Security assessment
The change is a minor terminology update (branding consistency) without altering security implications of PrivateLink usage. No evidence of addressing vulnerabilities or security weaknesses.
Diff
diff --git a/m2/latest/userguide/vpc-interface-endpoints.md b/m2/latest/userguide/vpc-interface-endpoints.md index c8bba156a..8b46bff6b 100644 --- a//m2/latest/userguide/vpc-interface-endpoints.md +++ b//m2/latest/userguide/vpc-interface-endpoints.md @@ -11 +11 @@ AWS Mainframe Modernization Service (Managed Runtime Environment experience) is -You can use AWS PrivateLink to create a private connection between your VPC and AWS Mainframe Modernization. You can access AWS Mainframe Modernization 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 Mainframe Modernization. +You can use AWS PrivateLink to create a private connection between your VPC and AWS Mainframe Modernization. You can access AWS Mainframe Modernization 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 Mainframe Modernization.