IAM, ACCOUNTS AND AWS ORGANISATIONS Flashcards
IAM Identity Policies
policy permissions that tell AWS what resources can or can’t be accessed using the identity
What takes priority when reading a IAM Policy?
If you have a explicit Deny statement that Always takes president over an explicit allow
What if there is No explicit deny or allow on an IAM Policy ?
the AWS resource are by default denied
Inline policies
attached policies to an individual accounts
used for special or exceptional allow or Deny for managed policies
Managed Policies
reusable low management overhead
IAM Users
identity used for anything that requiring long-term AWS access ex. Humans, applications or service accounts
What are Access Keys used for ?
Humans using CLI and applications
IAM user account limit
5,000 IAM users per account
Account Group limits
IAM users can be member of 10 groups
IAM Groups
containers for IAM users
Can IAM groups have policies attached to them ?
groups can have policies attached to them inline/managed
cons of IAM Groups
- no nesting
- no built in All users group
- 200 groups per account (soft limit can be increased )
- not an identity
What can’t you do with an IAM group that you can do with IAM user?
Groups can not be login to and as such are not a true identity so they can’t be references as a principal in a policy
Principal
Physical person, application, device, or process which wants to authenticate with AWS
IAM user vs IAM role
single principal
Long time usage
can have policies attached to the, Both Inline and manages