*Session policies - used with the AssumeRole* API actions
The '''effective''' permissions are the union of the two policies, <math display="block">A \cup B</math> when combining an Identity-based policy with a Resource-based policy. But, are only the '''intersection''' <math display="block">A \cap B</math> when combining with Permissions boundary or Organizations SCP<ref>https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_evaluation-logic.html#policy-eval-basics-id-rdp</ref>
28. IAM Policy Structure
30. [HOL] Using Attribute-Based Access Control (ABAC)
Roles are '''assumed''' by users, applications and services.
Policies are JSON and may be either Identity based, or Resource based.
Authentication methods: password + optional MFA token; Access Key + Secret Access Key; X-509 Certificate
AWS Security Token Service (STS) sts:AssumeRole returns temporary security credentials.
Multi-Factor Authentication
;Something you '''know'''
;Something you ''' have'''
;Something you '''are'''
A Trust Policy is also an example of a resource-based policy.
A Permissions Policy is an identity-based policy.
31. [HOL] Apply Permissions Boundary
32. Use Cases for IAM Roles
cross-account access and 3rd-party access
33. [HOL] Cross-Account Access to S3
{{References}}<references />
[[Category:AWS]]