amplify push fails
See original GitHub issueDescribe the bug We follow the tutorial exactly and it results in an error.
To Reproduce Steps to reproduce the behavior:
npm i -g @aws-amplify/cliamplify configureamplify initamplify add authamplify push
Expected behavior Amplify will be configured without na error.
Screenshots If applicable, add screenshots to help explain your problem.
$ amplify push
| Category | Resource name | Operation | Provider plugin |
| -------- | --------------- | --------- | ----------------- |
| Auth | cognito73548268 | Create | awscloudformation |
? Are you sure you want to continue? Yes
⠴ Updating resources in the cloud. This may take a few minutes...
UPDATE_IN_PROGRESS webv3-20181213091931 AWS::CloudFormation::Stack Thu Dec 13 2018 10:07:33 GMT-0800 (PST) User Initiated
CREATE_IN_PROGRESS authcognito73548268 AWS::CloudFormation::Stack Thu Dec 13 2018 10:07:38 GMT-0800 (PST)
CREATE_FAILED authcognito73548268 AWS::CloudFormation::Stack Thu Dec 13 2018 10:07:39 GMT-0800 (PST) Template format error: Unrecognized resource types: [AWS::Cognito::UserPool, AWS::Cognito::IdentityPoolRoleAttachment, AWS::Cognito::UserPoolClient, AWS::Cognito::IdentityPool]
UPDATE_ROLLBACK_IN_PROGRESS webv3-20181213091931 AWS::CloudFormation::Stack Thu Dec 13 2018 10:07:40 GMT-0800 (PST) The following resource(s) failed to create: [authcognito73548268].
⠏ Updating resources in the cloud. This may take a few minutes...Error updating cloudformation stack
✖ An error occurred when pushing the resources to the cloud
Resource is not in the state stackUpdateComplete
UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS webv3-20181213091931 AWS::CloudFormation::Stack Thu Dec 13 2018 10:07:55 GMT-0800 (PST)
DELETE_COMPLETE authcognito73548268 AWS::CloudFormation::Stack Thu Dec 13 2018 10:07:57 GMT-0800 (PST)
UPDATE_ROLLBACK_COMPLETE webv3-20181213091931 AWS::CloudFormation::Stack Thu Dec 13 2018 10:07:57 GMT-0800 (PST)
Issue Analytics
- State:
- Created 5 years ago
- Reactions:6
- Comments:29 (12 by maintainers)
Top Results From Across the Web
amplify push - An error occurred when pushing the resources ...
When I use amplify cli version 4.36.0, I do not get error for the same changes to the backend. Its one of later...
Read more >Project-level configurations - Troubleshooting guide
If amplify push fails, check the CloudFormation event logs for the failing resource to get detailed information to fix the issues in the...
Read more >Troubleshoot CloudFormation stack issues in AWS Amplify
When I try to deploy my AWS Amplify application, I receive an AWS CloudFormation error similar to the following: "Resource is not in...
Read more >"amplify push function" error: Resource is not in the state ...
CloudFormation tells me that resource update failed because of: Embedded stack arn:aws:cloudformation:::stack/amplify----api-/ was not successfully updated.
Read more >Amplify API key not found - ArturoFM
When this happens? When you push to an existing environment to update the api, you get an error saying "API key not found" ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Region can be the cause of the issue too. Check here for more information.
We solved our issue for this. Apparently, our account was limited because a while back one of our devs exposed one of our API keys on Github. We worked with AWS billing support to resolve the limited status on our account.