Connected

Wildcard domain resolved to CloudFront successfully
—

Traffic & certificate flow

*.wildcard-poc.zgold-dev.razer.com wildcard routing across Route 53, ACM, CloudFront, EKS/Istio and merchant domain forwarding (*.cname-poc.zgold-dev.razer.com)
Merchant domain forwarding EKS cluster (Istio mesh) 🖥️ merchant.cname-poc... merchant storefront (CNAME) 🌐 Merchant DNS merchant.cname-poc... CNAME → tenant-a.wildcard-poc... 📜 AWS Certificate Manager issues wildcard cert for *.wildcard-poc... + merchant CNAME 📥 Content Onboarding requests cert, adds SAN after DNS validation succeeds 🖥️ *.wildcard-poc.zgold-dev.razer.com any tenant subdomain 🗺️ Route 53 *.wildcard-poc... → CloudFront 🛡️ AWS WAF SQLi / XSS / rate limiting ☁️ CloudFront terminates TLS, nearest edge POP ⚖️ Network LB *.wildcard-poc... *.wildcard-poc.../api 🪣 Amazon S3 *.wildcard-poc.../assets 🖼️ Vue.js (CSR) static assets bundle 🐳 Istio ingress frontend-service .app-space.svc 📦 Frontend App Node.js · EKS pod 📦 Backend App Java Spring · EKS pod provide CNAME name + value create DNS record (tenant-a → CF) request cert ISSUED closest CloudFront edge inspect terminate TLS *.wildcard-poc... *.wildcard-poc.../api decrypt HTTPS traffic (wildcard + merchant SAN)
DNS / Edge routing WAF / security ACM / onboarding EKS / Istio compute S3 / static assets

This connection

Live details for the request that loaded this page