AWS awsaccountbilling documentation change
Summary
Changed 'AWS Direct Connect' to 'Direct Connect' in VPC endpoint documentation
Security assessment
Branding terminology update that doesn't affect the security posture of PrivateLink implementation
Diff
diff --git a/awsaccountbilling/latest/aboutv2/vpc-interface-endpoints.md b/awsaccountbilling/latest/aboutv2/vpc-interface-endpoints.md index 849ea7a9d..056cc0c42 100644 --- a//awsaccountbilling/latest/aboutv2/vpc-interface-endpoints.md +++ b//awsaccountbilling/latest/aboutv2/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 and Cost Management. You can access Billing and Cost Management 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 and Cost Management. +You can use AWS PrivateLink to create a private connection between your VPC and AWS Billing and Cost Management. You can access Billing and Cost Management 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 and Cost Management.