Cloud DevOps - Infrastructure new era Part 1

A journey to migrate from CloudFormation to Terraform with zero downtime

Transcript

1. Cloud DevOps Infrastructure new era Part 1
2. Goals
3. Goals • Simplify • Infrastructure as a code • Human readable • Output of changes before apply • Automated CI/CD
4. Old era
5. High pace team Utilize the strengths of the team to deliver faster
6. Tools • Github actions • AWS CodePipeline • AWS Codebuild • AWS Cloudformation • AWS Lambda (status for PRs)
7. Bootstrap CI/CD Cloudformation Codepipeline Github Status
8. Infrastructure CI/CD
9. Problem - Complex
10. Problem - Hard to read (YAML)
11. Problem - Nested stacks spaghetti
12. Problem - No output of changes
13. New era
14. Learnings - Need to focus • Quality • Scalability • Readability • Simplification • Easy to on-board other Ops people
15. High pace team Do it the right way
16. Tools • Handover to Christos K. • Github actions • Terraform
17. Challenges • Import current state of infra • Delete cloudformation stacks (still not solved)
18. Import State https://github.com/lensesio-dev/cloud-infra-terraform/blob/master/tf-state.sh
19. Review before apply
20. Review before apply
21. Testing • Test infrastructure as a code • Use gruntwork-io/terratest
22. Benefits • Remote state • Protect state with locks • Keeping sensitive information off disk • Encrypted state • Output of changes before apply • Reusable terraform modules https://github.com/lensesio-dev/cloud-terraform-modules Infrastructure repo: https://github.com/lensesio-dev/cloud-infra-terraform
23. Dev Infrastructure
24. Prod Infrastructure
25. To be continued… Part 2 is coming
26. Thanks