4 ms·

> the average time from push-to-repo to AWS account compromise was 6 minutes. Wow, I didn't realize it had become so efficient, but I shouldn't be surprised.

> the average time from push-to-repo to AWS account compromise was 6 minutes. Wow, I didn't realize it had become so efficient, but I shouldn't be surprised. I never really understood the value in hosting non-public software in the public, and if it's open source, it shouldn't be getting anywhere near secrets that can be used to extract money from its developers. I remember thinking, back when it became trendy for people to upload their personal dotfiles to Github, that it would be a source of endless suffering. Who knows what information you're leaking in your ".profile" or ".bashrc"? Is that risk justified by the dubious benefit of storing your dotfiles on the internet for everyone to see, forever?

tjr225 7y ago
I had accidentally pushed an AWS credential out a month or two ago- within about a minute and a half AWS had disabled the IAM user, and automatically emailed me(as well as my entire org- how embarrassing!)- when we were going through the access logs it looked like it had taken only a minute and a half longer for some other, presumably malicious, system to attempt to access my compromised user. Probably between 2 or 3 minutes total. I'm not a huge Amazon fan but props to AWS for saving my butt.
- scarface74 7y ago
  Why have credentials anywhere outside of the .aws directory in your home directory? When developing locally all of the SDKs will read them from there and when deploying to AWS, the SDK will get them from the attached role.
  - tjr225 7y ago
    I understand what the best practices are, it was a total mistake- I never even intended to push what I did to github.
    - house9-2 7y ago
      `git diff` before making a commit `git log` and `git show` before pushing to a remote These 2 simple things have saved me on more than one occasion.