This blog is now hosted on an AWS micro instance. It feels a little weird to no longer administer my own database or DNS server. I still have postfix for my mail server.
The migration was largely uneventful. I definitely recommend migrating the database first, updating the existing wordpress server to point to the new database and verify everything still works, and then migrating the wordpress server itself.
Route 53 is a lot easier to use than manually editing bind9 configuration files.
Permalinks no longer work. I’ve spent hours verifying that the old and new configurations are identical (with the sole exception of the apache release) but they work on the old server and do not work on the new server. I’ve verified there’s no references to the old server name in the database or files. I’ve turned off plugins. All to no avail. Maybe it will be clearer tomorrow.
Security groups still require some thought. I edited the RDS security group to grant access to the database from the old server but needed to edit the EC2 instance’s security group to include the RDS security group instead of listing an explicit IP address.
I couldn’t get SES working for system email traffic. I’ve used it for application email before and this is a verified domain but when I try to use it as a smarthost the hostname/domain name of outbound mail is changed to the internal AWS values. I’m fairly certain this is done by SES. It’s not a big burden since I don’t need to handle inbound mail.