Our AWS Tech Bubble
Last weekend I was involved in a Twitter thread around this blog post.
AWS Lambda Security Best Practices
I think this is a very good blog post. It is concise, easy to follow, and the regular Open S3 Bucket Of The Week demonstrates the need to reiterate this material repeatedly. But you might ask while reading it, why would someone create a wildcard IAM policy? We know better...
I want to point out most of the readership of this email is highly engaged with AWS. We're a small self-selected minority of the tech world. While the example of wildcarding an IAM role may seem trivial, this stuff happens in the real world. If we forget the real world for the idealized world we're going to fail at making new adopters successful.
One of the moments in my career that played an important role in forming ServerlessOps was being at a DevOpsDays event in a non-major tech hub. I talked with two engineers who were excited to start adopting DevOps. For me that was a wakeup moment. People were just adopting practices, and excited about it, that I had been immersed in for about six years.
The realization that people were just adopting what I thought everybody knew was important for me to understanding there were still people out there to reach. That same realization extends to AWS adoption too. Keep in mind that not everyone lives and breathes the AWS world like we do.
I'm Tom from ServerlessOps and we provide services to make you successful with your DevOps transformation and enhancement through AWS serverless adoption. Ask us about our training and advisory services.
Also let us know what you think of this week's Cold Start using the 👍/👎 links at the end of this email!
Tom at ServerlessOps