AWS Security ChangesHomeSearch

AWS elasticloadbalancing documentation change

Service: elasticloadbalancing · 2026-01-25 · Documentation low

File: elasticloadbalancing/latest/classic/elb-monitor-logs.md

Summary

Updated terminology from 'ELB' to 'Elastic Load Balancing' for consistency across documentation

Security assessment

Changes are purely branding/nomenclature updates without technical modifications. No security vulnerabilities, features, or configurations are mentioned. The content about access logs and CloudTrail remains functionally identical with only name standardization.

Diff

diff --git a/elasticloadbalancing/latest/classic/elb-monitor-logs.md b/elasticloadbalancing/latest/classic/elb-monitor-logs.md
index 6186f2dd6..90458d0bf 100644
--- a//elasticloadbalancing/latest/classic/elb-monitor-logs.md
+++ b//elasticloadbalancing/latest/classic/elb-monitor-logs.md
@@ -12 +12 @@ You can use the following features to monitor your load balancers, analyze traff
-ELB publishes data points to Amazon CloudWatch about your load balancers and back-end instances. CloudWatch enables you to retrieve statistics about those data points as an ordered set of time-series data, known as _metrics_. You can use these metrics to verify that your system is performing as expected. For more information, see [CloudWatch metrics for your Classic Load Balancer](./elb-cloudwatch-metrics.html).
+Elastic Load Balancing publishes data points to Amazon CloudWatch about your load balancers and back-end instances. CloudWatch enables you to retrieve statistics about those data points as an ordered set of time-series data, known as _metrics_. You can use these metrics to verify that your system is performing as expected. For more information, see [CloudWatch metrics for your Classic Load Balancer](./elb-cloudwatch-metrics.html).
@@ -14 +14 @@ ELB publishes data points to Amazon CloudWatch about your load balancers and bac
-**ELB access logs**
+**Elastic Load Balancing access logs**
@@ -17 +17 @@ ELB publishes data points to Amazon CloudWatch about your load balancers and bac
-The access logs for ELB capture detailed information for requests made to your load balancer and stores them as log files in the Amazon S3 bucket that you specify. Each log contains details such as the time a request was received, the client's IP address, latencies, request path, and server responses. You can use these access logs to analyze traffic patterns and to troubleshoot your back-end applications. For more information, see [Access logs for your Classic Load Balancer](./access-log-collection.html).
+The access logs for Elastic Load Balancing capture detailed information for requests made to your load balancer and stores them as log files in the Amazon S3 bucket that you specify. Each log contains details such as the time a request was received, the client's IP address, latencies, request path, and server responses. You can use these access logs to analyze traffic patterns and to troubleshoot your back-end applications. For more information, see [Access logs for your Classic Load Balancer](./access-log-collection.html).
@@ -22 +22 @@ The access logs for ELB capture detailed information for requests made to your l
-AWS CloudTrail enables you to keep track of the calls made to the ELB API by or on behalf of your AWS account. CloudTrail stores the information in log files in the Amazon S3 bucket that you specify. You can use these log files to monitor activity of your load balancers by determining which requests were made, the source IP addresses where the requests came from, who made the request, when the request was made, and so on. For more information, see [Log API calls for ELB using CloudTrail](https://docs.aws.amazon.com/elasticloadbalancing/latest/userguide/cloudtrail-logs.html).
+AWS CloudTrail enables you to keep track of the calls made to the Elastic Load Balancing API by or on behalf of your AWS account. CloudTrail stores the information in log files in the Amazon S3 bucket that you specify. You can use these log files to monitor activity of your load balancers by determining which requests were made, the source IP addresses where the requests came from, who made the request, when the request was made, and so on. For more information, see [Log API calls for Elastic Load Balancing using CloudTrail](https://docs.aws.amazon.com/elasticloadbalancing/latest/userguide/cloudtrail-logs.html).