5 ms·
"If someone gets access to your AWS access credentials, you’re in trouble." I know we're not supposed to post negative comments that don't "add value" to a dis
by developer1 11y ago
"If someone gets access to your AWS access credentials, you’re in trouble."
I know we're not supposed to post negative comments that don't "add value" to a discussion, but the only thing that comes to mind is "really?". Your setup is as secure as you make it. How you use your API access is up to you. Putting all your eggs in one basket is not insecure. This article doesn't actually bring to light anything important. There is no risk involved so long as you pay attention to what you are doing.
Any set of credentials, if leaked, destroys security. So... don't set yourself up to leak your credentials? I mean, come on, seriously?
*edit: I unfairly used the word "incompetent". Change to a phrase about paying attention to what you are doing.
- zippergz 11y agoPay attention to what you're doing, and never make a mistake. Or have anyone in your team/company make a mistake. While you're at it, please make sure you don't put any bugs in the code also. We're humans. We're imperfect. Sometimes a safety net isn't a bad thing.
- angrybits 11y agoExcept for the fact that you can explicitly contain the potential damage by controlling which accounts can do what. It's not like you have to have one god account with no MFA that has the keys to the city.
- snorkel 11y agoThis is easy advice to a single DevOp who completely controls their own AWS account, but often there is a team of devs and ops with elevated access to the same AWS account and not all of them understand AWS IAM access control, so they put admin level keys in their code. This article gives advice for mitigating the risk of access key leakage.