brandon/oam
1
0
Fork 0
mirror of https://gitea.com/mcereda/oam.git synced 2026-02-23 12:04:23 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix(aws/iam): add note about access key creation tagging the user

Browse Source
This commit is contained in:
Michele Cereda
2026-02-10 20:43:03 +01:00
parent ef181ac7d3
commit 1b151d8c68
1 changed files with 15 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
knowledge base/cloud computing/aws/iam.md
View File

@@ -2,6 +2,20 @@
Controls who is authenticated (signed in) and authorized (has permissions) to use resources.
1. [TL;DR](#tldr)
1. [Users](#users)
1. [Groups](#groups)
1. [Policies](#policies)
1. [Trust Policies](#trust-policies)
1. [Trust Relationships](#trust-relationships)
1. [Roles](#roles)
1. [Assume Roles](#assume-roles)
1. [Require MFA for assuming Roles](#require-mfa-for-assuming-roles)
1. [Further readings](#further-readings)
1. [Sources](#sources)
## TL;DR
Authentication is provided by matching the sign-in credentials to a _principal_ trusted by the AWS account.<br/>
Principals are IAM users, federated users, IAM roles, and applications.
@@ -52,16 +66,7 @@ From [Using service-linked roles]:
Refer [aws.permissions.cloud] for a community-driven source of truth for AWS IAM.
1. [Users](#users)
1. [Groups](#groups)
1. [Policies](#policies)
1. [Trust Policies](#trust-policies)
1. [Trust Relationships](#trust-relationships)
1. [Roles](#roles)
1. [Assume Roles](#assume-roles)
1. [Require MFA for assuming Roles](#require-mfa-for-assuming-roles)
1. [Further readings](#further-readings)
1. [Sources](#sources)
When creating Access Keys, the user owning it will be tagged with the Key's ID for… ahem… easing management, I guess.
## Users