AWS whitepapers documentation change
Summary
Updated terminology from 'ELB' to 'Elastic Load Balancing' for clarity
Security assessment
Change is purely terminological (acronym expansion) with no security context. No vulnerabilities, configurations, or security practices were modified or discussed.
Diff
diff --git a/whitepapers/latest/building-scalable-secure-multi-vpc-network-infrastructure/using-network-firewall-for-centralized-ingress.md b/whitepapers/latest/building-scalable-secure-multi-vpc-network-infrastructure/using-network-firewall-for-centralized-ingress.md index aec608b28..5c84b9e5d 100644 --- a//whitepapers/latest/building-scalable-secure-multi-vpc-network-infrastructure/using-network-firewall-for-centralized-ingress.md +++ b//whitepapers/latest/building-scalable-secure-multi-vpc-network-infrastructure/using-network-firewall-for-centralized-ingress.md @@ -23 +23 @@ Network Firewall can perform deep packet inspection (DPI) on ingress traffic. Us - * ELB in Edge VPC can only have IP addresses as target types, not a hostname. In the preceding figure, the targets are the private IPs of the Network Load Balancer in spoke VPCs. Using IP targets behind the ELB in the edge VPC results in the loss of Auto Scaling. + * Elastic Load Balancing in Edge VPC can only have IP addresses as target types, not a hostname. In the preceding figure, the targets are the private IPs of the Network Load Balancer in spoke VPCs. Using IP targets behind the ELB in the edge VPC results in the loss of Auto Scaling.