Scalable AWS Infrastructure Deployment
Designed and deployed scalable cloud infrastructure on AWS using EC2, Elastic Load Balancer and Auto Scaling to ensure high availability and performance optimization.
$ whoami
▌
3 years running production infrastructure — AWS · Linux · Networking · Security · Hosting
System Administrator & Cloud Architect with 3 years of experience in AWS cloud infrastructure, Linux server administration, networking, security hardening, and website hosting. Skilled in server setup, cloud deployment, DNS configuration, SSL installation, reverse proxy design, and automated backups.
Experienced in managing secure and scalable environments with minimal downtime — intrusion prevention with fail2ban, firewall management with UFW/iptables, and proactive log monitoring. Dedicated to delivering reliable IT support and efficient technical solutions.
# production stack I run daily
cloud:
provider: AWS
services: [EC2, S3, VPC, Route53, ELB, AutoScaling]
os:
linux: [Ubuntu, RHEL]
stack:
web: Apache
db: MySQL
panels: [cPanel/WHM, CyberPanel]
automation:
- bash + crontab
- rsync incremental backups
security:
- Certbot SSL
- Cloudflare WAF / DNS
- SPF · DKIM · DMARC
uptime_target: "24/7"
Indev Consultancy Pvt. Ltd. — Noida, UP, India
Designed and deployed scalable cloud infrastructure on AWS using EC2, Elastic Load Balancer and Auto Scaling to ensure high availability and performance optimization.
Configured secure AWS networking environments — VPC, VPC Peering, Route Tables, Elastic IPs and Route 53 — with firewall-level security controls protecting production.
Connected 8 in-house servers through a single static IP via reverse proxy configuration — secure routing, centralized access management and optimized internal traffic flow.
Generated and deployed SSL certificates using Certbot with Apache on Linux. Configured secure HTTPS environments and optimized server configuration.
Developed automated backup solutions using rsync and crontab scheduling for over 50 websites, with incremental backup strategies and disaster recovery planning.
Migrated WordPress, CodeIgniter 4 and CMS platforms between GoDaddy, SiteGround, Hostinger, AWS and local servers — data integrity with near-zero downtime.
Deployed fail2ban across production Linux servers — real-time parsing of auth logs, automatic IP banning after repeated failed password attempts, custom jail rules for SSH, Apache and panel logins.
Integrated Cloudflare for DNS management, IP masking, SSL security and DDoS protection. Improved performance with load balancers and DNS optimization.
The production AWS architecture I design and run — watch requests travel from users through Cloudflare, Route 53 and the load balancer into the Auto Scaling VPC, with rsync backups flowing to S3.
A real project: 8 in-house servers published through one static IP. The reverse proxy reads the Host header of every request and routes it to the right internal machine — one public address, eight services, centralized SSL and access control.
# one vhost per service — all behind 203.0.113.10
<VirtualHost *:443>
ServerName wp.company.com
SSLEngine on
SSLCertificateFile /etc/letsencrypt/live/wp.company.com/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/wp.company.com/privkey.pem
ProxyPreserveHost On
ProxyPass / http://192.168.1.11:8081/
ProxyPassReverse / http://192.168.1.11:8081/
</VirtualHost>
# router: forward ONLY 80/443 to the proxy box
# wp.company.com → 192.168.1.11 (WordPress)
# crm.company.com → 192.168.1.12 (CodeIgniter)
# mail.company.com→ 192.168.1.14 (webmail)
# …8 subdomains → 8 internal servers, 1 public IP
✔ Internal servers are never exposed — only the proxy has a public route.
✔ SSL certificates renewed centrally with Certbot on the proxy.
✔ fail2ban on the proxy bans brute-force attempts for all 8 services at once.
✔ Adding server #9 = one new vhost + DNS record. No new IP needed.
How I protect servers in real time: fail2ban tails the auth log, counts failed password attempts per IP, and bans the attacker at the firewall after 5 strikes. Watch it happen live below — this site's own admin login uses the same rule (5 wrong passwords = 15-minute IP ban).
[sshd]
enabled = true
port = ssh
filter = sshd
logpath = /var/log/auth.log
maxretry = 5 # strikes before ban
findtime = 10m # window for strikes
bantime = 1h # firewall ban duration
[apache-auth]
enabled = true
port = http,https
logpath = /var/log/apache2/error.log
A live network-operations view. Host metrics below are served in real time by this very
Apache/PHP server (api/stats.php) — the racks and traffic simulate a production floor.
A real interactive shell. Type help to explore my profile the sysadmin way.