AWS global-accelerator documentation change
Summary
Updated terminology from 'ELB' to 'Elastic Load Balancing' in policy examples
Security assessment
Consistency update in documentation without security impact. No changes to actual permissions or security controls.
Diff
diff --git a/global-accelerator/latest/dg/security_iam_id-based-policy-examples.md b/global-accelerator/latest/dg/security_iam_id-based-policy-examples.md index 9f9511264..69b35c201 100644 --- a//global-accelerator/latest/dg/security_iam_id-based-policy-examples.md +++ b//global-accelerator/latest/dg/security_iam_id-based-policy-examples.md @@ -89 +89 @@ Attach the first policy, `GlobalAcceleratorReadOnlyAccess`, if users only need t -Attach the second policy, `GlobalAcceleratorFullAccess`, to users who need to create or make updates to accelerators. The full access policy includes _full_ permissions for Global Accelerator as well as _describe_ permissions for Amazon EC2 and ELB. +Attach the second policy, `GlobalAcceleratorFullAccess`, to users who need to create or make updates to accelerators. The full access policy includes _full_ permissions for Global Accelerator as well as _describe_ permissions for Amazon EC2 and Elastic Load Balancing. @@ -93 +93 @@ Attach the second policy, `GlobalAcceleratorFullAccess`, to users who need to cr -If you create an identity-based permissions policy that does not include the required permissions for Amazon EC2 and ELB, users with that policy will not be able to add Amazon EC2 and ELB resources to accelerators. +If you create an identity-based permissions policy that does not include the required permissions for Amazon EC2 and Elastic Load Balancing, users with that policy will not be able to add Amazon EC2 and Elastic Load Balancing resources to accelerators.