Launch a static website on Amazon S3 featuring chatGPT as a content creator

Online tutorial for this project can be found here
How I went about mine
1. Create website content
What is a website without its content? The first thing to get out of the way before starting this task is the website content (the HTML, CSS, … files). I wasn’t sure what website I wanted to build until I remembered that I’m part of the people that seldom buys domain names for each bright idea I get (usually every 3 business days) and forgets about them. I decided to finally go with the real estate website I had promised to build for a friend eon years ago. (The website I created is a sample website pending when my friend is serious to start his real estate business)
I didn’t want anything complicated so I simply went to Github and searched for a vanilla JS real estate website and I cloned the repo.
For the details to fill on the website, I used chatGPT to fill up the different information segments. Some of the prompts I asked it can be seen below:

2. Register domain name
I skipped this step because as I mentioned earlier, I already had domain names registered with Route 53
3. Steps 3–12
I followed every step as seen on the tutorial

Mistakes made (sorry I mean painful learning)

To avoid spending hours sweating and trying to figure out what is wrong, please learn from my mistakes:
1. Website content upload
I uploaded the entire website content as a folder and quickly clicked on the bucket endpoint to see if my website looked like it was meant to look. To my surprise, all I saw was a text-only website- it had no images or format as I had prepared it. I went back to the bucket and realized the CSS files did not upload alongside the folder, so I had to upload it separately. So be sure to confirm that every file on website your folder is properly uploaded.

2. The tiny mistake that cost me 2 hours

The tutorial specifically mentioned that the domain and sub-domain names must be the same when creating the necessary services (bucket, alias record etc). I followed this instruction to the T (or so I thought). When I got to the point of creating an alias record, there’s a step where you select the s3 bucket you are creating the record for. This worked perfectly for the domain name but didn’t for the sub-domain name. I was so confused because the steps were literally the same, I tried to manually input the bucket name in the suggested format but it kept giving an error. I tried every possible thing, deleted and started all over again severally but nothing worked. At the point where the caffeine in my body could no longer sustain me, I decided to call it a night but chose to go over to the s3 service and confirm that my bucket names were properly written. To my greatest surprise, I created a bucket for the sub-domain with the wrong spelling. Rather than write www.bestdiddyproperties.com, I wrote www.bestdiddyproperties.ocm. This little typo of spelling .com as .ocm cost me over 2 hours so be sure to confirm that all domain and sub-domain names are properly spelt so they can easily be linked.

Links
Link to the website

Link to the Github repo

Disclaimer: This article describes my personal journey and recommendations made are merely suggestions.
Please feel free to share your thoughts, feedback or criticisms. Look forward to hearing from you