5 ms·
Is it really on the web service companies to make sure you (the developer) don't do anything stupid? The article author could have avoided a lot of headache if
by Alupis 11y ago
Is it really on the web service companies to make sure you (the developer) don't do anything stupid?
The article author could have avoided a lot of headache if he simply checked the repo before walking away. Red flags should have gone up as soon as he received the first weird Amazon messages, but he still didn't think to check his own work.
The author calls this a "Data Breach" but in reality it was a "Data Leak".
- RussianCow 11y agoAmazon would save some money by doing this, since they usually reimburse "victims" of public AWS keys (at least on the first instance) and eat the cost.
- spdionis 11y agoThey don't "reimburse" anything. They only cancel the due amount. The only thing they lose is their wasted computing power (and some support costs) and I think the RAW computing power is very cheap to them, especially considering their scale. The cost in terms of support for the victims is probably bigger but still not significant.
- RussianCow 11y agoIt's still a cost that could be mitigated with a couple hours of someone's time.
- mhuffman 11y agoMaybe not, but it think it is the web service company's responsibility to alert and contact you on suspicious activity ... like a sudden $6,000 jump in service usage of spot instances in regions you have never used before. I mean a quick automated email would be enough for you to take action. The way it is set up now, you pay for it and humbly beg Amazon to deduct those charges if they see fit.
- Alupis 11y agoI agree, and it seems this sort of thing is already in place on AWS, but the author didn't heed the first two warnings. Short of just blocking things from happening and risking inconveniencing other customers, I don't see much more AWS could have done that would be reasonable.
- runamok 11y agoYou can easily set up billing alerts in cloudwatch to do this. I have done so. I agree by default it should prompt you to do so during the aws on boarding process.
- onion2k 11y agoIs it really on the web service companies to make sure you (the developer) don't do anything stupid? Yes. The web service company should look at it as basic security - if people are using their service to discover private information and use it to defraud their users, even if the users have been stupid enough to upload that information publicly, the company should do what they can to mitigate the problem. If I post a photo of my credit card on Twitter I would expect my bank to limit the damage as much as possible by declining obviously fraudulent transactions. Ultimately it's my own fault, and I would be liable for the costs, but that doesn't mean the bank should just let it happen if they can do something to stop it.
- 15155 11y ago> mitigate the problem. This seems like very minor engineering effort on behalf of GH - simple regexes, even.
- onion2k 11y agoTo detect the key, sure. But then there's the interface design to inform the user, hooking in to an email to notify the user if they're committing via git, a system to disable the option if necessary, monitoring the AWS format in case it changes, dealing with other formats that are requested by AWS's competitors, and so on. I don't think this would be a minor undertaking or simple in any way, but it is important enough that a provider (and target) the size of GitHub should still do it.
- alkonaut 11y ago> Is it really on th web service companies [...] Yes. Or, it's not so much a responsibility as it is an opportunity. I'd choose the provider that stops me from shooting my foot. I assume AWS has spending caps for each account. My credit card company blocks my card and calls me if I spend in a suspicious pattern. And so on.
- tolmasky 11y agoGitHub is a service. Its not their job to offer me issue tracking, or pull requests, or really much of anything. They CHOOSE to offer me things, and if those things are interesting, I CHOOSE to pay them. As users, we can certainly declare that we believe AWS key detection to be of foundational importance to a code sharing community, and signal them to thus take action or risk losing us as paying customers. I would certainly feel better if this was a feature, given its apparent ease of implementation and huge head aches it would solve.
- Fomite 11y agoGitHub is a value added service. Making sure I don't do something stupid and expensive is a value add.
- pbreit 11y agoIt's not "on" them but it would behoove them to perform better than this tale suggests. And they are not doubt capable of such. Or just waive the charges.
- nsxwolf 11y agoThere's a huge amount of value in a service that insulates you from mistakes like this. You really, really have to know what you're doing with EC2 because it is a loaded gun. Personally, I don't like using things that are covered in spring loaded booby traps that require eternal hypervigilance in order to avoid nasty financial consequences. Certainly not when deploying something that would be right at home on something like Heroku.
- Alupis 11y ago> You really, really have to know what you're doing with EC2 because it is a loaded gun. That's a fair point, but keep in mind the article author was given several warnings that something was wrong, but failed to correct the problem each time (which resulted in the huge bill he ultimately received). At what point is the responsibility on the author here?
- chrismcb 11y agoThe author deleted the old key and created a new one and changed his password as soon as he was notified. How did he fail to correct the problem? What else should he have done?
- koffiezet 11y ago> The article author could have avoided a lot of headache if he simply did not check in secrets into any source control system. FTFY It baffles me that people actually do this. Passwords and secrets DO NOT BELONG THERE. Even your 'if he simply checked the repo' statement is in my view completely crazy. No you should not have to worry about that, because that should not be there at all. Leaking your source-code should not result in a system-breach at any point.