- Create new instance: smooth
- Create new static ip: smooth
- Export / Import content from old instance to new: ok
What is left:
- setup HTTPS for new instance
- solve for new instance able to send email
- move DNS routing to new instance
Setup HTTPS for the new instance:
- https://docs.aws.amazon.com/lightsail/latest/userguide/amazon-lightsail-enabling-https-on-wordpress.html
- Also: https://44.235.24.161/?p=59 (willaford.com/?p=59)
- Check the firewall rules — back to the console, again. Careful! You must to to the instance, then the networking tab. Going to the networking section of lightsail then selecting the instance gives you something *very* different. OK. Yes, 22, 80, 443 are all configured.
- I think we are going to have issues with lightsail domains conflicting with existing Route53 Configuration. Checking.
- OKAY — going back and swapping in the static IP in raw DNS config in route53. Manual change. No CDK, pipeline, MCM or checklist
- at 5:36 PM Pacific Time 22 October 2026, William decided to use the sharpest tool on the internet [dns] without guardrails.
- Testing the change by saving this and reloading from willaford.com. Expected result is non-secure [no https] routing to this location.
- Notably, the old instance does not have this update. willaford.net and willafor.org will resolve to the old instance until those are changed.