Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

amplify push | Api update > CREATE FAILED

See original GitHub issue

I’m getting a ‘CREATE FAILED’ error when running amplify push. I updated my schema.graphql by adding more Object types and relations. The gql-compile was successful but the push then fails with the following output:

amplify --version 3.9.0

CREATE_FAILED      Action   AWS::CloudFormation::Stack Tue Oct 22 2019 14:39:20 GMT+0200 (SAST) S3 error: The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint. For more information check http://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html
CREATE_FAILED      Contact  AWS::CloudFormation::Stack Tue Oct 22 2019 14:39:20 GMT+0200 (SAST) S3 error: The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint. For more information check http://docs.aws.amazon.com/AmazonS3/latest/API/ErrorResponses.html
UPDATE_FAILED      Retailer AWS::CloudFormation::Stack Tue Oct 22 2019 14:39:20 GMT+0200 (SAST) Resource update cancelled                                                                                                                                                                                                                        
UPDATE_FAILED      Voucher  AWS::CloudFormation::Stack Tue Oct 22 2019 14:39:20 GMT+0200 (SAST) Resource update cancelled

Issue Analytics

State:
Created 4 years ago
Comments:6 (2 by maintainers)

Top GitHub Comments

4reactions

christodupreezcommented, Oct 26, 2019

I have solved the issue.

It was caused by moving the project to another folder and not updating the project’s route or name in /amplify/.config/local-env-info.json

To solve it open /amplify/.config/local-env-info.json and check projectPath

Thank you for all your help.

0reactions

github-actions[bot]commented, May 26, 2021

This issue has been automatically locked since there hasn’t been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels for those types of questions.

Top Results From Across the Web

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...

"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.

Update CloudFormation stacks stuck in ... - AWS

Short description. If your stack is stuck in the UPDATE_ROLLBACK_FAILED state after a failed update, then the only actions that you can perform ......

Amplify API - AppSync - CRUD (Create Read Update Delete)

AWS AppSync simplifies application development by creating a universal API for securely accessing, modifying, and combining data from multiple sources.

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" ......