AWS migrationhub-orchestrator documentation change
Summary
Updated 'AWS Direct Connect' to 'Direct Connect' for service name consistency
Security assessment
This is a minor terminology update without substantive changes to security guidance. The documentation continues to describe VPC interface endpoints and PrivateLink security benefits without introducing new security features or addressing vulnerabilities.
Diff
diff --git a/migrationhub-orchestrator/latest/userguide/vpc-interface-endpoints.md b/migrationhub-orchestrator/latest/userguide/vpc-interface-endpoints.md index af42fe7a7..19ae723c8 100644 --- a//migrationhub-orchestrator/latest/userguide/vpc-interface-endpoints.md +++ b//migrationhub-orchestrator/latest/userguide/vpc-interface-endpoints.md @@ -11 +11 @@ AWS Migration Hub is no longer open to new customers as of November 7, 2025. For -You can establish a private connection between your VPC and Migration Hub Orchestrator by creating an _interface VPC endpoint_. Interface endpoints are powered by AWS PrivateLink. With AWS PrivateLink, you can privately access Migration Hub Orchestrator API operations without an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. Instances in your VPC don't need public IP addresses to communicate with Migration Hub Orchestrator API operations. Traffic between your VPC and Migration Hub Orchestrator stays within the Amazon network. +You can establish a private connection between your VPC and Migration Hub Orchestrator by creating an _interface VPC endpoint_. Interface endpoints are powered by AWS PrivateLink. With AWS PrivateLink, you can privately access Migration Hub Orchestrator API operations without an internet gateway, NAT device, VPN connection, or Direct Connect connection. Instances in your VPC don't need public IP addresses to communicate with Migration Hub Orchestrator API operations. Traffic between your VPC and Migration Hub Orchestrator stays within the Amazon network.