TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Amazon AWS vs GitHub – “Suspected Unauthorized Activity”

10 pointsby arijitrajaabout 11 years ago

4 comments

codegeekabout 11 years ago
&quot;When we moved our Github repository from private to public (as the co-founder was leaving and I had to share it with some other prospective co-founders), the AWS keys were all in the open for everyone under the sky to play with. Doing some online search, I figured out we were not the only ones. It’s apparently quite a common mistake developers do.&quot;<p>Yes, Yes and Yes. I have made a similar mistake once on Github for a personal project, I realized my mistake and immediately updated the file and did a new commit. Guess what ? Even after committing a new version of the file, you can always check the &quot;History&quot; of the file which will show you the version with the credentials. My only option was to delete that config file completely.<p>Having said this, it can be scary if you leave your credentials on sites like Github. I work a lot with Python Flask framework and oen of the commonly used extension is Flask-Mail to send emails. Guess what ? A lot of developers are leaving their email credentials in the open and being a flask dev, I know that most of the time, it is MAIL_PASSWORD variable usually in a config file. Knowing this, I can just do a code search on github with keyword MAIL_PASSWORD. You figure out the rest.
评论 #7574796 未加载
评论 #7577361 未加载
res0nat0rabout 11 years ago
Another reason to always always always setup AWS billing alerts: <a href="https://aws.amazon.com/about-aws/whats-new/2012/05/10/announcing-aws-billing-alerts/" rel="nofollow">https:&#x2F;&#x2F;aws.amazon.com&#x2F;about-aws&#x2F;whats-new&#x2F;2012&#x2F;05&#x2F;10&#x2F;announ...</a><p>This can POST to a URL, SMS you, email you etc. Set a $ threshold you are comfortable with and enable this right away.
评论 #7574598 未加载
tedchsabout 11 years ago
The best practice with AWS API keys is to ONLY EVER use IAM (Identity and Access Management). There is nowadays zero reason to even generate account-level API keys. With IAM, you can create separate keys with separate abilities, down to the API call, even locked down to certain IP addresses. Even on my personal account I have separate IAM &quot;users&quot;, e.g. one for each S3 bucket that I use for backups, locked down to the minimum access needed for the backup software to work.
mathattackabout 11 years ago
I&#x27;ve heard the billing alerts elsewhere.<p>Seems like AWS did a great job of making things right in the end.