AWS opensearch-service documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in VPC endpoint documentation
Security assessment
Minor terminology update without altering the security posture. The guidance about private network access remains unchanged.
Diff
diff --git a/opensearch-service/latest/developerguide/vpc-interface-endpoints.md b/opensearch-service/latest/developerguide/vpc-interface-endpoints.md index 831bdd89c..021f4b10a 100644 --- a//opensearch-service/latest/developerguide/vpc-interface-endpoints.md +++ b//opensearch-service/latest/developerguide/vpc-interface-endpoints.md @@ -9 +9 @@ ConsiderationsProvide access to a domainCreate an interface VPC endpointManaging -You can access an Amazon OpenSearch Service domain by setting up an OpenSearch Service-managed VPC endpoint (powered by AWS PrivateLink). These endpoints create a private connection between your VPC and Amazon OpenSearch Service. You can access OpenSearch Service VPC domains as if they 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 OpenSearch Service. +You can access an Amazon OpenSearch Service domain by setting up an OpenSearch Service-managed VPC endpoint (powered by AWS PrivateLink). These endpoints create a private connection between your VPC and Amazon OpenSearch Service. You can access OpenSearch Service VPC domains as if they 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 OpenSearch Service.