We'll go over a couple use cases for using Pulumi to manage AWS infrastructure with Typescript as the primary language for your Pulumi configuration. Attendees will have the opportunity to learn some basic Pulumi functions, even if they're not familiar with Typescript!

It seems so simple, right? Many developers know how to deploy an application but some don't because that might be outsourced to a deployment engineer. Also, many systems engineers may know how to maintain infrastructure, but they don't know how an application is actually deployed. In this worskshop, we'll go over the basics of DevOps and provide those who may not have a current window into current automated build and deployment processes an example application to deploy to Azure using Azure DevOps.

Terraform is a great tool to write your infrastructure as code. It can be challenging to get started and find the best practices. This session will be packed with information and examples on how to use Terraform at scale. We'll look at best practices, Terraform within CI/CD, using Terragrunt and CDKTF. The demonstrations will be within the AWS environment, however, concepts can apply for all cloud or on premise providers. After this session you will be able to setup Terraform with reusable modules configurable by environment.

Attendees will understand the benefits of creating their own extended version of the Amazon Cloud Development Kit. They will see how defining rules and setting up standards around CDK can enable better, safer and more maintainable infrastructure as code.

At first glance, ingress is an easy concept: you route traffic from the wider world into your cluster. As you layer on SSL and load balancing, the principles stay the same and everything works with minimal thought and effort. But as your infrastructure grows, your clusters grow, the interactions get more complex, and your security requirements explode. In this session, I’ll walk you through how we designed and built an Ingress Controller and have converted our clusters to use it in production to support millions of requests. It wasn’t easy but running it as an open source effort from the start encouraged our team and customers to review, explore, and consider situations outside our original plans.