AWS elasticloadbalancing documentation change
Summary
Updated terminology from 'ELB API' to 'Elastic Load Balancing API' and corrected link text for CloudTrail documentation
Security assessment
Change only involves branding/terminology updates without altering security content or addressing vulnerabilities. Maintains existing security logging capabilities without modification.
Diff
diff --git a/elasticloadbalancing/latest/gateway/monitoring.md b/elasticloadbalancing/latest/gateway/monitoring.md index 0ff3318db..0da3b224b 100644 --- a//elasticloadbalancing/latest/gateway/monitoring.md +++ b//elasticloadbalancing/latest/gateway/monitoring.md @@ -26 +26 @@ There are two entries for each connection through your Gateway Load Balancer, on -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).