Run dev, staging and production from Terraform modules and GitOps, and prove recovery in a second region.
A SaaS company wants three identical environments and a tested plan to rebuild production after a regional outage.
The detailed steps, checklists and trainer review open in the SOTT student portal for enrolled students.
Banking: Self-service environments. Developers waited a week for test servers from the infrastructure team. Terraform modules and a pipeline let developers create approved environments from a pull request. Waiting time fell from a week to under an hour, within security rules.
E-commerce: Containers instead of VMs. Each app needed its own VM and releases meant patching servers one by one. Apps were containerised and deployed to Kubernetes through Jenkins, with Ansible handling the remaining VMs. Releases became daily, and infrastructure costs dropped as servers were shared.
SaaS: One-click disaster recovery. Nobody knew how long it would take to rebuild production after a region failure. All infrastructure is code, so a second region can be built from the same modules and data restored from backups. A recovery drill rebuilt production in another region in under two hours.
Yes. Once your trainer approves it, list it under Projects with the tools you used, one line on the problem it solves and a link to your repository and demo video.
About 22 hours of hands-on work, and it fits best after week 10 of the Cloud Automation with DevOps course.
Enrolled students get every task with steps, "done when" checks, the submission form and a trainer review in the SOTT student portal.