Five straight hours of trying to figure this out has left me exhausted, I cannot think of sleeping until I had this system fully configured. I understand that tomorrow may be problematic but I can sleep good tonight.
What I learned:
- Never use a default Linux AMI to install WordPress; its a waste of time…
- WordPress is very finicky when changing IP addresses, in order to swap around IP addresses either you need PHP access or you will need to set the system up correctly from the start. Make sure to setup your Elastic IP from the start to avoid being booted off a shared public IP.
- SSL certifications don’t exist for EC2 in the same way it exists for Cloudfront or application load balancers, termination will need to occur on the EC2 instance itself. fortunately Bitnami has a SSL certificate configuration tool that makes it easy to setup… see point 1.