Migrate service to another cloud or region#
When migrating a service, the migration happens in the background and does not affect your service until the service has been rebuilt at the new region. The migration includes the DNS update for the named service to point to the new region. Most of the services have usually no service interruption expected. However, for services like PostgreSQL®, MySQL and Redis®*, it may cause a short interruption (5 to 10 seconds) in service while the DNS changes are propagated.
The short interruption mentioned above does not include the potential delays caused by client side library implementation.
When spinning a new Aiven service, you are not tied to a cloud provider or region. Your services can be migrated to better match your needs. Services can be moved to another cloud provider, or another region within the same provider, or both.
Log in to the Aiven console.
Go to your Services, and open the service you want to scale.
On the Overview tab, scroll down to Migrate Cloud.
Select the new service plan and new tier, if required.
Your service will be in a Rebalancing state, and once complete will be on the new cloud. The service will still be accessible through the process.
The Service URI remains the same after the migration.
You can also use the dedicated service update function to create a new service user via the Aiven CLI.