vaporsyndicate

In Route 53, try setting the value of your A record to the ELB Classic Load Balancer for your ELB app. To get the full function of the EC2 scaling you want all your incoming traffic to go through the load balancer.

Also, in Route 53, try using the Test Record Set button at the top of the page in the Hosted Zone. That could give you some helpful clues in getting your redirect loop straightened. out.

One other point to check is your Origins and Behaviors in CloudFront.

DOMAIN_CURRENT_SITE should be set as your domain name in the wp-config.php file, however… you will need to set up your domain to use NS from AWS by setting up a hosted zone in Route 53 with an IPV4 (A record) set as an alias to point to your load balancers – not the EC2 instance.

And as a suggestion… There is a whitepaper from AWS that covers a good way to set this up using Elastic Beanstalk so you have the load balancing function across autoscaled EC2 instances as well as utilization of ElastiCache (for Memcache with multiple nodes) and Cloudfront as the CDN accessing an S3 bucket for static content storage.

NOTE: The paper is based on a single WP install, but as long as you make the changes to the wp-config.php and .htaccess files are done BEFORE you activate and set up W3 Total Cache, the directions are pretty good.

Resolved

Finally figured out a resolution to this issue. Thought I would share in case anyone else runs into the same problem…

The issue was caused because of when the WordPress installation was converted to multisite.

Even though this was a fresh install, the WP install should be switched over to multisite BEFORE setting up W3 Total Cache. I’m assuming that the cache files and configurations for a single site can create redirect loops when WP is switched to multisite.