AWS elasticloadbalancing documentation change
Summary
Updated references from 'ELB API' to 'Elastic Load Balancing API'
Security assessment
Terminology update without security implications. CloudTrail logging functionality remains identical, with no new security features or vulnerabilities addressed.
Diff
diff --git a/elasticloadbalancing/latest/application/load-balancer-monitoring.md b/elasticloadbalancing/latest/application/load-balancer-monitoring.md index a72b72f22..9ae84e123 100644 --- a//elasticloadbalancing/latest/application/load-balancer-monitoring.md +++ b//elasticloadbalancing/latest/application/load-balancer-monitoring.md @@ -37 +37 @@ You can use request tracing to track HTTP requests. The load balancer adds a hea -You can use AWS CloudTrail to capture detailed information about the calls made to the ELB API and store them as log files in Amazon S3. You can use these CloudTrail logs to determine which calls were made, the source IP address where the call came from, who made the call, when the call 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). +You can use AWS CloudTrail to capture detailed information about the calls made to the Elastic Load Balancing API and store them as log files in Amazon S3. You can use these CloudTrail logs to determine which calls were made, the source IP address where the call came from, who made the call, when the call 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).