AWS

Complete The Cloud Resume Challenge The Challenge Part 1: Get AWS Certified and complete The Cloud Resume Challenge Part 2: HTML - Create a website –> Part 3: CSS - Style your website <– Part 4: Static Website - Amazon S3 Part 5: HTTPS - Set up Amazon CloudFront Part 6: DNS - Custom domain name with Amazon Route 53 Part 7-12: Backend - Creating a serverless API and requesting it with JS Part 13-16: CI/CD - Commit, Build and Deploy with AWS CodePipeline tl;dr: Learn some basic CSS at w3schools.com. Style a website using CSS. ...

Complete The Cloud Resume Challenge The Challenge Part 1: Get AWS Certified and complete The Cloud Resume Challenge –> Part 2: HTML - Create a website <– Part 3: CSS - Style your website Part 4: Static Website - Amazon S3 Part 5: HTTPS - Set up Amazon CloudFront Part 6: DNS - Custom domain name with Amazon Route 53 Part 7-12: Backend - Creating a serverless API and requesting it with JS Part 13-16: CI/CD - Commit, Build and Deploy with AWS CodePipeline tl;dr: Create a website using HTML ...

Complete The Cloud Resume Challenge The Challenge –> Part 1: Get AWS Certified and complete The Cloud Resume Challenge <– Part 2: HTML - Create a website Part 3: CSS - Style your website Part 4: Static Website - Amazon S3 Part 5: HTTPS - Set up Amazon CloudFront Part 6: DNS - Custom domain name with Amazon Route 53 Part 7-12: Backend - Creating a serverless API and requesting it with JS Part 13-16: CI/CD - Commit, Build and Deploy with AWS CodePipeline tl;dr: Complete an AWS Certification Exam and create an AWS Account. Next we’ll create a website using different AWS services. Following the steps of The Cloud Resume Challenge ...

tl;dr: Script to sync github repo with S3: https://github.com/jakejarvis/s3-sync-action Workflow Writing this blog I want as little friction as possible. By that I mean that i want as short as possible distance/time/clicks between me writing a post in a markdown file and the blog being updated on the world wide web. My solution to this goal was version control on GitHub and creating a pipeline with GitHub Actions, that would deploy my webpage automatically on push to main. This way all I need to do is write a new blog post and push it to git ...