From Infrastructure as Code to Environment as Code

Implementing and maintaining Infrastructure as Code (IaC) to automate the provisioning of Environments, becomes challenging as you scale. IaC is good at provisioning individual resources (or a few of them together) but engineering teams want an entire environment with various components like networking, platform (ec2/eks), database, s3 buckets, etc. to deploy and operate their applications. To provision and tear down an entire environment, these teams have two options. They can either hand roll pipelines to manage individual resources and then manage complex dependencies between these resources within those pipelines or create a monolith IaC for the entire environment. These approaches are inefficient and slow down feature development and innovation. What if there were a better way? In this presentation, we will introduce Environment as Code that enables teams to provision & teardown entire Environments in an efficient way and promotes best practices like loosely coupled infrastructure resources. Key Takeaways: ● Challenges implementing & maintaining Infrastructure as Code ● What is Environment as Code? ● How Environment as Code can help resolve those challenges?