DEV Community: Stephen Lawal

How I Hosted My Static Website on Amazon S3 Using the AWS Console

Stephen Lawal — Fri, 07 Feb 2025 10:46:41 +0000

As I continue learning cloud computing and getting hands-on with AWS, I decided to host a simple static website using Amazon S3. Since my website only contains HTML and CSS, S3’s static website hosting was the perfect solution—no need for servers or backend configurations. In this article, I’ll share exactly how I set it up using the AWS Management Console.

Why I Chose Amazon S3

I wanted a cost-effective and easy-to-manage way to host a simple website. After researching different hosting options, S3 stood out because:

It's affordable-I only pay for what I use.
It's easy to set up-no need to configure web servers.
It's scalable-AWS handles traffic fluctuations automatically.

With that in mind, I jumped right into the setup.

Step 1: Creating an S3 Bucket

1. Logging into AWS
First, I logged into the AWS Management Console and searched for S3
in the AWS services menu.
2. Creating the Bucket

Clicked "Create bucket".
Selected my preferred AWS region.
Disabled "Block all public access" (since I wanted my website to be public).
Clicked "Create bucket" to finish the setup.

At this point, my storage space was ready, but I still needed to upload my website files.

Step 2: Uploading My Website Files

Opened my new S3 bucket.
Clicked "Upload".
Clicked "Add files" and selected my index.html and image folder.
Clicked "Upload" to store them in S3.

Now, my files were in the cloud, but the website wasn’t live yet.

Step 3: Enabling Static Website Hosting

To make my website accessible via a URL, I had to enable static website hosting:

Opened the Properties tab in my S3 bucket.
Scrolled down to Static website hosting and clicked Edit.
Selected "Enable".
Chose "Host a static website".
Entered s3.html as my Index document.
Clicked Save changes.

After enabling this, AWS provided me with a website endpoint URL, something like this: http://stephenbucket.s3.us-east-1.amazonaws.com/s3.html

However, when I tried opening the link, I got an Access Denied error. That meant I needed to allow public access to my files.

Step 4: Making My Website Public

By default, all S3 files are private, so I had to update permissions.
1. Adjusting Bucket Permissions

Opened the Permissions tab in my S3 bucket.
Clicked Edit under Block public access settings.
Unchecked "Block all public access".
Confirmed the change by typing confirm and clicked Save changes.

2. Changing Object Permissions
Even though I updated the bucket settings, my files were still private. I had to manually make them public:

Went back to the Objects tab.
Selected my s3.html file.
Clicked "Actions" > "Make public".

Now, my website was accessible to the public!

Step 5: Testing My Website

To verify everything was working, I:

Opened a browser.
Pasted the S3 website URL from Step 3.
Saw my website load successfully!

It was a great feeling to see my work live on the internet, hosted entirely on AWS.

Final Thoughts

Hosting a static website on S3 was a smooth experience, and I learned a lot about AWS in the process. The AWS Management Console made it easy to:

Create and configure an S3 bucket.
Upload and manage website files.
Enable public access for website hosting.

If you’re also exploring AWS, I highly recommend trying this out. It’s a simple yet powerful way to get hands-on cloud experience.

Into the Cloud: A Journey Beyond Limits

Stephen Lawal — Thu, 09 Jan 2025 15:13:14 +0000

Imagine a world where innovation knows no boundaries, where businesses rise and fall on their ability to adapt, scale, and thrive in an instant. This is the realm of cloud computing—a force so transformative, it’s redefining how we connect, create, and conquer the future. My journey into the AWS Cloud Practitioner learning path has felt like stepping into this world for the first time, uncovering the unseen architecture powering the digital age.

It all began with cloud concepts, the gateway to understanding a revolution hiding in plain sight. I was introduced to the essence of cloud computing: flexibility, scalability, and cost-efficiency. But these weren’t just buzzwords; they were keys to a new way of thinking. Businesses no longer needed to invest millions in infrastructure—they could build, grow, and innovate at a fraction of the cost, thanks to the cloud.

What struck me was the simplicity masking its power. Three service models—Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS)—serve as the foundation for this new era. Each model offers a unique way to create and deliver solutions, tailored to specific needs. The cloud isn’t just a tool; it’s a playground where possibilities are limitless.

But understanding the cloud wasn’t enough—I needed to see its engine. That’s where the AWS global infrastructure came in, and it was nothing short of awe-inspiring. AWS spans the globe like a living, breathing entity, with Regions, Availability Zones, and Edge Locations working together in perfect harmony. It’s the backbone of the modern internet, the silent force enabling Netflix to stream without interruption and e-commerce giants to process millions of transactions in seconds.

The beauty of AWS’s infrastructure lies in its design. Regions are built to be resilient, with multiple Availability Zones ensuring that even if disaster strikes, operations continue seamlessly. And Edge Locations? They’re the unsung heroes, delivering content at lightning speed, no matter where in the world you are. I explored this network through hands-on exercises, creating resources in specific Regions and witnessing firsthand how AWS brings its promises to life.

But this wasn’t just about technology—it was about strategy. Selecting a Region wasn’t as simple as picking the closest one. Compliance, latency, cost—every decision carried weight. It felt less like learning and more like unlocking secrets of the digital world, understanding the precision behind every deployment, every service, every innovation.

These first two modules have been nothing short of transformative. They aren’t just lessons; they’re revelations. Cloud computing is more than a tool—it’s a movement, a reshaping of what’s possible. AWS’s infrastructure isn’t just a network—it’s the foundation of a digital empire. And as I dive deeper into this journey, I feel like an explorer standing at the edge of a vast, uncharted land, ready to uncover its secrets.

This is just the beginning. The cloud is calling, and I’m ready to answer.

My Journey: From Web Developer to AWS Cloud Practitioner

Stephen Lawal — Tue, 07 Jan 2025 18:23:13 +0000

My name is Stephen Lawal, and I am a passionate technologist with a background in web development. Over the years, I have gained extensive experience designing, building, and deploying user-friendly web applications. My journey in technology has been one of continuous learning, adaptability, and a drive to stay at the forefront of innovation.

Recently, I have decided to take the next step in my career by transitioning into the world of cloud computing, starting with becoming an AWS Cloud Practitioner. This decision stems from my desire to broaden my technical skill set and contribute to creating scalable, secure, and efficient cloud solutions for businesses.

During my web development career, I worked with technologies that required seamless deployment and optimization, which sparked my interest in how cloud infrastructure could enhance efficiency and scalability. AWS, being the industry leader, presented itself as the perfect platform to deepen my knowledge and advance my career in this fast-evolving field.

As I pursue the AWS Cloud Practitioner certification, my goal is to build a strong foundation in cloud architecture, storage, networking, and security. This transition will allow me to merge my web development expertise with cloud computing to create innovative solutions that bridge application development and cloud infrastructure.

I am excited to embark on this new journey, tackle challenges, and contribute to projects that leverage the power of cloud computing. This move represents not just a career shift but also an opportunity to redefine how I can deliver value through technology.

My Journey: From Web Developer to AWS Cloud Practitioner

Stephen Lawal — Tue, 07 Jan 2025 18:23:12 +0000