AWS wellarchitected documentation change
Summary
Updated terminology from 'ELB' to 'Elastic Load Balancing' in network logging recommendations
Security assessment
Change is purely terminological (abbreviation to full service name) with no security implications. No vulnerabilities or security features are mentioned or modified.
Diff
diff --git a/wellarchitected/latest/healthcare-industry-lens/detective-controls.md b/wellarchitected/latest/healthcare-industry-lens/detective-controls.md index ff9d5cf3b..c2c506db7 100644 --- a//wellarchitected/latest/healthcare-industry-lens/detective-controls.md +++ b//wellarchitected/latest/healthcare-industry-lens/detective-controls.md @@ -22 +22 @@ Enable AWS Config in all AWS accounts to assess, audit, and evaluate resources w -Capture network layer logs to track the transport layer activity going to and from network interfaces in your VPC using VPC Flow Logs. When using ELB, enable access logs to capture detailed information about the requests received and processed by one or more load balancers, including client IP addresses, request paths, and server responses. Similar approaches should be employed for other AWS services, such as Amazon API Gateway, which offer similar functionality. +Capture network layer logs to track the transport layer activity going to and from network interfaces in your VPC using VPC Flow Logs. When using Elastic Load Balancing, enable access logs to capture detailed information about the requests received and processed by one or more load balancers, including client IP addresses, request paths, and server responses. Similar approaches should be employed for other AWS services, such as Amazon API Gateway, which offer similar functionality.