I am starting to get into an IT path; The AWS cloud resume challenge was assigned by our professor.
And as just a beginner in these matters, I knew nothing, honestly it was a struggle since day one, but it is okey, every expert was once a learner.

  1. Certification
    First thing to do was obtaining the AWS cloud practitioner certification which I already had from a previous class.

  2. Front End (steps 2,3)
    I did my resume in really basic HTML and CSS, as I just learned while doing this project, I even started doing it in notepad, as I had not yet installed vscode. I believe is fairly easy to learn this as I think there is plenty of detail resources but had to keep it simple as far difficult tasks were coming along.

  3. AWS Resources (steps 4-10)
    This is the part where it starts to get difficult, though the AWS console is pretty user friendly, there are lots of configurations that you need to learn and get used to.
    Even then I founded pretty interesting to create the static website and get my first DNS.
    I found good you tube videos that helped me with the python code for the lambda and the java script for the visitor counter. The Database was pretty simple but worked just fine.

  4. TESTS!!
    I got completely stuck and wasted so much time trying to find good guidance with this part. Finally, a good advice, USE CHAT GPT. It helped a lot but of course, I felt this part was pretty tedious as I had to install lots of software and extensions to my vscode. Every time I thought I got it, there was yet another error message. But with the help of lots of you tube and chat GPT, made it work.

  5. Source Control
    As I got stuck with the testing, I decided to do the next task, so this part was actually done before the test, this part took some time,
    but it worked. I got my first GITHUB repository yay!

  6. CICD Front End
    I used Git Hub actions to update my s3 bucket every time I made changes to my front-end code.

  7. Infrastructure as Code and CICD Back end
    I did get to install all requirements and successfully deployed a stack, but time was already out I could not set up the function properly. And the CICD Back end was not set up also.

  8. Blog
    This was the last step; to share my experience, Here I am telling you my journey, Hope whoever read this be successful and happy!!

Conclusion
Even if the project felt really hard for me, I appreciated being exposed to all this new knowledge. I did learn a lot.
sadly, I could not finish the whole project in time, but I am not giving up, I am planning on continuing the project and keep upgrading it with every new knowledge I obtain.
while doing my research I realize this project is pretty popular, and I don't know if it is just me but majority of resources I found are not really beginner friendly.
But I would love to give props to the dev community as I really appreciate that many share their knowledge, it makes me feel more confident in this journey, even though... I realize it will be long.