AWS IAM documentation change
Summary
Replaced 'classic IAM console' with 'Console' in multiple locations
Security assessment
Terminology update from 'classic IAM console' to 'Console' appears to be branding/UI naming standardization with no security implications mentioned.
Diff
diff --git a/IAM/latest/UserGuide/id_users_change-permissions.md b/IAM/latest/UserGuide/id_users_change-permissions.md index 61a828538..b9c254778 100644 --- a//IAM/latest/UserGuide/id_users_change-permissions.md +++ b//IAM/latest/UserGuide/id_users_change-permissions.md @@ -61 +61 @@ Adding an IAM user to an IAM group updates the user's permissions with the permi -classic IAM console +Console @@ -103 +103 @@ If you choose to add permissions to an IAM user by copying permissions, IAM copi -classic IAM console +Console @@ -131 +131 @@ You can attach a managed policy directly to an IAM user. The updated permissions -classic IAM console +Console @@ -159 +159 @@ A permissions boundary is an advanced feature for managing permissions in AWS th -classic IAM console +Console @@ -196 +196 @@ Changing permissions updates the user's access immediately. -classic IAM console +Console @@ -226 +226 @@ Changing a permissions boundary updates the user's access immediately. -classic IAM console +Console @@ -252 +252 @@ Removing a permissions policy updates the user's access immediately. -classic IAM console +Console @@ -282 +282 @@ Removing the permissions boundary updates the user's access immediately. -classic IAM console +Console