You’ve clicked through the cloud portal and deployed the infrastructure. But what about the next environment? Can you click exactly the same buttons in the same order? And what about when the needs change? Can you evolve all the environments identically? Click-ops can only get you so far. Infrastructure-as-Code allows you to create consistent, durable, codified environments the same way you make durable and consistent applications. Once the code is in place, you can efficiently spin up another environment that is identical in every way. And when a change occurs, the same code updates the next system identically and consistently. In this workshop we look at Terraform, the most popular Infrastructure-as-code platform. We’ll use AWS as a target environment, and deploy sample infrastructure. We’ll deploy: - DynamoDB database - Lambda code function - API Gateway - A container running in Fargate ECS - An Application Load Balancer (ALB) - All the necessary configuration for every piece - Roles, policies, and permissions for each Along the way we’ll learn: - The value of Infrastructure as Code - The pain of Click-ops - Terraform syntax and popular commands - How to run Terraform in a DevOps pipeline Terraform is definitely an investment, but it’s an investment that pays you back every time you need to make a change to any environment or recover from disaster. You can get started or level-up with Terraform on AWS today. For this workshop you’ll need: - Install and update Terraform - Install and update the AWS CLI - An AWS account with root access - Optional: Node.js - Optional: Docker Desktop or another OCI build environment See the full instructions at https://github.com/robrich/terraform-hands-on-workshop-aws