yarn init -ygit init
Amplify tries to be very invested in your project, editor, and more (which, tbh, is super annoying and makes it hard to tell which question will lead to what effect). We don't care about any of this really because the only thing we're using amplify for is easy cognito setup.
➜ amplify add authUsing service: Cognito, provided by: awscloudformationThe current configured provider is Amazon Cognito.Do you want to use the default authentication and securityconfiguration? (Use arrow keys)❯ Default configurationDefault configuration with Social Provider (Federation)Manual configurationI want to learn more.How do you want users to be able to sign in?UsernamePhone NumberEmail or Phone NumberI want to learn more.Do you want to configure advanced settings?❯ No, I am done.Yes, I want to make some additional changes.
It gives us two options for next steps
Some next steps:"amplify push" will build all your local backend resources and provision it in the cloud"amplify publish" will build all your local backend and frontend resources (if you have hosting category added) and provision it in the cloud
➜ amplify push✔ Successfully pulled backend environment dev from the cloud.Current Environment: dev| Category | Resource name | Operation | Provider plugin || -------- | ----------------------- | --------- | ----------------- || Auth | cbsubscriptions4d05cfea | Create | awscloudformation |? Are you sure you want to continue? (Y/n)
Y you get to wait a few minutes (mine just took >3m) and see a lot of cloudformation output.
In the amplify service section of the AWS console you will now see your project. We don't really care about this area at all and care much more about the cognito user pool that is now in the cognito services area with our project name.