AWS vpc documentation change
Summary
Added Client VPN to attachment types list and included new Client VPN Data Transfer Out usage under billable data types.
Security assessment
Changes solely update billing-related documentation: adding Client VPN to existing attachment type lists and creating a new billing category for Client VPN data transfer. No security mechanisms, vulnerabilities, or security features are mentioned or implied in the additions.
Diff
diff --git a/vpc/latest/tgw/metering-policy.md b/vpc/latest/tgw/metering-policy.md index 2ee99c59f..e4599454b 100644 --- a//vpc/latest/tgw/metering-policy.md +++ b//vpc/latest/tgw/metering-policy.md @@ -57 +57 @@ By default, transit gateway uses a sender-based cost allocation model where data - * Source and destination attachment types (VPC, VPN, Direct Connect Gateway, Peering, Network Function and VPN Concentrator) + * Source and destination attachment types (VPC, VPN, Client VPN, Direct Connect Gateway, Peering, Network Function, and VPN Concentrator) @@ -87 +87,3 @@ Flexible cost allocation via metering policies applies to following data usage t - * Transit gateway Data Processing Usage on VPC, VPN, VPN Concentrator and Direct Connect attachments + * Transit gateway Data Processing Usage on VPC, VPN, Client VPN, VPN Concentrator, and Direct Connect attachments + + * Client VPN Data Transfer Out usage on Client VPN attachments