Capital One Says Breach Hit 100M Individuals in U.S

Re:Capital One Says Breach Hit 100M Individuals in U.S by scarface74 on Monday July 29, 2019 @10:52PM (#20561727)

It doesn’t matter. There is never a reason for credentials to be anywhere near your repository. If you’re running locally, you should have your credentials in your home directory (via aws configure). If you are running your code on AWS either on an EC2 instance, lambda, or Docker you should be using the role associated with the execution environment.

Every SDK that I have used let’s you use a constructor without a parameter and can get your credentials from the config file/role.

[ Parent | on HN ]

Re:Capital One Says Breach Hit 100M Individuals in U.S by samstave on Monday July 29, 2019 @11:42PM (#20561971)

i know, this was a few years ago, and these types of practices were still being developed out in the greater community (lambda didnt exist yet, dockeer was still nascient etc)

[ Parent | on HN ]

Re:Capital One Says Breach Hit 100M Individuals in U.S by acdha on Tuesday July 30, 2019 @07:45AM (#20563934)

I’m sympathetic in that a lot of people started learning this on the fly but that was widely recognized as bad practice even before Amazon was founded and various patterns for doing it right were widely established.

(If anyone needs me, I’m busy feeling old after remembering having this conversation with a new PHP developer in 1998)

[ Parent | on HN ]

Re:Capital One Says Breach Hit 100M Individuals in U.S by samstave on Tuesday July 30, 2019 @09:49AM (#20564794)

Haha, agreed...

He was a remote worker and aparently had a poor handler on our end. I was head of ops not in dev, so i just had to deal with the fallout.

[ Parent | on HN ]