amplify push fails due to s3 permanent redirect
See original GitHub issueDescribe the bug
amplify push
fails due to s3 301’ing.
Interestingly in my case it reports The bucket is in this region: us-east-1
even though my project is configured to use eu-central-1
Amplify CLI Version
4.18.1
To Reproduce
This has happened a number of times to me and there is no discernable pattern to reproduce, other than adding some amplify services, pushing (it;ll succeed a few times) then add some more services or make say a schema change and then pushing again leads to the push failing.
Expected behavior
Push should succeed.
Screenshots
I see the following errors in the output:
UPDATE_FAILED GraphQLSchema AWS::AppSync::GraphQLSchema Thu Apr 30 2020 15:44:29 GMT+0200 (Central European Summer Time) The bucket is in this region: us-east-1. Please use this region to retry the request (
Service: Amazon S3; Status Code: 301; Error Code: PermanentRedirect; Request ID: 5B953F953E19A80F; S3 Extended Request ID: zeO6Y5i8RKA3MjEebgiDlJBfqRIibBMbuF+09j0Xa9eYzk5by7H09fNDaZ+QxoAMQHSJ++ilWJc=)
UPDATE_IN_PROGRESS GraphQLSchema AWS::AppSync::GraphQLSchema Thu Apr 30 2020 15:44:28 GMT+0200 (Central European Summer Time)
...
⠼ Updating resources in the cloud. This may take a few minutes...
UPDATE_ROLLBACK_IN_PROGRESS amplify-XXX-XXX-01215-apiamplifyDatasource-T9RSVPPKQ8Q4 AWS::CloudFormation::Stack Thu Apr 30 2020 15:44:30 GMT+0200 (Central European Summer Time) The following resource(s) fail
ed to update: [GraphQLSchema].
⠼ Updating resources in the cloud. This may take a few minutes...
UPDATE_ROLLBACK_IN_PROGRESS amplify-XXX-XXX-01215 AWS::CloudFormation::Stack Thu Apr 30 2020 15:44:34 GMT+0200 (Central European Summer Time) The following resource(s) failed to update: [apiamplifyDatasourc
e].
UPDATE_FAILED apiamplifyDatasource AWS::CloudFormation::Stack Thu Apr 30 2020 15:44:34 GMT+0200 (Central European Summer Time) Embedded stack arn:aws:cloudformation:eu-central-1:575024130701:
stack/amplify-XXX-XXX-01215-apiamplifyDatasource-T9RSVPPKQ8Q4/d46d94b0-8a66-11ea-850e-06b323d6b6e2 was not successfully updated. Currently in UPDATE_ROLLBACK_IN_PROGRESS with reason: The following resource(
s) failed to update: [GraphQLSchema].
Desktop (please complete the following information):
- OS: MacOS 10.14.5
- Node Version. 12.16.1
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:11 (3 by maintainers)
Top Results From Across the Web
Error Responses - Amazon Simple Storage Service
Error Code Description HTTP Status Code
AccessControlListNotSupported The bucket does not allow ACLs. 400 Bad Request
AccessDenied Access Denied 403 Forbidden
BucketAlreadyOwnedByYou 409 Conflict (in all...
Read more >Prevent AWS Amplify From Adding Trailing Slash and Forcing ...
I am using AWS Amplify and cannot figure out how to configure my rewrite and redirects or routes.js to prevent trailing slashes from ......
Read more >Hosting - Overview - AWS Amplify Docs
Deploy and host your app using either Amplify Console or Amazon CloudFront/S3. The Amplify Console offers fully managed hosting with features such as...
Read more >Troubleshoot HTTP 307 errors in Amazon S3 | AWS re:Post
When I send requests to an Amazon Simple Storage Service (Amazon S3) bucket, Amazon S3 returns a 307 Temporary Redirect response. Why am...
Read more >Redirect Rules for All; How to configure redirects for your static ...
In this post, lets walk through configuring redirect rules with your ... are given a status code of 301, which is a permanent...
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
For what it’s worth after I killed
amplify mock
that was running in a different tmux session the error disappeared.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.