As a clinical laboratory technician trying to pivot into a new career in Cloud and software development, I have often found it difficult to turn theoretical knowledge into real meaningful experience. The suggestion from those with experience is typically, "do some projects" but this is always easier said than done. There are only so many "Hello world" applications you can write before you start losing focus revert back to watching the world burn.
When I learned about the Cloud Resume Challenge, created by Forrest Brazeal, I realized it was the perfect project for diving in to the Cloud field. If you haven't heard of the challenge, it is quite simple on its face. You need to make a simple website that will display your resume and a visitor count (there is also a requirement to pass the AWS Certified Cloud Practitioner exam but that's kind of adjacent to the development of the website).
Sounds simple right? I did that easily back in the anglefire.com days.
But it is in the way that you need to do these tasks that makes the Cloud Resume Challenge such a great project that forces the challenger to not just get their feet wet, but fully submerged.
This means that the challenger will need to use the AWS SAM CLI and learn how to properly write .YAML templates to automate the creation (or update) of serverless resources like permissions and APIs and DynamoDB tables, use python to make functions to update the DynamoDB table, use Github actions to automate the process of packaging and deploying of the serverless components, and using CLI commands to make sure that the virtual machine running the jobs in your Github actions have the resources to complete your tests and deployments.
Speaking on all of this in one post would be exhausting to both read and write, so I will be following up this post with additional posts outlining the challenges and revelations that went into my completions of each step (like how it took an entire day of troubleshooting to realize that my spacing was wrong in a SAM template.yaml file or how long it took me to realize where I had to look to find errors in my Github actions jobs).
So I will be back with more! But with this post, I complete the challenge!
The "more" that was promised
.1 The Site