AWS singlesignon documentation change
Summary
Contraction replacements ('don't' to 'do not', 'can't' to 'cannot') in permissions boundary documentation
Security assessment
Changes are grammatical/style improvements without altering security meaning. Existing security documentation about permissions boundaries remains unchanged except for contraction replacements.
Diff
diff --git a/singlesignon/latest/userguide/permissionsetcustom.md b/singlesignon/latest/userguide/permissionsetcustom.md index 45cd41dbd..6babfec99 100644 --- a//singlesignon/latest/userguide/permissionsetcustom.md +++ b//singlesignon/latest/userguide/permissionsetcustom.md @@ -44 +44 @@ Your AWS account also contains a large number of AWS managed IAM policies for sp -AWS populates every AWS account with AWS managed policies. To deploy a permission set with AWS managed policies, you don't need to first create a policy in your AWS accounts. When you build your permission set with Customer managed policies, you must create the policies in your AWS accounts yourself before you assign the permission set. +AWS populates every AWS account with AWS managed policies. To deploy a permission set with AWS managed policies, you do not need to first create a policy in your AWS accounts. When you build your permission set with Customer managed policies, you must create the policies in your AWS accounts yourself before you assign the permission set. @@ -62 +62 @@ For more information, see [Customer managed policies](https://docs.aws.amazon.co -You can attach a _permissions boundary_ to your permission set. A permissions boundary is an AWS managed or customer managed IAM policy that sets the maximum permissions that an identity-based policy can grant to an IAM principal. When you apply a permissions boundary, your Inline policies, Customer managed policies, and AWS managed policies can't grant any permissions that exceed the permissions that your permissions boundary grants. A permissions boundary doesn't grant any permissions, but instead makes it so that IAM ignores all permissions beyond the boundary. +You can attach a _permissions boundary_ to your permission set. A permissions boundary is an AWS managed or customer managed IAM policy that sets the maximum permissions that an identity-based policy can grant to an IAM principal. When you apply a permissions boundary, your Inline policies, Customer managed policies, and AWS managed policies cannot grant any permissions that exceed the permissions that your permissions boundary grants. A permissions boundary doesn't grant any permissions, but instead makes it so that IAM ignores all permissions beyond the boundary.