9.5.2. Steps

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

The first step involves preparing the files necessary for your static website. You need to create two essential HTML files: 'index.html' serves as the main page of your website, while 'error.html' provides a custom error page for instances when a user tries to access a non-existent page. This ensures a good user experience even when errors occur.

Think of 'index.html' like the front door of your store that welcomes customers, while 'error.html' is a sign you put up to guide lost customers back to the right path, keeping them informed and reducing their frustration.

2. Login to AWS Console and go to the S3 Dashboard. 3. Create a new bucket: ○ Bucket name must be globally unique. ○ Disable "Block all public access" under Permissions.

In this step, you log into the AWS management console, navigate to the Amazon S3 section, and create a new storage bucket. Make sure to choose a unique name, as no two buckets can share the same name globally. Additionally, you'll need to adjust the permissions by disabling the 'Block all public access' option, which allows your website to be accessed by anyone on the internet.

Creating an S3 bucket is similar to getting your storefront ready. You have to choose a unique name for your storefront that no one else has, and then ensure the doors are unlocked so that customers can freely enter and browse your offerings.

4. Upload website files to the bucket.

Once your bucket is ready, the next step is to upload the HTML files (index.html and error.html) you prepared earlier. This can typically be done using the AWS Management Console's simple drag-and-drop feature or through a file upload option provided in the S3 interface.

Think of uploading your files like stocking your store with products. Once your storefront is built, you need to fill it with items (in this case, website files) that customers can browse and purchase (or in web terms, view).

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

To make your bucket serve as a static website, you need to enable the static website hosting feature in the bucket properties. When doing this, specify which documents to use for your index page (index.html) and error page (error.html). This tells AWS how to handle requests for your website.

Enabling static website hosting is like turning on the lights in your store. When the lights are on, customers can enter and see your products; by enabling this feature, you're making your website accessible to visitors.

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 allow users to access your uploaded files, you need to set a bucket policy that makes them publicly readable. This JSON structure defines permissions for who can access your bucket and includes 'Allow' for everyone ('Principal':'*') to read the objects stored, which is fundamental for a public website.

This step is akin to putting up a sign on your storefront that says 'Everyone Welcome!' By setting up a public access policy, you're inviting anyone to visit and view your content.

7. Access your website using the S3 website endpoint.

The final step involves accessing your static website through the S3 website endpoint. This is a special URL provided by AWS that directs users to your website. Simply enter that URL into any web browser to view your site live.

Accessing your website is like giving your customers the address of your store. Once they have the address (the S3 endpoint), they can easily find and visit your shop at any time.

--