If that seems counterintuitive then let me explain why. You will not make any changes to your Apache configuration. To work around this I added 301 as a possible valid response code, and voilá, the ELB can correctly determine the health (or lack thereof) of my EC2 instances. After some investigating I learned that - sometimes, depending on particulars of your server state - Apache might send a redirection code like say, 301, instead of a success code like 200. Additionally, Apache didn’t necessarily return a 200 status code even if the file could be pinged. To workaround these problem I created an empty file in the root of each of my WordPress sites named health.aws. Ok, so, in my case i host multiple virtual servers from the same Apache server, and this, along with the fact that all web sites are WordPress sites, caused problems with the default health check, which is to ping index.php. Mind you, there are additional details which hopefully are self explanatory. For any EC2 instance included in your Target Pool, if the success code returned matches up with the value in the routing configuration (the, “Success Code”) then the EC2 instance is considered healthy. The theory behind this is simple: AWS ELB’s will regularly try to ping a certain file. One of my more vexing problems regarded Health Checks.
Now then, to get the ELB to work at all I had to get creative with a couple of things. This article will hopefully help you to get your own ELB and SSL certificate up and running quickly and painlessly. After a long afternoon of banging my head against the keyboard I finally got HTTPS working.
Namely, WordPress can get stuck in an infinite loop of URL redirections whenever you try to redirect traffic to HTTPS. Unfortunately, getting an ELB with an SSL certificate to work with WordPress is tricky. Perform maintenance to your server without having to take your site offline.Add an automatically-renewing SSL certificate to your site for free.Horizontally scale your WordPress site.If you use an AWS EC2 instance to host your WordPress environment then there are many advantages to adding an AWS Elastic Load Balancer (ELB) to your infrastructure architecture. In recent past AWS introduced new serverless load-balancing models that are designed to sit in front of your web app architecture and importantly, these new ELB models are both highly-reliable and free.
0 kommentar(er)
