Deploying a Static Portfolio Website Using AWS S3 (No Server Needed) 🚀

Alina Shujaat — Tue, 19 May 2026 20:17:44 +0000

As part of my Cloud Computing Internship, I completed my first project: The Global Launch — deploying a static website globally without provisioning any server.

Instead of using traditional hosting, I leveraged AWS S3 Static Website Hosting to host a portfolio website in a cost-effective and scalable way.

Project Objective

Build and deploy a personal portfolio/resume website that:

Loads globally over the internet
Requires no backend server
Uses cloud storage only
Is publicly accessible through a shareable URL

Tech Stack

HTML5
CSS3
AWS S3
AWS Bucket Policies

Implementation Steps
1. Built a Static Portfolio Website

Created a simple responsive website containing:

About Me
Skills
Projects
Certifications
Contact Information

*Code on GitHub *
Link: https://github.com/Alina-Shujaat/MY_Portfolio.git

Created an AWS S3 Bucket Go to AWS Console → S3 Configured a dedicated bucket for hosting website files. bucket: alina-portfolio-website

3. Uploaded Website Files

Uploaded:

index.html
style.css

4. Enabled Static Website Hosting

Configured S3 bucket properties:

Enabled static hosting
Set index document as:

inside bucket:

Properties → Static Website Hosting
Enable:

Host static website
Index document: index.html
Save.

AWS gives you an endpoint URL like:
http://alina-portfolio-website-2026.s3-website-us-east-1.amaz

5. Configured Public Access

Disabled block public access and added bucket policy
*Bucket → Permissions → Bucket Policy:
*

Final Result

Successfully hosted a live static website accessible globally through an AWS S3 endpoint URL.

Conclusion

This project was a great hands-on introduction to real-world cloud deployment.

Hosting websites without provisioning servers demonstrates how cloud services simplify infrastructure while reducing cost and complexity.

Looking forward to building more cloud projects during my internship.

🚀 Blue/Green Deployment, Ensuring Zero Downtime Deployments

Alina Shujaat — Thu, 13 Nov 2025 15:09:38 +0000

🧠 Introduction

In modern software development, high availability and continuous delivery are key goals. Users expect applications to be online 24/7 — and even a few seconds of downtime can affect user experience and trust.

That’s where Blue/Green Deployment comes in. It’s a DevOps strategy that helps teams deploy new versions of applications safely, test in production-like environments, and roll back instantly if needed.

🎯 What Is Blue/Green Deployment?

Blue/Green Deployment is a release strategy that uses two identical environments:

Blue Environment → The current live (production) version.
Green Environment → The new version (ready to replace Blue).

Instead of updating the running application directly, you deploy the new version to Green, test it, and then switch the traffic from Blue to Green once it’s stable.

This allows for:
✅ Zero downtime
✅ Easy rollback
✅ Safer updates

⚙️ How It Works (Step by Step)

Set up two environments — Blue (live) and Green (idle).
Deploy the new version of your application to Green.
Run tests and validation on the Green environment.
Once confirmed stable, redirect production traffic from Blue to Green (for example, via Load Balancer or Route 53 in AWS).
The Blue environment becomes idle and can be updated or kept as a rollback option.

Example: Blue/Green Deployment on AWS

In my project, I implemented Blue/Green deployment using AWS CodeDeploy, EC2, and Elastic Load Balancer (ELB).

Steps I followed:

Configured two EC2 environments (Blue and Green).
Used CodeDeploy deployment groups to manage traffic shifting.
Integrated Elastic Load Balancer (ELB) to handle live traffic switching.
Verified deployment using AWS CloudWatch and CodeDeploy logs.

This approach ensured zero downtime and quick rollback capability in case of any deployment issues.

📊 Benefits of Blue/Green Deployment

Zero downtime — Users experience no interruptions.
Instant rollback — Quickly revert if errors occur.
Safe testing — Validate new releases in a live-like environment.
Faster releases — Enable continuous delivery. 🧩 Real-World Use Cases

Rolling out new microservice versions safely.
Updating containerized applications in ECS or EKS.
Deploying web apps in EC2 or Lambda environments.
Testing infrastructure updates before full release.

💬 Conclusion

Blue/Green Deployment is one of the most effective DevOps strategies for minimizing risk during application updates. By maintaining two identical environments and switching traffic seamlessly, teams can achieve **continuous delivery with confidence.

If you’re deploying on AWS, CodeDeploy’s Blue/Green support makes the process smooth and automated.

✍️ Author

👩‍💻Alina Shujaat
Computer Science Major | Cloud & DevOps Enthusiast | AWS Learner
🔗 LinkedIn Profile

Forem: Alina Shujaat

Deploying a Static Portfolio Website Using AWS S3 (No Server Needed) 🚀

🚀 Blue/Green Deployment, Ensuring Zero Downtime Deployments