I'm setting up my first amplify project for a JS app, working through the getting started documentation here. After running amplify add auth and configuring a new cognito user pool, with no problems, and running amplify push with no problems. I cannot find the new cognito pool anywhere in the AWS console. I've looked through every region, and I've tried logging in to the console as my amplify IAM user, and I see nothing – both in the cognito section or cloudformation section.
So... where is it? Has it not been created yet? Do amplifty user pools not appear in the console?
Bob,
Kindly check your Amplify logs to see what has really happened. If configuration and provisioning are successful, Amplify will write the configurations in aws-exports.js. if you cannot find the file, simply fire > grep "userPoolId:" . -r
Robin
Related
I have total 600 users in the aws congnito user pool in my old aws account , and i want to move/migrate all the users to my new aws account. It is possible to migrate aws congnito users from one aws account to another.
Please Help Me.
I checked through every document linked to Congnito, but I was unable to find a document for moving Congnito users between AWS accounts.
You should consider to use cognito-backup-restore npm tool. It's easy to use and oriented to What you require, but there are some important points to take into account:
You need the AWS CLI and security credentials installed and well configured locally, preferably use IAM roles to access Cognito.
You're backing up users from Cognito user pool to a JSON file locally, so do it in a safe environment and remove the file after restoring the backup.
There is no way of getting passwords of the users in Cognito, so you may need to ask them to make use of ForgotPassword to recover their account.
I needed to re-do my Amplify auth from scratch. There were some Cognito custom attributes that are not removable once created and since this is going to production, I wanted a clean slate.
The problem started after running amplify remove auth hit a snag as my User Pool contains a Cognito domain.
Because of that the process never finishes and I had to abort the CLI process. I removed Cognito domain and re-ran and seemed OK, but CloudWatch says UserPool is still unable to be removed. I then removed it manually via AWS console.
Question
I'm not sure if aborting the CLI process caused this to hang but I'm seeing some leftover resources not removed from the console - e.g. CloudFormation stacks, Lambda applications and Log Groups (see pics).
Since this is going to be production environment, I'm wanting to ensure the previous auth resources are properly removed. How can I ensure that?
When I go to Amplify backend page, the Authentication just hangs and keeps on loading and console shows a weird error. Note, I've not done amplify publish. Is this a normal behaviour?
Currently my amplify project has the API, Authentication, File Storage and Functions categories. Everything works perfectly fine until I add Analytics!
I am having the following error when I add analytics to my amplify project in react native and try to push GraphQL changes by performing amplify push:
Failed to create models in the cloud: Modelgen job creation failed
Everything is actually on the same AWS-Region, which is us-east-1.
Many suggests on the web that it's an issue that comes from the credentials that I am using, I verified numerous times and it is not, my amplify credentials and config file are perfectly matching AWS credentials. My aws_access_key_id, aws_secret_access_key and region from the credentials and config file are aligned with amplify user.
I also verified my user IAM permissions, and it has the following one :
AdministratorAccess
AdministratorAccess-Amplify
AmazonMobileAnalyticsFullAccess
When I revert my changes, by removing Analytics from my project using amplify remove analytics I am not having that error anymore when I push GraphQL changes.
Anyone has an idea what could be causing this error?
I want to do automatic user provisioning for AWS SSO and G-Suite, for this, I am using SSOSync. here when I'm going to use AWS Serverless Application Repository but it is showing the following error.
You are not authorized to perform: serverlessrepo:GetApplication.
I gave full permissions to users but it seems like this application is not maintained longer. Do we have another alternative option for doing auto user provisioning?
Try this: https://github.com/slashdevops/idp-scim-sync . The app you are requesting no longer exists.
I am following this tutorial for creating a React app in AWS.
In step Initialize the Amplify app of section 3, I see the following error (i.e. Setting up Admin UI failed.) in the Backend environments tab:
I know that I have a limited account from our administration side, but I don't know what role is missing that I cannot create the backend for my app!
Does anyone have any idea that, how I can find out what role is missing that I am not allowed to create the Amplify Backend?
Also in the console tab no info is printed.
I had the same problem when I tried to deploy from the Admin UI sandbox app, as a ROOT user on my AWS account. I fixed it after I went to Billing and completed the payment info requirements.
Before that I couldn't even access DynamoDB tables (which are used by AWS Amplify and Admin UI).
If this doesn't work, you can try having Amplify and maybe DynamoDB related roles enabled in IAM for your user.
You can start with these roles:
AdministratorAccess-Amplify
AmazonDynamoDBFullAccess