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

my broken deployment issue is going to cost me $2300 this month and wont delete! HELP #13775

Open
2 tasks done
contractorwolf opened this issue May 12, 2024 · 7 comments
Open
2 tasks done
Labels
pending-triage Issue is pending triage

Comments

@contractorwolf
Copy link

How did you install the Amplify CLI?

npm

If applicable, what version of Node.js are you using?

18

Amplify CLI Version

details on previous ticket

What operating system are you using?

mac

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

just trying to delete the project. have backed up the dynamodb using a different s3 bucket and was using the aws amplify console to delete the backend services before deleting the project

Describe the bug

I have a previous issue deploying here:
#13398

I tried a bunch of their suggestions but nothing seemed to unstick the deploymment. I even had AWS 2 engineers trying to help me. This is a fun side project, not a money making project and it has run costing me ~$40 a month for a few years. 6 months ago a deployment got stuck and I could no longer deploy, but the site still worked so it wasnt a big deal. AWS Engineers looked for a bit (2 hours on the phone) with me but then needed to regroup because they couldnt figure it out. Here we are a few month later and i looked at billing and last month cost me $900 (its hitting lots of errors and logging a ton now) and this month has already cost me $889 and is projected to cost me $2300. I backed up the data to s3 and decided to just delete the project backend first. It WONT DELETE!!!!

Screenshot 2024-05-12 at 2 25 50 PM

please help, i cant afford to pay $2300 a month for a silly project that i made a few years ago.

Expected behavior

I should be able to delete the aws amplify backend using the existing tools for aws amplify

Reproduction steps

I am just trying to delete a backend aws amplify service using the console and my deployment issue seems to also be blocking my deletion

Project Identifier

No response

Log output

# Put your logs below this line


Additional information

No response

Before submitting, please confirm:

  • I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
  • I have removed any sensitive information from my code snippets and submission.
@contractorwolf contractorwolf added the pending-triage Issue is pending triage label May 12, 2024
@contractorwolf
Copy link
Author

Screenshot 2024-05-12 at 2 36 03 PM

@biller-aivy
Copy link

Go to cloudformation and delete the Projekte there. But better would be to check in cost editor what it is and delete or stop the Ressource which is called recursively maybe

@contractorwolf
Copy link
Author

Screenshot 2024-05-12 at 5 06 31 PM

@contractorwolf
Copy link
Author

as it turned out those were the same issues I was dealing with trying to deploy it for 8 months wouldnt allow me to delete it either. Was getting stuck on some IDP thing that I eventually just decided to go nuclear and delete. I was finally able to delete the whole project :/

@contractorwolf
Copy link
Author

this is the same issue i was hitting:
#2096

@josefaidt
Copy link
Contributor

Hey @contractorwolf 👋 thanks for raising this and sorry to hear of the rough experience!! Were you able to successfully delete the project in its entirety?

@josefaidt josefaidt added the pending-response Issue is pending response from the issue author label May 22, 2024
@contractorwolf
Copy link
Author

yeah but I am still working through the process to get the charges removed

@github-actions github-actions bot removed the pending-response Issue is pending response from the issue author label May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pending-triage Issue is pending triage
Projects
None yet
Development

No branches or pull requests

3 participants