Practical Path to Infrastructure as Code at Scale | Sean O'Dell

Explore the practicalities of Infrastructure as Code at scale, from overcoming common challenges to the future of IaC with Kubernetes, serverless computing, and cloud-native applications.

Key takeaways
  • Infrastructure as Code (IaC) is a good thing, but it’s not a silver bullet for all infrastructure management challenges.
  • AWS CloudFormation templates and Jenkins were not designed for infrastructure management, but Terraform was.
  • Terraform has limitations, such as lack of visibility and lack of support for multiple infrastructure providers.
  • Atlantis and TerraGrunt provide capabilities to improve IaC, but they don’t solve all the problems.
  • IaC is not just about infrastructure, it’s about the entire lifecycle of the application, including development, testing, and deployment.
  • The teams and silos issue is a common challenge in IaC, and it’s hard to overcome.
  • Open-source solutions like Terraform, Pulumi, and Ansible provide flexibility and cost-effectiveness.
  • The importance of security in IaC cannot be overstated, and it’s essential to have a robust security strategy in place.
  • The presentation of IaC to a non-technical audience can be challenging, but it’s essential to keep it simple and focused on the benefits.
  • The future of IaC is exciting, with advancements in areas like Kubernetes, serverless computing, and cloud-native applications.
  • The importance of empathy and understanding in the IaC space cannot be overstated.