AWS mpa documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in Multi-party approval VPC documentation
Security assessment
Service name abbreviation update. No impact on security posture or PrivateLink configuration instructions.
Diff
diff --git a/mpa/latest/userguide/vpc-interface-endpoints.md b/mpa/latest/userguide/vpc-interface-endpoints.md index 46536314a..fe07498a4 100644 --- a//mpa/latest/userguide/vpc-interface-endpoints.md +++ b//mpa/latest/userguide/vpc-interface-endpoints.md @@ -9 +9 @@ ConsiderationsCreate an interface endpointCreate an endpoint policy -You can use AWS PrivateLink to create a private connection between your VPC and Multi-party approval. You can access Multi-party approval 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 Multi-party approval. +You can use AWS PrivateLink to create a private connection between your VPC and Multi-party approval. You can access Multi-party approval 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 Multi-party approval.