AWS r53recovery documentation change
Summary
Updated terminology from 'AWS Direct Connect' to 'Direct Connect' in PrivateLink documentation
Security assessment
Change only modifies product name formatting without altering security context. No evidence of addressing vulnerabilities or changing security guidance.
Diff
diff --git a/r53recovery/latest/dg/vpc-interface-endpoints.md b/r53recovery/latest/dg/vpc-interface-endpoints.md index a2b4c0a2a..23877aa81 100644 --- a//r53recovery/latest/dg/vpc-interface-endpoints.md +++ b//r53recovery/latest/dg/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 Amazon Application Recovery Controller (ARC) zonal shift. You can access ARC zonal shift 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 ARC zonal shift. +You can use AWS PrivateLink to create a private connection between your VPC and Amazon Application Recovery Controller (ARC) zonal shift. You can access ARC zonal shift 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 ARC zonal shift.