9.4.2. Steps

1. Prepare your website files:
   • Create an index.html and error.html page.

The first step in hosting a static website on Amazon S3 is to prepare your files. This involves creating two essential HTML files called index.html and error.html. The index.html file is the main page that users will see when they access the website, while the error.html file will be displayed if there are any issues, such as a broken link.

Think of your website as a book. The index.html is like the cover page that introduces readers to the content, while the error.html acts as a 'sorry, this page is not available' message, similar to having a warning sign in a library.

2. Login to AWS Console and go to the S3 Dashboard.

Once your website files are prepared, the next step is to access the AWS Management Console. You will log in to your AWS account and navigate to the S3 (Simple Storage Service) Dashboard, where you will manage your storage buckets and uploaded files.

Imagine entering a large warehouse where you store all your items (your website files). The S3 Dashboard acts as your control room, where you can see and manage everything you have stored.

3. Create a new bucket:
   • Bucket name must be globally unique.
   • Disable 'Block all public access' under Permissions.

Creating a new bucket is crucial for storing your files. A bucket in S3 is like a folder in your file cabinet. When creating it, you must give it a name that is unique across all AWS users. Additionally, to make your website accessible to everyone, you must disable the 'Block all public access' setting, allowing public visibility of the files in that bucket.

Think of your bucket as a public library. You need a unique name for the library that does not exist anywhere else, and to let people in, you need to take down any 'no entry' signs.

4. Upload website files to the bucket.

Now that your bucket is created, the next step is to upload your prepared website files (index.html and error.html) into the bucket. This step brings your website content into the storage space you just created.

This can be compared to filling your library with books. You gather your carefully prepared books (website files) and place them onto the shelves of your library (the bucket).

5. Enable static website hosting:
   • Go to the bucket's Properties tab.
   • Enable Static website hosting and set index/error documents.

With your files uploaded, you need to enable static website hosting in the bucket's settings. This involves navigating to the Properties tab of your bucket and selecting the static website hosting option. Here, you’ll specify which files to use for index and error documents so that S3 knows how to handle incoming requests.

Imagine you set up a website like opening the front door of your library for visitors. By enabling static website hosting, you are essentially creating a front desk that tells visitors what to look for (index.html) and what to do if they can’t find it (error.html).

6. Set Bucket Policy to make files public:

   {
     "Version": "2012-10-17",
     "Statement": [
       {
         "Sid": "PublicReadGetObject",
         "Effect": "Allow",
         "Principal": "*",
         "Action": "s3:GetObject",
         "Resource": "arn:aws:s3:::your-bucket-name/*"
       }
     ]
   }

To ensure that everyone can access your website, you need to set a bucket policy that allows public access. This involves editing the bucket policy JSON to permit 'GetObject' actions for all users so they can read the files in your bucket.

It’s as if you decided to keep your library open to everyone. By providing an open-door policy (bucket policy), you let anyone walk in and read the books (files) without restriction.

7. Access your website using the S3 website endpoint.

Finally, with everything set up, you can access your website. S3 provides a unique URL called the website endpoint where users can reach your site and view your content online.

This step is like opening the library to the public with a sign outside that tells them where to enter and find the books. The endpoint serves as the library's address, leading people straight to your online resources.

--