AWS migrationhub-refactor-spaces documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in VPC interface endpoints documentation
Security assessment
The change appears to be a terminology update (brand name shortening) rather than addressing security functionality. No security implications identified in the context of PrivateLink configuration.
Diff
diff --git a/migrationhub-refactor-spaces/latest/userguide/vpc-interface-endpoints.md b/migrationhub-refactor-spaces/latest/userguide/vpc-interface-endpoints.md index cca720311..3cc04f04e 100644 --- a//migrationhub-refactor-spaces/latest/userguide/vpc-interface-endpoints.md +++ b//migrationhub-refactor-spaces/latest/userguide/vpc-interface-endpoints.md @@ -11 +11 @@ AWS Migration Hub Refactor Spaces is no longer open to new customers as of Novem -You can use AWS PrivateLink to create a private connection between your VPC and AWS Migration Hub Refactor Spaces (Refactor Spaces). You can access Refactor Spaces 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 Refactor Spaces. +You can use AWS PrivateLink to create a private connection between your VPC and AWS Migration Hub Refactor Spaces (Refactor Spaces). You can access Refactor Spaces 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 Refactor Spaces.