-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to delete Amplify backend environment #882
Comments
Sure. App ID is Where do the options from this dropdown come from? |
Looking at the network requests it appears that they should be coming from a request to https://us-west-2.console.aws.amazon.com/amplify/api/amplify with an operation value of Update: Tried selecting "Create new environment" and using name "prod" and I get the same Update 2: Failed deploy created an S3 bucket that is displayed in the S3 console, but hit a 404 when trying to access or delete it |
Having the same issue, and there is no useful error message at all. |
I have the same problem. |
I have the same problem. |
Have you tried the suggestion here: #1330 (comment) Specifically: |
@ganipcanot - this fixes it for me, but the AWS console should also do this |
@apiel51 @marlonmarcello @sharmaaditya570191 @gilvaju @cnbrkkaya @PabloLION Could any of you please confirm if you attempted to delete the backends via CloudFormation first before attempting a delete via the AWS Console? Also, have you tried the workaround suggested here: #1330 (comment) and did that resolve your issue? We are currently unable to reproduce the issue correctly. I would really appreciate if any of you could provide detailed reproduction steps, so I can investigate this properly. |
@Narrator - yes, this is what happened to mine. Using the aws cli seems to fix it. |
Having the same problem for almost 2 months, there is no trace left of any resource that backs the Amplify projects anymore, no CloudFormation, no nothing, how it is possible that no one can fix this... so annoying. |
Same and I cant delete certificate for something I used :))) |
no progress? same problem here! |
This is what worked for me.
Credit due: |
We have since fixed this issue. Resolving. |
This issue is now closed. Comments on closed issues are hard for our team to see. |
This issue has been automatically locked. |
** Please describe which feature you have a question about? **
Deleting unused backend environment
** Provide additional details**
I'm trying to remove a deprecated amplify backend environment, but I am getting a "The specified bucket does not exist." error whenever I try to use
amplify pull
to pull the environment so I can delete it. I don't have any resources related to this environment (all deleted) but it doesn't seem like I can delete the environment itself. What's the best way to get around this?The text was updated successfully, but these errors were encountered: