A Wedding Photography web application with frontend UI, backend integration, and database connectivity, deployed on a Three-Tier AWS Architecture.
- Home Page – Elegant landing page with photography showcase
- Gallery – Displays wedding photography collections
- Services – Detailed list of photography packages
- Contact Form – Submit inquiries via PHP backend
- User Registration & Login – Secure authentication with PHP & MySQL
- Payment Page – Payment processing interface
- Reviews – User feedback and testimonials
- Responsive Design – Styled with CSS for modern UI/UX
wedding-photography/
Wedding-Photography/ ├── frontend/ │ ├── html/ │ │ ├── home.html │ │ ├── gallery.html │ │ ├── services.html │ │ ├── services1.html │ │ ├── services2.html │ │ ├── services3.html │ │ ├── services4.html │ │ ├── services5.html │ │ ├── services6.html │ │ ├── contact.html │ │ ├── login.html │ │ ├── registration.html │ │ ├── payment.html │ │ ├── successPage.html │ │ └── review.html
│ └── css/ │ │ ├── home.css │ │ ├── gallery.css │ │ ├── services.css │ │ ├── contact.css │ │ ├── login.css │ │ ├── review.css │ │ └── style.css │ └── images/ │ ├── mc.png │ └── pp.png
├── backend/ │ ├── php/ │ │ ├── contact.php │ │ ├── login.php │ │ ├── payment.php │ │ └── database.php └── README.md
This project is deployed on AWS Three-Tier Architecture:
-
Presentation Tier (Frontend)
- HTML, CSS, JavaScript
- Hosted on AWS EC2 (public subnet) or S3 + CloudFront
-
Application Tier (Backend)
- PHP files (
login.php
,contact.php
,payment.php
) - Runs on Apache/Nginx inside a private subnet EC2 instance
- PHP files (
-
Database Tier
- MySQL hosted on AWS RDS (private subnet)
- Connected via
database.php
-
Networking Setup
- VPC with public & private subnets
- Route Tables for traffic flow
- Internet Gateway (IGW) for frontend access
- NAT Gateway for backend → internet traffic
- Security Groups & NACLs for security
AWS 3‑Tier Architecture Overview
The three tiers are:
Tier Purpose AWS Components / Characteristics Web / Presentation Tier Handles incoming client requests, serves static content, TLS termination, load balancing Public subnets, Internet Gateway, Load Balancers (ALB / ELB), Web servers (EC2 / Auto Scaling) Application / Logic Tier Business logic, processing, internal APIs Private subnets, limited inbound access (only from Web tier), NAT or outbound Internet via NAT Gateway if needed Database / Data Tier Data storage, persistent databases or caches Private subnets, highly restricted access (only from App tier), possibly multi‑AZ RDS, etc.
📸 Screens (Pages)
home.html → Homepage
gallery.html → Wedding gallery
services.html → Services offered
contact.html → Contact form
login.html / registration.html → User auth
payment.html / payment.php → Payment integration
review.html → Client reviews
The diagram will include In ThreeTier Architecture:
VPC
Public Subnet → EC2 (Frontend / Web Tier)
Private Subnet → EC2 (Backend / App Tier)
Private Subnet → RDS (Database Tier)
Internet Gateway + NAT Gateway
Route Tables showing connectivity