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?
Related
We need to create gcp resources with terraform, but we are stuck at the terraform init stage while terraform tries to authenticate to gcp. We have already configured our backend and obtained our service account key but minifying (removing the extra lines in credential json file) the credential json and exporting to GOOGLE_CREDENTIALS, doesn't work. How are you setting this value?
If you are in a local and controlled environment you can use GOOGLE_APPLICATION_CREDENTIALS and set it with the path to the JSON key file. But as discussed key files are bad practices security wise. An alternative is to authenticate using gcloud auth application-default login and you dont have to deal with key files.
Another alternative is to use Google Cloud Shell which is already setup with the credentials of the authorised user opening the session.
Finally for automated pipeline you can use Google Cloud Build where processes will be run using the authentication and the authorisation of the service account used by Cloud Build
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
I recently "Created a new Access Key" for my AWS Amplify IAM user, and disabled the old key. I also changed how I was authenticating to AWS (using an IAM user now instead of previously a SSO Federated user).
Now when I run something like:
amplify api push
I get:
InvalidAccessKeyId: The AWS Access Key Id you provided does not exist in our records.
I tried re-running:
amplify configure
I used aws configure to set the new Access Key to the default profile, but still no luck.
How can I resolve this?
I ended up checking local-aws-info.json in the amplify/config directory and noticed that the "useProfile" and "profileName" keys weren't accurate anymore.
To fix I ran:
amplify configure project
And once that finished, I ran:
amplify pull however, this was probably only necessary due to the hacking around I did trying to fix the error originally.
I had several issues while working through this workshop including
a. AMAZON REKOGNITION not working,
b. dynamodb tables not updated with images being uploaded.
To avoid getting charged for aws resources, I deleted all the AWS resources using amplify delete command. If I run the amplify publish command, I get the following error:
**StackTrace:**
You are not working inside a valid amplify project.
Use 'amplify init' in the root of your app directory to initialize your project with Amplify
Error: You are not working inside a valid amplify project.
How can I recreate all the AWS resources without going through the amplify init process again?
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