Production Traffic Cutover via Application Load Balancer
Operational Challenge
Production traffic cutover was required for the WordPress platform on app.enterprise-platform.com and its apex domain to a new EC2 instance (INTERNAL-HOST-01, i-00000000) in AWS us-east-1. The multi-tenant Application Load Balancer (ALB) ENV-SERVICE-RESOURCE managed several workloads on a single HTTPS listener (port 443). The operation demanded zero downtime, elimination of slow Route 53 DNS propagation windows, avoidance of ACM TLS certificate reissuance, continuous availability for neighboring tenant domains, and an immediate rollback mechanism in case of production discrepancies.
Technical Diagnosis
Prior to cutover, Target Group health was verified via aws elbv2 describe-target-health, validating that instance i-00000000 was healthy on port 80. On the target host, wp-config.php was inspected to ensure WP_HOME and WP_SITEURL enforced HTTPS to the canonical domain. Local curl tests emulating the X-Forwarded-Proto: https header confirmed the absence of SSL termination redirect loops, returning HTTP 200 under PHP 8.5.12 and canonical HTTP 301 redirects from apex to www. Listener rule priority 12 was audited via aws elbv2 describe-rules to inspect existing Host-Header condition boundaries before modification.
Implemented Solution
The cutover was executed by modifying listener rule priority 12 on the ALB using aws elbv2 modify-rule, adding production domains to the host-header condition to atomically route traffic to the target group. External HTTP/2 validation confirmed HTTP/2 200 responses with the x-powered-by: PHP/8.5.12 header and clean canonical 301 redirects. Adjacent tenant services were verified to ensure uninterrupted operation on independent PHP 8.2.20 runtimes. An immediate rollback procedure was documented using AWS CLI to revert rule 12 conditions to the legacy instance via the default listener rule, though contingency execution was not required.
Key Metrics & Impact
/>Technology Stack
/>