I've an m4.4xlarge instance running Percona MySQL 5.7 on Ubuntu 16.04 and I plan to change the instance family to m5a.4xlarge. Are there any unforeseen problems that I might run into when doing this or is it just a matter of shutting down the instance, changing the instance type and restarting it again? Are there any linux kernel level compatibility issues that I need to look into?
-
Make an AMI of the m4 instance, fire up an m5 instance with that AMI, and run your tests.– ceejayozAug 23, 2019 at 19:57
-
Should work fine as per answer below. Note that the device names can change, and you might need to install a driver - can't remember what it was but it's related to Nitro. Suggest you take a snapshot, create an AMI, and test it with the new instance type before you change the production instance type.– TimAug 25, 2019 at 4:08
Add a comment
|
1 Answer
The only potential data issue would be if you used instance store (as opposed to Elastic Block Storage) for the disk, but that's unlikely. Also, the IP address of the instance will change, so any applications that depend on that IP will need to be configured with the new IP. And as @ceejayoz pointed out, it's easy enough to test!
-
Will the private IP change as well? For public IP, we have associated an elastic IP to this instance.– DebAug 23, 2019 at 20:18
-
@Deb Yes, the private IP will be different. You can reassign the Elastic IP to the new instance. Aug 23, 2019 at 20:38
-
Whenever I've rebooted the instance or upgraded the instance within the same instance family, I've not seen the private IP changing. Are you saying that this does change when we change from instance family to the other?– DebAug 23, 2019 at 20:41
-
Yes the private IP will change - the instance will need to stop & start, which causes this. Rebooting is different and doesn't cause an IP to change.– wrk2bikeAug 23, 2019 at 20:47
-
In the same instance family, I've actually upgraded by stopping the instance, changing the instance type and starting the instance a good number of times in the past. But I've not seen the private IP change. Quoting from the aws docs - docs.aws.amazon.com/AWSEC2/latest/UserGuide/… "A private IPv4 address remains associated with the network interface when the instance is stopped and restarted, and is released when the instance is terminated."– DebAug 23, 2019 at 20:56