AWS elasticloadbalancing documentation change
Summary
Updated 'ELB API' to 'Elastic Load Balancing API' in CloudTrail logging documentation
Security assessment
Change only updates product naming in existing monitoring documentation. CloudTrail logging remains a security best practice, but this update doesn't add new security guidance or address vulnerabilities.
Diff
diff --git a/elasticloadbalancing/latest/network/load-balancer-monitoring.md b/elasticloadbalancing/latest/network/load-balancer-monitoring.md index 3f82d14e5..a7e39558a 100644 --- a//elasticloadbalancing/latest/network/load-balancer-monitoring.md +++ b//elasticloadbalancing/latest/network/load-balancer-monitoring.md @@ -38 +38 @@ You can use access logs to capture detailed information about TLS requests made -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).