You're reading from Implementing Identity Management on AWS A real-world guide to solving customer and workforce IAM challenges in your AWS cloud environments

Product type Paperback

Published in Oct 2021

Publisher Packt

ISBN-13 9781800562288

Length 504 pages

Edition 1st Edition

Tools

AWS

Concepts

Identity Management

Author (1):

Jon Lehtinen

View More author details

Table of Contents (17) Chapters

Preface

1. Section 1: IAM and AWS – Critical Concepts, Definitions, and Tools

2. Chapter 1: An Introduction to IAM and AWS IAM Concepts FREE CHAPTER

3. Chapter 2: An Introduction to the AWS CLI

4. Chapter 3: IAM User Management

5. Chapter 4: Access Management, Policies, and Permissions

6. Chapter 5: Introducing Amazon Cognito

7. Chapter 6: Introduction to AWS Organizations and AWS Single Sign-On

8. Chapter 7: Other AWS Identity Services

9. Section 2: Implementing IAM on AWS for Administrative Use Cases

10. Chapter 8: An Ounce of Prevention – Planning Your Administrative Model

11. Chapter 9: Bringing Your Admins into the AWS Administrative Backplane

12. Chapter 10: Administrative Single Sign-On to the AWS Backplane

13. Section 3: Implementing IAM on AWS for Application Use Cases

14. Chapter 11: Bringing Your Users into AWS

15. Chapter 12: AWS-Hosted Application Single Sign-On Using an Existing Identity Provider

16. Other Books You May Enjoy

Using Managed AD and trusts

We will bring our non-administrative users into AWS using a Managed AD instance in AWS Directory Services. Strictly speaking, we don't even need to import our user's accounts into the Managed AD environment in order to accomplish our goal. We can arrange for the Managed AD instance to perform lookups and binds against our on-premises AD forest using a trust. A trust allows two or more AD domains to authenticate against resources that are available in the other:

Figure 11.9 – A user signing in to an app through a domain trust

Consider the example in Figure 11.9. An AWS-hosted application that requires either AD or LDAP for user authentication or authorization is configured to look to an AWS Managed AD instance for user information. The Managed AD and the on-premises AD have a two-way trust: