Cloud Resume Challenge - Building a Cloud-Native Portfolio
NOTE: This is my blog post for the Cloud Resume Challenge for my website . The Cloud Resume Challenge is a project comprised of a list of requirements to complete in order to host your resume/portfolio in the cloud using cloud-native infrastructure. Please also visit the GitHub repo for more information as well as the README. Two Birds, One Stone For quite some time now, I have wanted to have my…
The Cloud Resume Challenge is a project that involves hosting a resume/portfolio in the cloud using cloud-native infrastructure. The author decided to build this challenge as their own portfolio website to showcase their technical skills, in addition to their resume. This approach provides more control, cost savings, and SRE/DevOps experience.
To create their infrastructure diagram, the author used Lucidchart. Instead of following the challenge guidelines strictly, the author utilized their existing Hashicorp Vault hosted in their on-premises Kubernetes cluster. This decision provides granular control over JWT and keeps secrets off the cloud and behind a VPN.
For infrastructure as code (IaC), the author chose Terraform over Pulumi due to their Terraform Associate certification and the industry-standard HCL. This experience proved to be more valuable than initially expected, leading to a greater inclination to use Terraform/HCL for future projects.
The author's CI/CD process consists of two GitHub repositories, one for the backend and the other for the web frontend. They used GitHub Actions workflows with YAML in two branches: a testing branch for running terraform plan and a main branch for live production. If necessary, manual destruction of infrastructure is possible through a workflow dispatch.
The frontend of the portfolio site was built using a template from Start Bootstrap, with modifications to HTML, CSS, and JavaScript. The author learned HTML, CSS, JavaScript, and how to use localStorage for a visitor counter that doesn't increase upon browser refresh. While not their primary focus, the author enjoyed learning about frontend development.
In terms of the backend, the author focused on Terraform and learned about data blocks, resource blocks, locals, and for_each. Although they plan to clean up the code further, they are satisfied with the current structure and feel confident about its correctness and optimality. The author also plans to add a blog to the portfolio site and upgrade the visitor counter with additional information and improved accuracy.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
