.webp)
HashiTalks: Israel
Our talk: Bootstrapping a secure AWS environment? Terraform to the Rescue!
It's been 20 years since EC2 landed, and we've learned quite a bit about managing cloud operations at scale over these years. One area that remains a real pain point is securing AWS environments (a lot of moving parts and controls to think about), this is particularly acute in the world of fast-paced engineering today.This talk will give an overview of how to secure AWS architecture through code, leveraging Terraform for automation, or your IaC of choice. This will take a look at good security practices for managing your AWS organization - from the dedicated accounts per user, switching roles for additional access, enforcing MFA, segregation of different account types - dev vs. staging vs. prod, as well as SCP policies. In addition we will review best practices for working locally and deploying code changes to your SCM (with a Github example) without compromising your AWS keypairs, and all this with an everything-as-code approach built with Terraform.
Agenda
You cannot detach engineering processes and culture from the infrastructure.In this talk we will share from our experience of supporting and managing serverless production environments. We will discuss the not-so-obvious way it differs from managing other more common modern infrastructures and the impact it has on the operations methodology. we will discuss how it influences the developers day to day work and lessons learned.
Let's face it - now that we're a few years past the whole "shift left" trend, we can honestly say it has largely failed when considering security debt. Instead of solving issues earlier in the cycle, which was at the premise of the “shift left” promise, we mostly shifted the problem left. To date, security has largely been a source of friction between development and security teams––and fostering a proactive security culture among developers is still the holy grail a lot of companies are dreaming about without really managing to reach it. That's because this mindset needs a hard reset. We need to look at security completely differently. Security should not and cannot be decoupled from product quality - notably because developers are measured on code quality and velocity and not on how secure their code is. In the same way that our product's usability is a first-order engineering concern, security should be regarded in the exact same way. In this talk, I'll share some lessons learned and the way to bridge the gap between security and engineering, by changing the way it is viewed and implemented in current processes.
%20(1).webp)
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna