News for hackers. Stuff that matters.
Re:On Internal Engineering Practices at Amazon by throwaway1280 on Tuesday March 26, 2019 @04:58PM (#19495961)
Speaking of twitchy lawyers and Move to AWS... one of the weirdest things we had to deal with inside Amazon was that, for many years after AWS launched, we weren't allowed to use it because it "wasn't secure enough".

Given that we were actively shopping it around to major financial institutions at the time, doesn't that strike you as particularly hypocritical? :)

Re:On Internal Engineering Practices at Amazon by Hamuko on Tuesday March 26, 2019 @05:32PM (#19496226)
So wait, when I need to convince customers why AWS is secure for their data, I can't say "It's good enough for Amazon!"?
Re:On Internal Engineering Practices at Amazon by jtoberon on Tuesday March 26, 2019 @09:20PM (#19497443)
To clarify, an AWS customer has a shared responsibility to describe the security of their systems including how they use AWS tools, and in this respect Amazon is no different than other AWS customers.
Re:On Internal Engineering Practices at Amazon by umanwizard on Wednesday March 27, 2019 @02:01AM (#19498469)
GP's comment may have been true at one point, but AWS is extremely mainstream within Amazon now and has been for several years.
Re:On Internal Engineering Practices at Amazon by anth_anm on Tuesday March 26, 2019 @08:23PM (#19497169)
No, you can say hey amazon might use this if they do a security evaluation first.

It's totally cool for your data though, don't worry about it.

Amazon fucking sucks at dogfooding.

Re:On Internal Engineering Practices at Amazon by andrewguenther on Wednesday March 27, 2019 @01:19PM (#19503222)
This is misleading. This had more to do with internal audit tools and guardrails available than it did the services themselves.
Re:On Internal Engineering Practices at Amazon by amznthrowaway2 on Tuesday March 26, 2019 @05:03PM (#19495993)
It's still highly restricted for many teams working with customer data