This should be somewhat fun. Its time to really get my feet wet with AWS and that means experiencing the pain as well as the knowledge. Perhaps most of the pain is experienced when you get the bill, but for now we will focus on the technical chops of moving things over to a new instance.
Process Steps:
- Backup existing data stores — MySQL db for wordpress.Wow — headache and a half. A common syntax in several walk-throughs all had me trying this:mysqldump -u [username] -p [password] [databasename] > [backupfile.sql]but…. because of the way my hosting service has their MySQL accounts configured, the username and the database name are merged making my syntax incorrect. Fortunately they listed this constraint on their faq site:
mysqldump -p user_name > DESIGNATED_DATABASE_BACKUP_NAME.sql
Not only did I have an extra parameter in there ( the username and the db name are merged ) but there is only one name that you are allowed to give to a backup of your db.
Whatever floats their integers….
- Create new web server instance on AWS — using new stack mind you…Man… we are already 1:50 into this project and pizza is looking very far away. Time for a run. Back in 30… and i just realized that all further commits are going to have to be manually ported over after I import the backup… lol.
- Upload site files and data store.
- Configure site components and bring site up.
- Change name server settings with registrar to point domain to migrated site.
- The internet is amazing! Ordering Pizza.
Started Sunday, July 23, 2017 at 11:51 am. Lets see how long this takes. No sleep til’ Brooklyn.