DevOps Engineering Intern · DaFi Labs

Building and shipping things
on the cloud.

I'm Rameen Zafar, a Computer Science student learning infrastructure the practical way — registering domains, wiring DNS, deploying to Vercel and AWS Amplify, and keeping an eye on the bill while I do it.

Deployed on
Vercel + AWS Amplify
DNS managed via
Route 53
Mail
Zoho + Resend

I like the part where it actually goes live.

Most of what I know about cloud infrastructure I learned by breaking it first. A domain that wouldn't resolve taught me more about DNS propagation than any diagram, and a misconfigured SPF record taught me why deliverability is its own discipline.

Right now I'm working through the DevOps Engineering Internship at DaFi Labs, where the focus is on the full path from source code to a live URL: version control, build pipelines, hosting platforms, custom domains, and the AWS services that sit underneath all of it.

I care about setups that are simple enough to explain to someone else. If I can't draw the request path on a whiteboard, I don't understand it yet.

What I work with

Cloud & AWS

EC2, S3, IAM, Route 53, Amplify, CloudWatch, Cost Explorer.

  • IAM policies
  • S3 static hosting
  • Route 53
  • Amplify Hosting

Deployment

Git-based continuous deployment on Vercel and AWS Amplify, with build specs and preview environments.

  • Vercel
  • Amplify CI/CD
  • Build specs
  • Preview builds

Domains & DNS

Registrar setup, nameserver delegation, and the record types that make it all resolve.

  • A / AAAA
  • CNAME
  • MX
  • TXT · SPF · DKIM

Email Infrastructure

Business mailboxes on a custom domain, plus transactional email sent straight from code.

  • Zoho Mail
  • Resend
  • ZeptoMail
  • SendGrid

Linux & Tooling

Comfortable on the command line — the place where most infrastructure work actually happens.

  • Bash
  • SSH
  • Git
  • Node.js

Cost Awareness

Reading Cost Explorer, setting budget alerts, and tearing down resources I'm done practising on.

  • Cost Explorer
  • Budgets
  • Free tier limits

Selected projects

01 Cloud Deployment

This portfolio, deployed twice

The same static site running on two independent hosting platforms — Vercel and AWS Amplify — both wired to a custom domain. Building it twice was the point: it made the differences between platform DNS models obvious in a way reading about them never did.

  • HTML / CSS / JS
  • Vercel
  • AWS Amplify
  • Custom domain
02 Email Infrastructure

Business email on a custom domain

A professional mailbox served by Zoho Mail, verified through domain TXT records and routed with MX records. On top of it, a small Node.js service that sends transactional mail through three different providers behind one interface.

  • Zoho Mail
  • Resend
  • ZeptoMail
  • SendGrid
  • SPF / DKIM
03 DNS

Route 53 as the single source of truth

One hosted zone holding every record for the domain — web hosting, mail delivery, and sender authentication — with the registrar delegating to Route 53 nameservers. One place to look when something stops resolving.

  • Route 53
  • Hosted zones
  • ALIAS records
  • Nameserver delegation

How this site reaches you

A request for this page travels through every piece of infrastructure listed below. Nothing here is decorative — it's the actual path.

  1. Registrar

    The domain is registered for a year and its nameservers point at the Route 53 hosted zone.

  2. Route 53

    The authoritative DNS answer lives here — A/ALIAS for the site, MX and TXT for mail.

  3. Amplify & Vercel

    Both platforms build from the same Git repository on every push and serve over HTTPS from their CDN edge.

  4. Your browser

    Static HTML, CSS, and a little JavaScript. No framework, no build step, nothing to wait for.

Let's talk

The form below posts to a serverless function that sends the message through Resend to my business mailbox. If you'd rather use your own mail client, that works too.

Prefer email?

hello@rameenzafar.me