Help Center/ ROMA Connect/ User Guide(new)/ Instance Management/ Creating a ROMA Connect Instance/ Preparing Resources
Updated on 2025-07-17 GMT+08:00
View PDF

Preparing Resources

Before creating a ROMA Connect instance, you need to ensure availability of resources, including a virtual private cloud (VPC) and subnet. Each ROMA Connect instance is deployed in a VPC and bound to a subnet. In this way, ROMA Connect provides an isolated virtual network environment that can be easily configured and managed by users.

Required Resources

The following table lists the resources required by a ROMA Connect instance.

Table 1 Resources

Resource

Requirements

Operation

VPC and subnet

Different ROMA Connect instances can use the same or different VPCs and subnets based on site requirements. Note the following when creating a VPC and subnet:

  • The created VPC and ROMA Connect must be in the same region.
  • Retain the default settings unless otherwise specified. RCU instances do not support IPv6.
  • To enable communication between instances across VPCs, ensure that the peer VPC CIDR block does not conflict with the internal CIDR block.

    The mapping between VPC CIDR blocks and internal CIDR blocks is as follows:

    • CIDR block 10 corresponds to the internal CIDR block 172.31.0.0/16.
    • CIDR block 172 corresponds to the internal CIDR block 192.168.0.0/16.
    • CIDR block 192 corresponds to the internal CIDR block 172.31.0.0/16.
    • The default VPC CIDR block corresponds to the internal CIDR block 192.168.0.0/16.

For details on how to create a VPC and subnet, see Creating a VPC. If you need to create and use a new subnet in an existing VPC, see Creating a Subnet for the VPC.

.