What's happening here

When a user types fintrack.qossim005.online in their browser, three things happen in order:

1. DNS Resolution (Route53) Route53 translates the domain name into the ELB's IP address. Think of it like a phonebook - you give it a name, it gives you an address.

2. TLS Termination (ACM + ELB) The browser connects to the ELB over HTTPS. The ELB uses the ACM certificate to decrypt the request. After decryption, the ELB forwards plain HTTP internally to NGINX. TLS never enters the cluster.

3. Traffic Routing (NGINX Ingress) NGINX receives the plain HTTP request and decides where to send it:

• URL starts with /api/ → backend pod (port 3001)
• Everything else / → frontend pod (port 80)

Step 1 - What Terraform Creates Automatically

When you run terraform apply, the dns module created:

• A Route53 hosted zone for qossim005.online - AWS now manages your DNS
• An ACM certificate for fintrack.qossim005.online
• A DNS validation record - Terraform added this to Route53 automatically so ACM could verify you own the domain
• An A record - fintrack.qossim005.online points to your ELB

You don't run these manually - Terraform handles them.

Step 2 - One-Time Namecheap Update

Route53 gives you 4 nameservers. You tell Namecheap to use them - this hands DNS control from Namecheap to Route53 permanently.

After terraform apply, your nameservers appear in the output:

nameservers = [
  "ns-1467.awsdns-55.org"
  "ns-1694.awsdns-19.co.uk"
  "ns-385.awsdns-48.com"
  "ns-905.awsdns-49.net"
]