Migrating a service between networks

Timescale Cloud services may be migrated between VPCs within a Cloud project, and may also be migrated to and from the public network. Typically, once you have attached your service to a VPC, it should remain attached to ensure that your applications running in your AWS VPC will have continued connectivity to your service.

warning

Timescale Cloud uses a different DNS name for a Timescale service once it has been attached to a VPC. This means that you will need to update your connection string if migrating a service from the public internet into a VPC, or vice-versa.

To migrate a Timescale Cloud service between VPCs, or to migrate to/from the public network, navigate to the Services Dashboard, select the service you wish to migrate, click the Operations tab in the service details view, and click the VPC tab within the Operations view. From this view, you have a few options depending on the state of your service.

warning

After migrating your Timescale Cloud service, please allow a few minutes for DNS propagation. If you receive DNS errors indicating that the DNS name could not be resolved, this indicates that more time is needed for DNS propagation.

Migrate from public network to VPC

When your service is attached to the public network, you have the option to select a VPC to migrate your service into.

Once you have selected the VPC to migrate your service into, click Attach VPC. You will then be prompted to confirm the migration.

After confirming the migration, your service will be attached to the VPC you selected. These operations are not immediate, and also involve DNS changes which may take a few minutes to propagate.

As mentioned on the confirmation modal, you will need to update your connection string in order to connect to your service after migration. The Service URL back on the service details page is already updated to include the new DNS info, and should be used for connecting to your service.

tip

When migrating your service into a VPC, ensure that your AWS VPC's security groups allow network access from your AWS VPC to the Cloud VPC which your service has migrated into. Security group configuration was previously covered as part of peering connection setup. Double-check to be sure, otherwise you will not be able to connect to your Timescale Cloud service.

Migrate between VPCs

When your service is already attached to a VPC, you have the option to migrate it to another VPC within the same project.

To migrate between VPCs, expand the Migrate into another VPC menu and select the VPC to migrate your service to. Then click Migrate. You will then be prompted to confirm the migration.

After confirming the migration, your service will be detached from its previous VPC and attached to the new VPC you selected.

In the case of VPC to VPC migration, the Service URL connection string will not be updated, only the IP address which the DNS name is associated with will be updated. Please allow a few minutes for the DNS record changes to propagate.

tip

When migrating your service between VPCs, ensure that your AWS VPC's security groups allow network access from your AWS VPC to the Cloud VPC which your service has migrated into. Security group configuration was previously covered as part of peering connection setup. Double-check to be sure, otherwise you will not be able to connect to your Timescale Cloud service.

Migrate back to public network

When your service is already attached to a VPC, you have the option to migrate it back to the public network.

To migrate your service back to the public network, click Migrate back to public network. You will then be prompted to confirm the migration.

After confirming the migration, your service will be detached from its previous VPC and made accessible over the public internet.

As mentioned on the confirmation modal, you will need to update your connection string in order to connect to your service after migration. The Service URL back on the service details page is already updated to include the new DNS info, and should be used for connecting to your service.

Found an issue on this page?

Report an issue!

Related Content