AWS incident-manager documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in VPC endpoint documentation
Security assessment
Terminology standardization without altering security posture. PrivateLink security benefits remain unchanged.
Diff
diff --git a/incident-manager/latest/userguide/vpc-interface-endpoints.md b/incident-manager/latest/userguide/vpc-interface-endpoints.md index e72bd0c04..b83d7ed54 100644 --- a//incident-manager/latest/userguide/vpc-interface-endpoints.md +++ b//incident-manager/latest/userguide/vpc-interface-endpoints.md @@ -11 +11 @@ AWS Systems Manager Incident Manager is no longer open to new customers. Existin -You can establish a private connection between your VPC and AWS Systems Manager Incident Manager by creating an _interface VPC endpoint_. Interface endpoints are powered by AWS PrivateLink. With AWS PrivateLink, you can privately access Incident Manager 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 Incident Manager API operations. Traffic between your VPC and Incident Manager stays within the Amazon network. +You can establish a private connection between your VPC and AWS Systems Manager Incident Manager by creating an _interface VPC endpoint_. Interface endpoints are powered by AWS PrivateLink. With AWS PrivateLink, you can privately access Incident Manager 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 Incident Manager API operations. Traffic between your VPC and Incident Manager stays within the Amazon network.