In the governance section, the wrap up section references AWS Cognito, but I don’t think that was covered in the previous videos. Am I missing something?
I have the same too, this was not covered unless this is misunderstood as creating a role for an external user.
In this guide you will learn how to integrate your existing Cognito User Pool & Federated Identities (Identity Pool) into an Amplify project. This will enable your GraphQL API (AppSync), Storage (S3) and other resources to leverage your existing authentication mechanism. AWS Amplify is the fastest and easiest way to build cloud-powered mobile and web apps on AWS. Amplify comprises a set of tools and services that enables front-end web and mobile developers to leverage the power of AWS services to build innovative and feature-rich applications. With today’s Amplify CLI release, customers can re-use their existing Cognito resources for their Amplify project. Benefits: enable Amplify categories (API, storage, function etc.) for your existing user base incrementally adopt Amplify for your application stack independently manage Cognito resources while working with Amplify What we’ll learn: How to use your existing Cognito resource with the Amplify JS Library’s Authenticator UI component How to authorize your existing users to interface with a new GraphQL API How to use your existing Identity Pool to manage file storage authorization with S3 What we’ll build: A todo application backed by an existing Cognito User Pool. Every user gets to set their own profile picture only visible only to themselves. Pre-requisites: Install the latest Amplify CLI version Open terminal and run npm install -g @aws-amplify/cli to update to the latest Amplify CLI. Amplify CLI is already configured If you haven’t configured the Amplify CLI yet, follow this guide on our documentation page. Have an existing Cognito User Pool and Identity Pool Make sure your Cognito User Pool has at least two app clients with the following configuration: one app client without a client secret one app client with a client secret You’ll require an Identity Pool with the both of aforementioned User Pool app clients as an authentication provider in order to complete the storage integration showcased at the bottom of the article. AWS courses in Pune | AWS classes in Pune
I’ve just had a look, it appears that it isn’t covered in the exam section but as an extra resource – it means where you can add user sign-up and authentication to your mobile and web apps. Amazon Cognito also enables you to authenticate users through an external identity provider and provides temporary security credentials to access your app’s backend resources in AWS or any service behind Amazon API Gateway. Amazon Cognito works with external identity providers that support SAML or OpenID Connect, social identity providers (such as Facebook, Twitter, Amazon) and you can also integrate your own identity provider.
I have the same question