AWS healthlake documentation change
Summary
Updated terminology from 'AWS Direct Connect' to 'Direct Connect' in VPC endpoint documentation
Security assessment
The change is a minor terminology update (branding consistency) and does not introduce or modify security-related content. No evidence of addressing vulnerabilities or security features.
Diff
diff --git a/healthlake/latest/devguide/vpc-endpoints.md b/healthlake/latest/devguide/vpc-endpoints.md index b1cc61f31..5b45098ac 100644 --- a//healthlake/latest/devguide/vpc-endpoints.md +++ b//healthlake/latest/devguide/vpc-endpoints.md @@ -9 +9 @@ Considerations for HealthLake VPC endpointsCreating an interface VPC endpoint fo -You can establish a private connection between your VPC and AWS HealthLake by creating an _interface VPC endpoint_. Interface VPC endpoints are powered by [AWS PrivateLink](https://aws.amazon.com/privatelink), a technology that you can use to privately access HealthLake; APIs 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 HealthLake; APIs. Traffic between your VPC and HealthLake; does not leave the Amazon network. +You can establish a private connection between your VPC and AWS HealthLake by creating an _interface VPC endpoint_. Interface VPC endpoints are powered by [AWS PrivateLink](https://aws.amazon.com/privatelink), a technology that you can use to privately access HealthLake; APIs 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 HealthLake; APIs. Traffic between your VPC and HealthLake; does not leave the Amazon network.