Help Center/ Huawei Cloud Flexus_Huawei Cloud Flexus L Instance/ FAQs/ Network/ How Does FlexusL Instances Communicate with Each Other and with Other Cloud Resources Over a Private Network?
Updated on 2025-08-04 GMT+08:00
View PDF
Share

How Does FlexusL Instances Communicate with Each Other and with Other Cloud Resources Over a Private Network?

A FlexusL instance has the following default network configurations when it is created:

  • Public network: By default, a fixed elastic IP address (EIP) and VPC (vpc-default-smb) are assigned to a FlexusL instance. They cannot be changed.
  • Private network: By default, a fixed private IP address (172.31.x.x) and subnet (subnet-default-smb) are allocated to a FlexusL instance. They cannot be changed.

    If the network segment of an existing FlexusL instance is 192.168.x.x, you need to unsubscribe from the FlexusL instance and delete the VPC and its associated subnets and security groups. Then, the network segment of the new FlexusL instance is 172.31.x.x.

The following table describes the network connectivity between FlexusL instances and other cloud resources (such as ECSs and cloud databases). You can select a proper solution as needed.

Table 1 FlexusL instance connectivity over a private network

Region

Account

Between FlexusL Instances

FlexusL Instances and Other Cloud Resources (Such as ECSs and Cloud Databases)

Same region

Current account

By default, they can communicate with each other over a private network in the same VPC.

They can only communicate with each other over a private network in the same VPC (which is vpc-default-smb).

Solutions for communication over a private network:

Different accounts

By default, they are in different VPCs and cannot communicate with each other over a private network.

By default, they are in different VPCs and cannot communicate with each other over a private network.

Solutions for communication over a private network:

Different regions

Same account

By default, they are in different VPCs and cannot communicate with each other over a private network.

By default, they are in different VPCs and cannot communicate with each other over a private network.

For details about communication over a private network, see Using a Cloud Connection to Connect VPCs in Different Regions.

Different accounts

By default, they are in different VPCs and cannot communicate with each other over a private network.

By default, they are in different VPCs and cannot communicate with each other over a private network.

For details about communication over a private network, see Using a Cloud Connection to Connect VPCs in Different Regions and Accounts.
  • If the local and peer VPCs have overlapping CIDR blocks, the VPC peering connection may not be usable. For details, see VPC Peering Connection Notes and Constraints.
  • When configuring a cloud connection, ensure that the subnet CIDR blocks of all network instances that use the same cloud connection do not overlap. Otherwise, the cloud connection may not take effect. For details, see Cloud Connect Notes and Constraints.
Parent Topic: Network