CLOUD COMPUTING | WEB HOSTING
AWS Static Website Deployment
This project demonstrates how to deploy and host a static website on AWS. It covers cloud networking, server configuration, web hosting, security groups, and connecting a custom domain.
PROJECT OVERVIEW
A static site on AWS
The goal was to make a static website available from an AWS-hosted server and connect it to a custom domain. Amazon EC2 provides the host, while Nginx serves the website files. The project materials also identify a VPC, security groups, and Route 53.
This page describes the services recorded for the project without assuming specific instance settings, network routes, security-group rules, or domain record values that are not documented.
ARCHITECTURE & TRAFFIC FLOW
From custom domain to website files
A high-level flow based on the project’s documented services.
- 01
Route 53
DNS connects the custom domain with the website host. The specific record type is not documented.
- 02
Amazon VPC
The EC2 host and its network access are part of the AWS networking layer.
- 03
Security Groups
Security groups control traffic to the server. The specific rules are not recorded.
- 04
EC2 & Nginx
Nginx serves the static website from the Amazon EC2 host.
The available project notes do not specify public or private subnet placement, route tables, allowed ports, or whether Ubuntu was used.
AWS SERVICES & TOOLS
The hosting components
- Amazon VPC
- Amazon EC2
- Nginx
- Security Groups
- Amazon Route 53
The existing project card confirms Route 53 as the DNS service. The operating system is not specified in the available project materials, so Ubuntu is not asserted here.
IMPLEMENTATION STEPS
The confirmed setup
- Deploy the static website on an Amazon EC2 host.
- Use Nginx to serve the website.
- Use the VPC and security groups for the AWS network and traffic-control layer.
- Connect a custom domain using Route 53.
The available project materials do not record the operating-system commands, DNS record values, or exact network and security-group configuration.
CHALLENGES & SOLUTIONS
What’s documented
The current project materials identify the services used but do not describe a specific deployment challenge or a confirmed fix. I have not added an unsupported troubleshooting story.
RESULTS & LESSONS LEARNED
A clear path to the site
The documented result is a static website hosted with EC2 and Nginx, using VPC networking, security groups, and Route 53 for a custom domain. No performance metrics are recorded, and this page does not claim that the AWS infrastructure is still running.
A general lesson from the setup is that a hosted site depends on several parts working together: the web server must serve the files, network rules must allow the required traffic, and DNS must direct the domain to the host.
EMBEDDED VIDEO WALKTHROUGH
Watch the deployment
LINKS & NAVIGATION