... At approximately 02:00 hours, while many slept, a colossal breakthrough was made ...
... After many long nights and countless eons ...
I finally completed my Cloud Resume Challenge Project !!!!!!!1!!!1!1!
You can find my Cloud Resume Project HERE!!
GitHub
LinkedIn
Also, I am actively looking for an opportunity to prove myself and develop my skills with my first job in the cloud! If you could please like and share I would immensely appreciate any and all help!
Contents
- The Challenge
- Certification
- Front End
- Back End
- IaC / CICD / Version Control
- Testing
- Challenges and Future Improvements
The Challenge
The Cloud Resume Challenge is a 16-step challenge designed for beginners to get hands-on experience with some of the tools and applications that DevOps Engineers and Cloud Architects use in their day-to-day tasks.
The steps outlined in the CRC were intentionally high-level and incredibly vague, providing a fun and sometimes challenging learning opportunity.
Certification
The first steps of the CRC recommended preparing to take the AWS Cloud Practitioner Exam. However, fancying myself an overachiever, I decided to pursue the AWS Solutions Architect Associate Course (SAA-C03) instead.
So, I signed up for Adrian Cantrill's AWS Certified Solutions Architect - Associate Course and Jon Bonzo’s AWS Certified Solutions Architect Associate Practice Exams and I am glad I did.
In March of '23, I passed the Cloud Practitioner exam, and finally, the Solutions Architect Associate.
I was quite nervous leading up to my exam day for SAA-C03, but when it finally came time to sit down for it... I immediately realized how well Cantrill's and Bonzo's services had prepared me.
Front End
Alright, so getting into the real meat ‘n potatoes, this is what I did…
The challenge required writing up my resume in HTML and CSS… Which I had some light experience with, but I did a some speedruns through a few free courses, found an example of a resume I liked, and mixed it all up and got that working locally in VSCode…
Next, I needed to create a domain using Route53 and setup a Cloudfront Distribution with a S3 Bucket as the origin… I found these sections to be pretty simple and straightforward… Again, I believe Adrian Cantrill’s course exceptionally prepared me for this area with the practical knowledge covered between his lectures and tutorials.
Back End
For this section, I needed to create a visitor counter for my site using Lambda, DynamoDB, and API Gateway, and some Javascript…
Figuring out the Javascript was by far the most difficult part of this challenge for me… I especially struggled trying to figure out how to make sure I could fetch my API URL dynamically.
IaC / CICD / Version Control
When first approaching these chunks I stalled for some time to do as much reading up as I could to understand. I had heard of these terms in passing but they were always quite vague to me as to what exactly they were and how they worked.
Setting up Version Control and my CICD pipelines seemed like a pretty daunting order at first, but after skimming through the GitHub Documentations I found these to be some of the easier steps to complete.
Getting to the Infrastructure-as-Code, I initially debated between using AWS SAM or Terraform as I would be learning about either completely fresh anyways. Ultimately, I went with SAM for its simplicity of use with serverless.
As I started to figure it out I had a surprising amount of fun working with SAM… And it was without a doubt my favorite part of the challenge.
This article, One Artifact, One Pipeline, One Path to Production, was particularly beneficial for helping get me started in this section.
Testing
This was another especially challenging portion of the challenge for me and it took a significant amount of tie for me to get this hammered out, but boy did it feel good when I got those 'PASSED' outputs.
Challenges and Future Improvements
1.
Improve the API functionality of the visitor counter to be more efficient in distinguishing repeat visitors.
2.
I would probably like to add a little bit more testing for my Lambda code.
3.
I may consider reworking the IaC with Terraform. Initially, I had explored the idea of using Terraform but decided I’d be better off going forward with SAM as it seemed more intuitive for me… Also, Terraform just has a cooler sci-fi sounding name!
Ok, now...
Crab rave
Top comments (0)