I will deploy nextjs nodejs app with docker nginx ci cd on aws vps
Senior DevOps and Network Security Engineer and Linux Expert
About this Gig
I've been a sysadmin/neteng long before "DevOps" became a title. That means when I set up your pipeline, I'm not just copying a YAML template I know what happens when the network hiccups, when the disk fills up, when the OOM killer visits at 3 AM.
What you get:
Dockerfile written for production multi-stage, non-root, distilled to <100MB, not the 1.2GB default
Nginx with proper TLS (Let's Encrypt, auto-renew via systemd timer), security headers, gzip, cache rules for _next/static
GitHub Actions workflow: build test Trivy scan deploy smoke test rollback on failure
Zero-downtime via systemd (or PM2 if you prefer) old container stays up until new one passes health check
UFW + fail2ban baseline because exposed SSH on port 22 is how incidents start
Runbook (PDF) architecture diagram, troubleshooting tree, "what to do when..." so you're not calling me at midnight
Stack I work daily: GitHub Actions / GitLab CI, Docker, Nginx/Traefik, AWS (EC2, RDS, ALB, S3), Hetzner/DO/VPS, Linux hardening, Terraform when you need IaC.
Packages:
Basic one service, prod only, 3 days
Standard FE + API + DB, staging + prod with approval gate, 5 days
Premium LB, auto-scale, Prometheus/Grafana/Loki
My Portfolio
Other DevOps Engineering Services I Offer
FAQ
How do you access my server? Is it secure?
You add my SSH public key to ~/.ssh/authorized_keys (or grant temporary IAM access for AWS). I never ask for passwords. Key is removed after delivery.
What if my app isn't Next.js / Node.js?
I support Python (FastAPI/Django), Go, PHP (Laravel), Java (Spring Boot). Message me first — I'll confirm the stack and adjust the Dockerfile/health checks accordingly.
Will there be downtime during deployment?
Basic: ~15s (systemd restart). Standard/Premium: Zero-downtime — new container must pass health checks before traffic switches. Failed deploy = automatic rollback.

