In this section we will walk-through how-to setup the Cognito User Pool that will be used by your application. The user pool will be where all of your users will be stored. This will give you the ability to have your users authenticate into our application.
To begin setting up your Cognito User Pool navigate to the Cognito service in the AWS Console of your Event Engine account. You will then see the Cognito landing page pictured below.
Click the Manage User Pools button. You will see screen below.
Click the Create a user pool button, and you should see the screen below.
The first thing you do is give your user pool a “Pool name”. After you have entered a pool name click the “Step through settings” button.
Next you will setup the user pool attributes. For the user pool attributes select the options that you see in the image below.
Click the “Next step” button at the bottom of the screen.
For the “Policies” you can leave the default values that you see on this screen.
Click the “Next step” button at the bottom of the screen.
For “MFA and verifications” select the options that you see in the screen below.
Click the “Next step” button at the bottom of the screen.
In this workshop we will not be using SES to send out emails. If you wanted to use your own email address to send out emails you could configure SES (Simple Email Service) to accomplish this. For the sake of simplicity, you will leave the below fields blank.
For the other options you see in the image below you can leave the default values. If you would like you can customize your message to your users here. Don’t make changes to the options in brackets since these are placeholders that Cognito uses to dynamically fill in message information such as username and temporary passwords.
After you have completed this form click the “Next step” button at the bottom of the screen.
On the next screen if you would like you can add tags to your user pool. For the workshop we will leave tags blank.
Click the “Next step” button at the bottom of the screen.
For the user device options below screen below leave the default value of “No”. If you were building an application where you wanted to track the devices users log in from you can give them the option “User Opt In” or you could always choose to track devices users log in from.
Click the “Next step” button at the bottom of the screen.
On the next screen we will setup the app client. By configuring the “app client” you are setting up the ability for an application to connect to your user pool. In this workshop we will be connecting to the user pool via the JavaScript SDK. On the screen you see below click the “Add an app client” link.
You should then see the following screen.
You will start giving your app client a name.
For the Refresh token expiration, Access token expiration, and ID token expiration you leave the default values for the workshop. If you wanted the tokens to expire before the default time-frames you can always come back and make changes.
Note: Be sure to uncheck "Generate client secret". Since you are running your code on the client-side you will not use this option. If your code was running on the server-side where users wouldn't have access to view your code you could use this option.
Next click the "Create app client" button.
For the auth flow settings be sure you select the third checkbox option, Enable username password-based authentication (ALLOW_USER_PASSWORD_AUTH)
This setting allows users to log into your Cognito user pool via username and password. If this option is not selected you will receive an error when you code call the authentication method.
For this section you will leave the default value.
Finally click the “Create app client” button before click the “Next step” button. After your app client has been create click the “Next step” button.
You will now see the following screen after you have created your app client. Click the "Next step" button.
For the triggers you will not be using them for this workshop. If you needed to add things such as custom logic for pre-authentication, pre-signup, post authentication, or post account confirmation you would configure those triggers here to initiate lambda functions.
A good example of taking advantage Cognito triggers are after a user confirms their account you could have default user settings record created in a backend database.
Since you will not be using triggers in this workshop you can click the “Next step” button at the bottom of the screen.
You should now see a screen similar to the image below with the “Pool name”, and the options that you select as you configured the user pool. Once you are satisfied with the options you have selected for your user pool click the “create pool” button.
Once your user pool has successfully been created you will see a screen similar the image below.
Now that you have setup your Cognito User Pool you will configure your application to use the user pool.