AWS IAM documentation change
Summary
Fixed typographical errors: removed stray comma and corrected 'SAMl' to 'SAML'
Security assessment
These are minor typographical corrections with no security implications. The changes improve readability but don't alter security concepts or address vulnerabilities.
Diff
diff --git a/IAM/latest/UserGuide/introduction_access-management.md b/IAM/latest/UserGuide/introduction_access-management.md index c3aa67bf5..feba59acd 100644 --- a//IAM/latest/UserGuide/introduction_access-management.md +++ b//IAM/latest/UserGuide/introduction_access-management.md @@ -48 +48 @@ You can organize IAM users into _IAM groups_ and attach a policy to the IAM grou -IAM users or IAM groups can have multiple policies attached to them that grant different permissions. In that case, the combination of policies determines the effective permissions for the principal. If the principal doesn't have explicit `Allow` permission for both an action and a resource, the principal doesn't have those permissions, . +IAM users or IAM groups can have multiple policies attached to them that grant different permissions. In that case, the combination of policies determines the effective permissions for the principal. If the principal doesn't have explicit `Allow` permission for both an action and a resource, the principal doesn't have those permissions. @@ -52 +52 @@ IAM users or IAM groups can have multiple policies attached to them that grant d -Federated principals don't have permanent identities in your AWS account the way that IAM users do. To assign permissions to federated principals, you can create an entity referred to as a _role_ and define permissions for the role. When a SAMl or OIDC federated principal signs in to AWS, the user is associated with the role and is granted the permissions that are defined in the role. For more information, see [Create a role for a third-party identity provider](./id_roles_create_for-idp.html). +Federated principals don't have permanent identities in your AWS account the way that IAM users do. To assign permissions to federated principals, you can create an entity referred to as a _role_ and define permissions for the role. When a SAML or OIDC federated principal signs in to AWS, the user is associated with the role and is granted the permissions that are defined in the role. For more information, see [Create a role for a third-party identity provider](./id_roles_create_for-idp.html).