AWS IAM documentation change
Summary
Updated service name from 'ELB' to 'Elastic Load Balancing' in service principal example
Security assessment
The change only corrects a service name abbreviation without modifying policy functionality or addressing security weaknesses. The example continues to demonstrate the same principal configuration pattern with no security impact.
Diff
diff --git a/IAM/latest/UserGuide/reference_policies_elements_principal.md b/IAM/latest/UserGuide/reference_policies_elements_principal.md index 0baf8a4d8..06c81ccd5 100644 --- a//IAM/latest/UserGuide/reference_policies_elements_principal.md +++ b//IAM/latest/UserGuide/reference_policies_elements_principal.md @@ -275 +275 @@ The service principal is defined by the service. You can find the service princi -The following example shows a policy that can be attached to a service role. The policy enables two services, Amazon ECS and ELB, to assume the role. The services can then perform any tasks granted by the permissions policy assigned to the role (not shown). To specify multiple service principals, you do not specify two `Service` elements; you can have only one. Instead, you use an array of multiple service principals as the value of a single `Service` element. +The following example shows a policy that can be attached to a service role. The policy enables two services, Amazon ECS and Elastic Load Balancing, to assume the role. The services can then perform any tasks granted by the permissions policy assigned to the role (not shown). To specify multiple service principals, you do not specify two `Service` elements; you can have only one. Instead, you use an array of multiple service principals as the value of a single `Service` element.