Federated Access and Identity Federation
Federated Access and Identity Federation in AWS IAM allows you to grant your organization's users single sign-on access to AWS Management Console using their existing identity system like Microsoft Active Directory, Google Workspace, or other identity providers like Okta or OneLogin. With this feature, you can use Security Assertion Markup Language 2.0 (SAML 2.0) or the AWS Security Token Service (STS) AssumeRole* API operations to get temporary security credentials for your users. This helps you avoid creating and managing individual IAM users for each organization user. Federation reduces the operational overhead while improving security by allowing for least-privilege access control and centralized account management.
Guide to Federated Access & Identity Federation in AWS
What is it?
Federated Access in AWS IAM pertains to the process of linking a user's identity from an external identity provider to an IAM role. It allows users to authenticate using their own organizational identities to access AWS resources. Identity Federation, on the other hand, is a broader concept that pertains to the combination of different identity management systems.
Why is it important?
It negates the need for multiple credentials as users can use their existing identities. This simplifies access management, enhances security, and increases efficiency.
How does it work?
It generally works by the Identity provider (IdP) sending an authentication request to AWS, which AWS confirms. On successful confirmation, AWS generates an access token (typically STS tokens) which is used by the federated user to access AWS resources. These tokens are temporary and expire after a short duration.
Exam Tips: Answering Questions on Federated Access and Identity Federation
Understanding the underlying mechanism, key terms, and principles is particularly important for the exam. Remember, federated users are not permanent AWS IAM users and AWS never stores their credentials. And focus on the part where these tokens have a default and maximum duration.
Note: Security Token Service (STS), External Identity Providers (IdP), SAML 2.0 are some key terms associated with Federated Access and Identity Federation.
For answering exam questions, understand that any question pertaining to large organizations, providing temporary access or the use of organizational identities to access AWS often points towards Federated Access and Identity Federation.
Also, understanding federated login workflow and STS service will help you in answering scenario-based questions.
AWS Certified Solutions Architect - Federated Access and Identity Federation Example Questions
Test your knowledge of Federated Access and Identity Federation
Question 1
An organization wants to grant their application running on EC2 access to specific resources in their Amazon S3 bucket. Which method is the most secure way to achieve this?
Question 2
A company uses a custom Identity Broker to federate users from its existing SAML 2.0 Identity Provider (IdP) into AWS. Focusing on the backend sequence that occurs after the user has successfully authenticated and the IdP has issued a SAML assertion, which ordered flow correctly shows how temporary AWS credentials are obtained and used to access an AWS service?
Question 3
A company wants to enable employees to access their AWS Management Console without creating separate AWS IAM user accounts. The employees already have Microsoft Active Directory accounts. Which approach should they pursue?