This project demonstrates the design and implementation of a secure AWS VPC architecture using public and private subnets.
- AWS VPC
- EC2
- Security Groups
- Route Tables
- Internet Gateway
- Linux (Amazon Linux 2023)
- Apache HTTP Server
- Production VPC (10.0.0.0/16)
- Public Subnet (10.0.1.0/24)
- Private Subnet (10.0.2.0/24)
- Internet Gateway
- Public Route Table
- Public Web Server
- Private Application Server
- Bastion Host Architecture
- Public server accessible from internet
- Private server has no public IP
- SSH allowed only through Bastion Host
- ICMP restricted using Security Groups
- SSH access verified
- Public to private communication verified
- Apache deployment verified
- Browser access verified
- Created Production VPC (10.0.0.0/16)
- Created Public Subnet (10.0.1.0/24)
- Created Private Subnet (10.0.2.0/24)
- Created and attached Internet Gateway
- Configured Public Route Table
- Associated Public Subnet with Route Table
- Created WebServer Security Group
- Launched Public EC2 Instance (Bastion Host)
- Installed and configured Apache HTTP Server
- Created PrivateServer Security Group
- Launched Private EC2 Instance
- Configured ICMP and SSH access from Bastion Host
- Verified Public-to-Private connectivity using ping
- Connected to Private Server through Bastion Host
- Verified Apache deployment and website accessibility
- AWS VPC Design
- Subnet Planning
- CIDR Management
- Internet Gateway Configuration
- Route Table Management
- Security Group Configuration
- EC2 Deployment
- SSH Troubleshooting
- Linux Administration
- Apache Web Server Deployment
- Bastion Host Architecture
- Difference between public and private subnets
- How route tables control traffic flow
- Security Group best practices
- Bastion Host implementation
- Web server deployment on AWS
- Add NAT Gateway
- Implement Network ACLs
- Configure Application Load Balancer
- Deploy Multi-AZ Architecture
- Automate Infrastructure using Terraform