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

Unexpected large spend with ConstructHub #918

Open
ali4579 opened this issue Jun 28, 2022 · 7 comments
Open

Unexpected large spend with ConstructHub #918

ali4579 opened this issue Jun 28, 2022 · 7 comments
Labels
bug Something isn't working effort/epic More than 1 week p1

Comments

@ali4579
Copy link

ali4579 commented Jun 28, 2022

What is the URL of the page with the issue?

No response

What did you do?

I deployed construct hub with default settings

What did you expect to happen?

Cost < $100 a day

What actually happened?

It behaved as expected for 7 days and then over a period of approximately 24 hours it spent $10,000 and then went back to normal spend.

Web Browser

No response

OS

No response

Other information

I accept responsibility for the charges - I deployed a project with defaults and didn't pay enough attention to it, plus I wasn't paying attention to my budget alerts!

I have spent some time looking at what happened and I understand some but not all. It was a test stack and I'll be deleting it, but before I do delete it, I was wondering if you are interested in knowing what happened or if you want any information from me.

I haven't attempted to reproduce!!

@ali4579 ali4579 added the bug Something isn't working label Jun 28, 2022
@RomainMuller
Copy link
Contributor

I'd be curious to know what service(s) was/were part of that $10K charge... I have some suspicions here, but I'd like to confirm them...

@ali4579
Copy link
Author

ali4579 commented Jul 19, 2022

So sorry, didn't see there had been a reply. I will get back to you with that info asap

@chris-bateman
Copy link

Was there anymore to this?

@mrpackethead
Copy link

Very curious to know about this.

@ali4579
Copy link
Author

ali4579 commented Oct 18, 2022

Hi Everyone

So sorry, there never seems to be enough time in the day to get back to this!

Looking at cost explorer, we see
June 21st
EC2 Other - $1887.97
Config - $731.11
ECS - $592.18
Step Functions - $86.87
Lambda - $36.19

June 22nd
EC2 Other - $3,481.24
Config - $1,457.37
ECS - $1,032.03
Step Functions - $128.91
Lambda - $27

All the cloudwatch data is still there, I'm just not 100% sure what I'm looking for. I can see tends of thousands of fargate executions. Am happy to go hunting for anything you think would be useful or we can possibly hop on a call, I'm in GMT+8

Ali

@rix0rrr
Copy link
Contributor

rix0rrr commented Oct 19, 2022

Our default setup does something silly: periodically regenerate all documentation in case the doc generator has changed in the mean time.

I would recommend disabling that altogether.

@ryparker ryparker added p1 effort/epic More than 1 week labels Dec 22, 2022
@mrgrain
Copy link
Contributor

mrgrain commented Aug 28, 2024

This PR #1392 greatly reduced the number of StateMachine executions and thus cost. However the general issue that the cost of the system depends on npmjs.com still stands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working effort/epic More than 1 week p1
Projects
None yet
Development

No branches or pull requests

7 participants