Skip to content
This repository has been archived by the owner on Apr 19, 2023. It is now read-only.

Unable to deploy/update backend via Amplify console #216

Closed
subtlegiant opened this issue Mar 10, 2021 · 2 comments
Closed

Unable to deploy/update backend via Amplify console #216

subtlegiant opened this issue Mar 10, 2021 · 2 comments

Comments

@subtlegiant
Copy link

Deployment of my backend fails after adding VOD. Everything works fine in my dev environment but after pushing my branch to be deployed, I get the following errors:

2021-03-09T14:34:37.588Z [INFO]: UPDATE_FAILED rS3InputBucket AWS::CloudFormation::Stack Tue Mar 09 2021 14:34:37 GMT+0000 (Coordinated Universal Time) Embedded stack arn:aws:cloudformation:xx-xx-xxxxxxx:stack/amplify-xxxxx was not successfully updated. Currently in UPDATE_ROLLBACK_IN_PROGRESS with reason: The following resource(s) failed to update: [UploadPolicy].
2021-03-09T14:34:37.756Z [INFO]: 
2021-03-09T14:34:37.756Z [INFO]: UPDATE_ROLLBACK_IN_PROGRESS arn:aws:cloudformation:xx-xx-xxxxxxx:stack/amplify-xxxxx AWS::CloudFormation::Stack Tue Mar 09 2021 14:34:33 GMT+0000 (Coordinated Universal Time) The following resource(s) failed to update: [UploadPolicy].
2021-03-09T14:34:37.863Z [INFO]: 
2021-03-09T14:34:37.863Z [INFO]: UPDATE_ROLLBACK_IN_PROGRESS arn:aws:cloudformation:xx-xx-xxxxxxx:stack/amplify-xxxxx AWS::CloudFormation::Stack Tue Mar 09 2021 14:34:34 GMT+0000 (Coordinated Universal Time) The following resource(s) failed to update: [S3AuthGet].
                                 UPDATE_FAILED               S3AuthGet                                                                          AWS::IAM::Policy           Tue Mar 09 2021 14:34:33 GMT+0000 (Coordinated Universal Time) The role with name NONE cannot be found. (Service: AmazonIdentityManagement; Status Code: 404; Error Code: NoSuchEntity; Request ID: 811752cf-9072-4a59-b3d2-e7eb318e48ef; Proxy: null)
@subtlegiant
Copy link
Author

Hello,

Any help with this would be appreciated. Permissions seem to be correct, but looks like they may not have propagated properly to CloudFormation.

@subtlegiant
Copy link
Author

Was able to fix this by recreating the backend from scratch. Still unsure if this was an issue on my end or a bug.

# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant