AWS IAM: Note: no console access IAM users in new AWS experience
Summary
Adds a note that in the new AWS experience you must add human users to your team and cannot create IAM users with console access, linking to the invite-team-members docs.
Security assessment
The note steers human access away from long-lived IAM users with console credentials toward centralized team/identity management, which is a recognized credential-management best practice (reducing static user credentials), so it qualifies as security guidance.
Evidence
+If you're using our [new AWS experience](https://docs.aws.amazon.com/accounts/latest/reference/sign-in-new.html) and want to provide human users with access to your projects or AWS Settings, you must add them to your team. In our new experience, you cannot create IAM users with console access. For more information, see [Invite team members](https://docs.aws.amazon.com/accounts/latest/reference/invite-team-members.html).
Diff
diff --git a/IAM/latest/UserGuide/id_users.md b/IAM/latest/UserGuide/id_users.md index 07ff6a321..737857f8d 100644 --- a//IAM/latest/UserGuide/id_users.md +++ b//IAM/latest/UserGuide/id_users.md @@ -14,0 +15,2 @@ IAM [best practices](./best-practices.html) recommend that you require human use +If you're using our [new AWS experience](https://docs.aws.amazon.com/accounts/latest/reference/sign-in-new.html) and want to provide human users with access to your projects or AWS Settings, you must add them to your team. In our new experience, you cannot create IAM users with console access. For more information, see [Invite team members](https://docs.aws.amazon.com/accounts/latest/reference/invite-team-members.html). +