The original text can be found at cloudresumechallenge.dev/docs/the-challenge/aws/ and was copied here to reflect the changes to the original idea.
Your resume needs to have the AWS Cloud Practitioner certification on it. This is an introductory certification that orients you on the industry-leading AWS cloud – if you have a more advanced AWS cert, that’s fine but not expected. You can sit this exam online for $100 USD. A Cloud Guru offers exam prep resources.
Your resume needs to be written in HTML. Not a Word doc, not a PDF. Here is an example of what I mean.
Sebastians Version: Html will be generated by a static blog site generator.
Your resume needs to be styled with CSS. No worries if you’re not a designer – neither am I. It doesn’t have to be fancy. But we need to see something other than raw HTML when we open the webpage.
Your HTML resume should be deployed online as an Amazon S3 static website. Services like Netlify and GitHub Pages are great and I would normally recommend them for personal static site deployments, but they make things a little too abstract for our purposes here. Use S3.
Sebastians Version: Add Cloudfront to the S3 Bucket. You need it later for Https anyway
The S3 website URL should use HTTPS for security. You will need to use Amazon CloudFront to help with this.
Point a custom DNS domain name to the CloudFront distribution, so your resume can be accessed at something like my-c00l-resume-website.com. You can use Amazon Route 53 or any other DNS provider for this. A domain name usually costs about ten bucks to register.
Your resume webpage should include a visitor counter that displays how many people have accessed the site. You will need to write a bit of Javascript to make this happen. Here is a helpful tutorial to get you started in the right direction.
Sebastians Version: Use typescript where possible. Add a basic test to everything. There will be no ‘visitor counter’ as this feature can be easily exploited by using lots of resources. I opted to build dynamic ‘video live status’ on the homepage - the ./live-status.md document describes this in depth.
The visitor counter will need to retrieve and update its count in a database somewhere. I suggest you use Amazon’s DynamoDB for this. (Use on-demand pricing for the database and you’ll pay essentially nothing, unless you store or retrieve much more data than this project requires.) Here is a great free course on DynamoDB.
Sebastians Version: There will be no data in DynamoDB as S3 will do fine as a storage for the small amount of puts and queries to the data.
Do not communicate directly with DynamoDB from your Javascript code. Instead, you will need to create an API that accepts requests from your web app and communicates with the database. I suggest using AWS’s API Gateway and Lambda services for this. They will be free or close to free for what we are doing.
Sebastians Version: The apigateway will be used to communicate with Twitch. See the ./live-status.md document for more information.
You will need to write a bit of code in the Lambda function; you could use more Javascript, but it would be better for our purposes to explore Python – a common language used in back-end programs and scripts – and its boto3 library for AWS. Here is a good, free Python tutorial.
Sebastians Version: No python is used here. Only Typescript.
You should also include some tests for your Python code. Here are some resources on writing good Python tests.
Sebastians Version: Test all the code. If possible avoid slow tests frmaeworks like jest and opt for faster variants e.g. mocha
You should not be configuring your API resources – the DynamoDB table, the API Gateway, the Lambda function – manually, by clicking around in the AWS console. Instead, define them in an AWS Serverless Application Model (SAM) template and deploy them using the AWS SAM CLI. This is called “infrastructure as code” or IaC. It saves you time in the long run.
You do not want to be updating either your back-end API or your front-end website by making calls from your laptop, though. You want them to update automatically whenever you make a change to the code. (This is called continuous integration and deployment, or CI/CD.) Create a GitHub repository for your backend code.
Sebastians Version: We will keep all the data in AWS CodeCommit
Set up GitHub Actions such that when you push an update to your Serverless Application Model template or Python code, your Python tests get run. If the tests pass, the SAM application should get packaged and deployed to AWS.
Sebastians Version: We will be using CodePipeline by AWS
Create a second GitHub repository for your website code. Create GitHub Actions such that when you push new website code, the S3 bucket automatically gets updated. (You may need to invalidate your CloudFront cache in the code as well.) Important note: DO NOT commit AWS credentials to source control! Bad hats will find them and use them against you!
Sebastians Version: We will keep all the code in one repository using lerna.js
Finally, in the text of your resume, you should link a short blog post describing some things you learned while working on this project. Dev.to is a great place to publish if you don’t have your own blog.