AWS billingconductor documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in a sentence about VPC connectivity
Security assessment
This is a branding/nomenclature update (shortening the service name). The security implications of using PrivateLink remain unchanged, and no new security guidance is added.
Diff
diff --git a/billingconductor/latest/userguide/vpc-interface-endpoints.md b/billingconductor/latest/userguide/vpc-interface-endpoints.md index c5b3d52c9..4d5260c05 100644 --- a//billingconductor/latest/userguide/vpc-interface-endpoints.md +++ b//billingconductor/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 AWS Billing Conductor. You can access Billing Conductor 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 Billing Conductor. +You can use AWS PrivateLink to create a private connection between your VPC and AWS Billing Conductor. You can access Billing Conductor 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 Billing Conductor.