Skip to main content

Intranet Connectivity

This page describes how the Cloud Hosting service accesses other resources in your Tencent Cloud account, such as cvm, mysql, redis, etc.

tip
  • Currently, the Intranet Connectivity feature is only supported in Standard Edition and above plans. The Personal Edition does not currently support this feature.
  • If you are using the Personal Edition and need this feature, please go to the Package Management page to upgrade your plan.

By default, the Cloud Hosting service and other resources under your Tencent Cloud account (such as cvm, mysql, redis, etc.) cannot communicate over the internal network. If you need to access other resources, you must enable the Intranet Connectivity feature for the service.

Enabling Intranet Connectivity

Prerequisites:

  • You need to create a VPC network segment in Tencent Cloud Virtual Private Cloud.
  • The region must be set to Shanghai region.
  • Use a subnet mask >= 22 for the VPC network segment whenever possible.
  • The subnet mask should be <= 28. This subnet will be occupied by the Cloud Hosting service. Please avoid creating other resources in this subnet to prevent any impact on the Cloud Hosting service.

Enable:

    1. Log in to Tencent Cloud Hosting.
    1. Select the service for which you want to enable the intranet connectivity function, and click on
    1. Click on
    1. Click the edit function in VPC
    1. Select the VPC you created and its subnet.
    1. Click Save and wait for the service update to complete.
    1. After the service update is complete, the Cloud Hosting service can access resources within the VPC. When creating resources such as mysql and redis, select this VPC.

Usage Notes

  • Ensure that the VPC network has allocatable IP addresses; otherwise, the Cloud Hosting service instance may fail to start due to the inability to allocate an IP.
  • If the service accessing the VPC needs to connect to the public network, ensure that the VPC has a NAT gateway and the route configuration is correct. For more information, see NAT Gateway Description.