AWS elasticloadbalancing documentation change
Summary
Updated terminology from 'ELB' to 'Elastic Load Balancing' throughout the document for consistency and branding. No technical changes to access log functionality or features.
Security assessment
The changes exclusively replace the acronym 'ELB' with the full service name 'Elastic Load Balancing'. There is no mention of vulnerabilities, security incidents, or weaknesses. Existing security features like SSE-S3 encryption remain unchanged and are not newly documented.
Diff
diff --git a/elasticloadbalancing/latest/classic/access-log-collection.md b/elasticloadbalancing/latest/classic/access-log-collection.md index c78e1242b..1258495ac 100644 --- a//elasticloadbalancing/latest/classic/access-log-collection.md +++ b//elasticloadbalancing/latest/classic/access-log-collection.md @@ -9 +9 @@ Access log filesAccess log entriesProcessing access logs -ELB provides access logs that capture detailed information about requests sent to your load balancer. Each log contains information such as the time the request was received, the client's IP address, latencies, request paths, and server responses. You can use these access logs to analyze traffic patterns and to troubleshoot issues. +Elastic Load Balancing provides access logs that capture detailed information about requests sent to your load balancer. Each log contains information such as the time the request was received, the client's IP address, latencies, request paths, and server responses. You can use these access logs to analyze traffic patterns and to troubleshoot issues. @@ -11 +11 @@ ELB provides access logs that capture detailed information about requests sent t -Access logs are an optional feature of ELB that is disabled by default. After you enable access logs for your load balancer, ELB captures the logs and stores them in the Amazon S3 bucket that you specify. You can disable access logging at any time. +Access logs are an optional feature of Elastic Load Balancing that is disabled by default. After you enable access logs for your load balancer, Elastic Load Balancing captures the logs and stores them in the Amazon S3 bucket that you specify. You can disable access logging at any time. @@ -15 +15 @@ Each access log file is automatically encrypted using SSE-S3 before it is stored -There is no additional charge for access logs. You will be charged storage costs for Amazon S3, but will not be charged for the bandwidth used by ELB to send log files to Amazon S3. For more information about storage costs, see [Amazon S3 Pricing](https://aws.amazon.com/s3/pricing/). +There is no additional charge for access logs. You will be charged storage costs for Amazon S3, but will not be charged for the bandwidth used by Elastic Load Balancing to send log files to Amazon S3. For more information about storage costs, see [Amazon S3 Pricing](https://aws.amazon.com/s3/pricing/). @@ -34 +34 @@ There is no additional charge for access logs. You will be charged storage costs -ELB publishes a log file for each load balancer node at the interval you specify. You can specify a publishing interval of either 5 minutes or 60 minutes when you enable the access log for your load balancer. By default, ELB publishes logs at a 60-minute interval. If the interval is set for 5 minutes, the logs are published at 1:05, 1:10, 1:15, and so on. The start of log delivery is delayed up to 5 minutes if the interval is set to 5 minutes, and up to 15 minutes if the interval is set to 60 minutes. You can modify the publishing interval at any time. +Elastic Load Balancing publishes a log file for each load balancer node at the interval you specify. You can specify a publishing interval of either 5 minutes or 60 minutes when you enable the access log for your load balancer. By default, Elastic Load Balancing publishes logs at a 60-minute interval. If the interval is set for 5 minutes, the logs are published at 1:05, 1:10, 1:15, and so on. The start of log delivery is delayed up to 5 minutes if the interval is set to 5 minutes, and up to 15 minutes if the interval is set to 60 minutes. You can modify the publishing interval at any time. @@ -107 +107 @@ You can store your log files in your bucket for as long as you want, but you can -ELB logs requests sent to the load balancer, including requests that never made it to the back-end instances. For example, if a client sends a malformed request, or there are no healthy instances to respond, the requests are still logged. +Elastic Load Balancing logs requests sent to the load balancer, including requests that never made it to the back-end instances. For example, if a client sends a malformed request, or there are no healthy instances to respond, the requests are still logged. @@ -111 +111 @@ ELB logs requests sent to the load balancer, including requests that never made -ELB logs requests on a best-effort basis. We recommend that you use access logs to understand the nature of the requests, not as a complete accounting of all requests. +Elastic Load Balancing logs requests on a best-effort basis. We recommend that you use access logs to understand the nature of the requests, not as a complete accounting of all requests.