Skip to content
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

Closed
apiel51 opened this issue Jul 22, 2020 · 19 comments
Closed

Unable to delete Amplify backend environment #882

apiel51 opened this issue Jul 22, 2020 · 19 comments
Labels
archived This issue has been locked. backend-builds bug Something isn't working pending-prioritization Added to the backlog. Pending prioritization.

Comments

@apiel51
Copy link

apiel51 commented Jul 22, 2020

** 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?

@ganipcanot
Copy link

Can you share your appId/region?

Are you able to delete the baackend environment through the console?:

image

@apiel51
Copy link
Author

apiel51 commented Jul 22, 2020

Sure. App ID is d25h3g71gr2w1w region is us-west-2 . So I was able to delete the environment using the solution outlined here but I am now trying to reprovision an environment with the same name (start new) but the deleted environment (prod) is still showing up as an existing environment when trying to link a branch:
image

Where do the options from this dropdown come from?

@apiel51
Copy link
Author

apiel51 commented Jul 22, 2020

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 listBackendEnvironemnts. The response from this request is correct and only contains the two backend environments that still exist (dev and master). Perhaps this is some sort of caching bug? @ganipcanot

Update: Tried selecting "Create new environment" and using name "prod" and I get the same NoSuchBucket exception when attempting to deploy

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

@marlonmarcello
Copy link

marlonmarcello commented Jan 6, 2021

Having the same issue, and there is no useful error message at all.
The backend environment in question was automatically created by a PR Review. The PR was closed and deleted and now the backend is stuck and won't go away.

@sharmaadityaHQ
Copy link

I am also facing the same issue on Amplify Console. I am not able to delete the whole app or the backend environment on the following configuration:-

  • Region: us-east-1
  • App ID: dpjxh4jhr63k2

image

@gilvaju
Copy link

gilvaju commented Mar 9, 2021

I have the same issue here

image

image

I can't delete any app on admin panel. I already delete the entire stack and I still can't delete the apps

Region: us-east-2
App ID: djf1iamwbw9t8 , dsh8fgin8n8qt, dt0rmlwxgppn, d3porshd7yfvix, d104mdex2jh3pt

@cnbrkkaya
Copy link

I have the same problem.
Is there any progress?

@PabloLION
Copy link

I have the same problem.
Is there any progress?

@ganipcanot
Copy link

ganipcanot commented Nov 10, 2021

Have you tried the suggestion here: #1330 (comment)

Specifically: aws amplify delete-backend-environment --app-id <YOUR_APP_ID> --environment-name <THE_BACKEND_ENVIRONMENT_NAME>

@abhi7cr abhi7cr added the bug Something isn't working label Nov 11, 2021
@michaelbrewer
Copy link

@ganipcanot - this fixes it for me, but the AWS console should also do this

@Narrator
Copy link
Contributor

Narrator commented Dec 6, 2021

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

@michaelbrewer
Copy link

@Narrator - yes, this is what happened to mine. Using the aws cli seems to fix it.

@smoothness
Copy link

smoothness commented Dec 26, 2021

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.

@ocbrollingpaper
Copy link

ocbrollingpaper commented Dec 31, 2021

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 :)))

@danielqba
Copy link

no progress? same problem here!

@ghost ghost mentioned this issue Jul 27, 2022
@ZachMurray
Copy link

This is what worked for me.

open AWS CloudShell and run cmd: aws amplify delete-app --app-id <your_app-id>
you can find amplify app id at amplify app detail

Credit due:
https://stackoverflow.com/a/70894285/11705601

@ghost ghost added the pending-prioritization Added to the backlog. Pending prioritization. label Jun 14, 2023
@swaminator
Copy link
Contributor

We have since fixed this issue. Resolving.

Copy link

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

Copy link

This issue has been automatically locked.

@github-actions github-actions bot added the archived This issue has been locked. label Mar 20, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Mar 20, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
archived This issue has been locked. backend-builds bug Something isn't working pending-prioritization Added to the backlog. Pending prioritization.
Projects
None yet
Development

No branches or pull requests