AWS elasticloadbalancing documentation change
Summary
Updated terminology from 'ELB' to 'Elastic Load Balancing' throughout the document for consistency and clarity.
Security assessment
The changes are purely terminological updates replacing 'ELB' with 'Elastic Load Balancing'. No security vulnerabilities, procedures, or features were modified or added. The documentation still describes the same access logging mechanism without altering security implications.
Diff
diff --git a/elasticloadbalancing/latest/classic/enable-access-logs.md b/elasticloadbalancing/latest/classic/enable-access-logs.md index e9d7cebc4..d047236a6 100644 --- a//elasticloadbalancing/latest/classic/enable-access-logs.md +++ b//elasticloadbalancing/latest/classic/enable-access-logs.md @@ -9 +9 @@ Step 1: Create an S3 bucketStep 2: Attach a policy to your S3 bucketStep 3: Conf -To enable access logs for your load balancer, you must specify the name of the Amazon S3 bucket where the load balancer will store the logs. You must also attach a bucket policy to this bucket that grants ELB permission to write to the bucket. +To enable access logs for your load balancer, you must specify the name of the Amazon S3 bucket where the load balancer will store the logs. You must also attach a bucket policy to this bucket that grants Elastic Load Balancing permission to write to the bucket. @@ -60 +60 @@ When you enable access logs, you must specify an S3 bucket for the access log fi -Your S3 bucket must have a bucket policy that grants ELB permission to write the access logs to the bucket. Bucket policies are a collection of JSON statements written in the access policy language to define access permissions for your bucket. Each statement includes information about a single permission and contains a series of elements. +Your S3 bucket must have a bucket policy that grants Elastic Load Balancing permission to write the access logs to the bucket. Bucket policies are a collection of JSON statements written in the access policy language to define access permissions for your bucket. Each statement includes information about a single permission and contains a series of elements. @@ -62 +62 @@ Your S3 bucket must have a bucket policy that grants ELB permission to write the -If you're using an existing bucket that already has an attached policy, you can add the statement for ELB access logs to the policy. If you do so, we recommend that you evaluate the resulting set of permissions to ensure that they are appropriate for the users that need access to the bucket for access logs. +If you're using an existing bucket that already has an attached policy, you can add the statement for Elastic Load Balancing access logs to the policy. If you do so, we recommend that you evaluate the resulting set of permissions to ensure that they are appropriate for the users that need access to the bucket for access logs. @@ -113 +113 @@ The S3 bucket name is amzn-s3-demo-logging-bucket. There is no prefix portion in -Previously, for Regions available before August 2022, we required a policy that granted permissions to an ELB account that was specific to the Region. This legacy policy is still supported, but we recommend that you replace it with the newer policy above. If you prefer to keep using the legacy bucket policy, which is not shown here, you can. +Previously, for Regions available before August 2022, we required a policy that granted permissions to an Elastic Load Balancing account that was specific to the Region. This legacy policy is still supported, but we recommend that you replace it with the newer policy above. If you prefer to keep using the legacy bucket policy, which is not shown here, you can. @@ -115 +115 @@ Previously, for Regions available before August 2022, we required a policy that -For reference, here are the IDs of the ELB accounts to specify in `Principal`. Note that Regions that are not in this list never supported the legacy bucket policy. +For reference, here are the IDs of the Elastic Load Balancing accounts to specify in `Principal`. Note that Regions that are not in this list never supported the legacy bucket policy. @@ -242 +242 @@ The bucket must meet the requirements described in step 1, and you must attach a -First, create a .json file that enables ELB to capture and deliver logs every 60 minutes to the S3 bucket that you created for the logs: +First, create a .json file that enables Elastic Load Balancing to capture and deliver logs every 60 minutes to the S3 bucket that you created for the logs: @@ -276 +276 @@ The following is an example response. -Be sure to disable access logs before you delete the bucket that you configured for access logs. Otherwise, if there is a new bucket with the same name and the required bucket policy created in an AWS account that you don't own, ELB could write the access logs for your load balancer to this new bucket. +Be sure to disable access logs before you delete the bucket that you configured for access logs. Otherwise, if there is a new bucket with the same name and the required bucket policy created in an AWS account that you don't own, Elastic Load Balancing could write the access logs for your load balancer to this new bucket. @@ -280 +280 @@ Be sure to disable access logs before you delete the bucket that you configured -After access logs are enabled for your load balancer, ELB validates the S3 bucket and creates a test file to ensure that the bucket policy specifies the required permissions. You can use the S3 console to verify that the test file was created. The test file is not an actual access log file; it doesn't contain example records. +After access logs are enabled for your load balancer, Elastic Load Balancing validates the S3 bucket and creates a test file to ensure that the bucket policy specifies the required permissions. You can use the S3 console to verify that the test file was created. The test file is not an actual access log file; it doesn't contain example records. @@ -282 +282 @@ After access logs are enabled for your load balancer, ELB validates the S3 bucke -###### To verify that ELB created a test file in your S3 bucket +###### To verify that Elastic Load Balancing created a test file in your S3 bucket @@ -303 +303 @@ If you receive this error, the following are possible causes: - * The bucket policy does not grant ELB permission to write access logs to the bucket. Verify that you are using the correct bucket policy for the Region. Verify that the resource ARN uses the same bucket name that you specified when you enabled access logs. Verify that the resource ARN does not include a prefix if you did not specify a prefix when you enabled access logs. + * The bucket policy does not grant Elastic Load Balancing permission to write access logs to the bucket. Verify that you are using the correct bucket policy for the Region. Verify that the resource ARN uses the same bucket name that you specified when you enabled access logs. Verify that the resource ARN does not include a prefix if you did not specify a prefix when you enabled access logs.