IAM Access Advisor - when the access keys were last used and which services
IAM Access Analyzer - the resources that are shared with public third party external other than trust zone.
Using cross account IAM role vs Resource Based Policies - If we assume a role, we gave up original permissions that we have and only have access permissions that the role have. But when using resource-based policies, no need to give up.
IAM permission boundaries - for users or roles to set maximum permission an IAM entity get so no escalation.
Use cases:
Identity Federation can have many flavors:
SAML 2.0 Federation
Security Assertion Markup Language 2.0 (SAML 2.0)
Open standard used by many identity providers (e.g., ADFS)
Access to AWS Console, AWS CLI, or AWS API using temporary credentials
Under-the-hood: Uses the STS API AssumeRoleWithSAML
SAML 2.0 Federation is the “old way”, Amazon Single Sign-On (AWS SSO) Federation is the new managed and simpler way
Custom Identity Broker Application
Use only if Identity Provider is NOT compatible with SAML 2.0
The Identity Broker Authenticates users & requests temporary credentials from AWS
The Identity Broker must determine the appropriate IAM Role
Uses the STS API AssumeRole or GetFederationToken by client to obtain temp credentials
Web Identity Federation – With Cognito
AWS Managed Microsoft AD
Create your own AD in AWS, manage users locally, supports MFA
Establish “trust” connections with your on- premises AD
One-way trust: AWS → On-prem
One-way trust: On-prem → AWS or
Two-way forest trust: AWS ↔ on-premises
No replication, just trust between on-premise AD and AWS AD
For better latency, replicate on-prem AD to EC2 instance manged by yourself and deploy AD.
AD Connector
Simple AD