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

Creating an Amazon Cognito identity pool

Since we now have a user pool that can provide federated identities, we can create an identity pool. Doing so will allow the federated identities from that user pool to access AWS resources. To do this from the Management Console, follow these steps:

Go to the Amazon Cognito service and select Manage Identity Pools.
Since we have no existing identity pools, we are taken directly to the wizard to configure our first one. Let's call this one rbiidentitypool:
Figure 5.51 – Naming the new identity pool
An interesting capability of identity pools is that they allow unauthenticated users to obtain temporary credentials to access AWS resources. It may seem counterintuitive to permit this, but there may be use cases where access to a resource, such as placing a file into a bucket or adding an entry into an Amazon DynamoDB database, may be deemed so sufficiently low risk that identifying principals taking these actions may...