 My name is Natasha Spieger and I work as a cloud operation engineer at Kickstarter. Today I wanted to tell you a little bit more about my unusual path to ops engineering. A few years ago, I had one of the toughest jobs in the world. I had become a standard mom to my two wonderful kids, Max and Anna. I realized that gaining painting skills really prepared me well to be into the workforce. For example, I picked up time management, tried to do 28 hours of work in 24. I also learned about problem solving, communication, collaboration. Another fun example is trying to get a toddler to do something they don't want to do. That's a true challenge right there. I also picked up dedication and reliability. Parents have truly mastered what it means to be reliable. Time becomes such a precious commodity that it cannot be wasted on survival. A few years later, I was really excited to be into the workforce and thought I could face anything that would come my way. Unfortunately, the views and opinions, the views of potential employers were very negative about state-owned parents. They considered it a risk to hire me. So I went back to the drawing board. We found out about the skills I had just picked up and the things I liked to do and I started to teach myself how to code. I was lucky enough to get a web development fellowship at the Flatiron School, a 22-week program that was created to enable diversity in a New York City tech pipeline. Upon graduation, I got a job at the Wall Street Journal as DevOps Engineer. The enthusiasm of employers in the tech industry was rather refreshing compared to what I had encountered before. Just a few months ago, I landed my dream job at Kickstarter, where I really started to develop a passion for DevOps Engineering. At Kickstarter, we have Ruby on Wheels monolithic application and we are moving towards a microservice-oriented architecture leveraging Docker. We also wanted to use AWS Lambda to enable automation. So you're going to ask me, what is Lambda? Well, Lambda is a serverless compute service that runs on code triggered by specific events. We use Lambda at Kickstarter for resource creation in cloud formation template. To use them, we needed tools, for example, the deployment service. So we picked Apex, a great deployment service that allows for a great workflow. We also needed to start thinking about testing. So we write on Lambda as a node and write unit tests that we would do for any other code base. And we also use a module called Lambda Local. It allows you to brand new functions on your local machine with using sample event data. Now that we had all the tooling set up, it was time to start building them. So, for example, we built a Lambda Finder that would gather all the information needed to split up a new instance. This Lambda Finder would be triggered by a cloud formation template and would, for example, retrieve the VPC ID and the subnets associated with this VPC or even use Logic to retrieve the latest AMI for your instance. Another example is recently we built, we used Lambda to build access control lists for other services such as BOT, a secret store, or console or services cover tool. So these were just a few very quick examples on how one ops engineer can leverage Lambda to automate the infrastructure. I hope it will give you a few ideas on how to use that. And as I'm reaching the end of my talk, I just wanted to say that this big career chain would not have been possible without the help and support of a few key alloys along the way. I could not have done it without them. Thank you and find me on Twitter and I would like to take to come for more questions about Lambda.