Finally, I managed to migrate my blog from GoDaddy to Amazon Lightsail, and everything looks good so far. Thanks to Amazon Lightsail for providing a static public IP (188.8.131.52).
It’s really simple to migrate your blogs from any other hosting Amazon Lightsail, details information can be found here.
They have very attractive pricing, which is one of the reason I moved from GoDaddy to Amazon (recently GoDaddy started charging additional TAX). I am currently using $5 plan which is also free for first month.
It is very common that sometimes we disabled the network adapter from VM to trouble shoot some network related issue, and after doing so we suddenly realize that we made a big mistake, especially if we do it on Azure VMs. Suddenly we lost all the communication to the VM, no RDP, no PowerShell, and VM got completely isolated from the network. If AWS, we could fix this very easily by adding one additional network adapter (ENI), but in Azure, it will be little bit tricky, coz currently Azure VM does NOT support adding or removing NICs after a VM is created, Multi-NIC can only be applied when a VM is created. So, fixing this will be bit trickier for Azure VMs. If you search “Disabled network card on Azure VM“, you will get multiple solution, but unfortunately those are not working with newer Azure VM (Resource Manager).
To fix this issue, you have to follow the steps bellow, and you will be able to re-enable the adapter.
AWS expanding their footprint again, this time with a new region in Mumbai, India. AWS customers in the area can use the new Asia Pacific (Mumbai) Region to better serve end users in India.
The new Mumbai region has two Availability Zones, raising the global total to 35. It supports Amazon Elastic Compute Cloud (EC2) (C4, M4, T2, D2, I2, and R3 instances are available) and related services including Amazon Elastic Block Store (EBS), Amazon Virtual Private Cloud, Auto Scaling, and Elastic Load Balancing.