AWS vpc documentation change
Summary
Updated service name references from 'ELB' to 'Elastic Load Balancing' in two locations for consistency and clarity.
Security assessment
This is a branding/documentation consistency update with no security implications. No security vulnerabilities, configurations, or policies were modified.
Diff
diff --git a/vpc/latest/network-access-analyzer/security_iam_required-API-permissions.md b/vpc/latest/network-access-analyzer/security_iam_required-API-permissions.md index e7169f6a5..73144001f 100644 --- a//vpc/latest/network-access-analyzer/security_iam_required-API-permissions.md +++ b//vpc/latest/network-access-analyzer/security_iam_required-API-permissions.md @@ -13 +13 @@ Network Access Analyzer relies on data from other AWS services. It uses permissi - * ELB + * Elastic Load Balancing @@ -55 +55 @@ The following permissions are required to call the Network Access Analyzer APIs. -Network Access Analyzer uses describe calls while gathering information about your resources from Amazon VPC, Amazon EC2, ELB, and AWS Network Firewall (for example, subnets, network interfaces, and security groups). To access Network Access Analyzer, users must also have these API permissions. +Network Access Analyzer uses describe calls while gathering information about your resources from Amazon VPC, Amazon EC2, Elastic Load Balancing, and AWS Network Firewall (for example, subnets, network interfaces, and security groups). To access Network Access Analyzer, users must also have these API permissions.