Help Center/ ROMA Connect/ User Guide/ Instance Management/ Creating a ROMA Connect Instance
Updated on 2026-01-19 GMT+08:00
View PDF

Creating a ROMA Connect Instance

Before using ROMA Connect, create a ROMA Connect instance. Each instance is an independent resource space, with its resources isolated from others. You can use multiple instances depending on your service needs.

If you delete an instance, all resource data created in the instance will be deleted. Exercise caution when performing this operation. Before deleting an instance, back up data by exporting asset data of the instance.

Required 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.

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

Table 1 Resources

Resource

Requirement

Reference

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.

.

Creating a ROMA Connect Instance

  1. Go to the Buy ROMA Connect Instance page.
  2. On the Buy ROMA Connect Instance page, configure basic instance information.
    Table 2 Basic configurations

    Parameter

    Description

    Region

    Select the region where the instance resides. Instances in different regions cannot communicate with each other. Select the nearest region to reduce network latency.

    Resource

    Select ROMA Connect Instance.

    AZ

    Select the availability zone (AZ) where the instance resides. Different AZs are physically isolated but can communicate with each other through a private network.

    • To enhance ROMA Connect availability, create instances in different AZs.
    • To shorten network latency, create instances in the same AZ.

    CPU Architecture

    The available value options depend on the CPU architecture supported by the environment. For this practice, select x86.

    Instance Name

    Enter the instance name as planned.

    Description

    Enter a brief description of the instance.

    RCU allocation

    Allocate RCUs to integration capabilities. Only capabilities with RCUs are available.

    • The ROMA compute unit (RCU) can be allocated to different integration capabilities. More RCUs indicate higher capability performance.
    • You can use the RCU values recommended by the system or customize them for different capabilities. The total RCU value cannot be 0.
    • Some integration capabilities depend on each other.
      • Composite Application (flow running) and Service Integration (Data API/Function API) depend on Service Integration (API management).
      • Device Integration depends on Message Integration.
  3. On the Advanced Configuration page displayed, complete the information and click Next.
    Table 3 Advanced settings

    Parameter

    Description

    Network Configuration

    VPC

    Select the VPC and subnet associated with the instance. The VPC and subnet must have been created during resource preparation.

    Accessing Internet

    Whether to enable the function of accessing ROMA Connect from a public network.

    Public Network Bandwidth

    Mandatory only when Accessing Internet is enabled.

    Select the bandwidth of the public network.

    Message Integration Configuration (Displayed only when RCUs are allocated to Message Integration.)

    Engine Version

    Version number of the Kafka server for message integration. Currently, version 2.7 is supported.

    MQS Capacity Threshold Policy

    Select a processing policy that will be used when the number of messages in MQS reaches the capacity threshold (95% of the storage space).

    • Stop creation: New message creation requests are rejected until messages are deleted after the configured aging time and the available storage space is greater than 5%. This policy applies when message consumption is slow or stacked messages need to be repeatedly consumed and cannot be deleted in advance.
    • Automatic deletion: The earliest messages (10% of the total number of messages) are automatically deleted to free up storage space for new requests. This policy has no adverse impact on message creation. It applies when message consumption is fast and there are no stacked messages.

    SASL_SSL

    Whether to enable SASL authentication and SSL encryption for message transmission. Enabling this parameter better secures data transmission.

    Enabling SASL_SSL cannot be undone.

    Intra-VPC Plaintext Access

    Available only when SASL_SSL is enabled.

    Whether plaintext access is used in the VPC.

    If intra-VPC plaintext access is enabled, you do not need to connect to topics in the VPC via SASL. In this case, no certificate is required for connecting to topics.

    Recommended Package

    You can buy a package for pay-per-use deductions.

    Package calculation: Recommends packages based on the estimated runtime of your selected instance specifications.

    Four distinct packages are available for selection. Specify the quantity and duration required for each package. You can purchase multiple packages with different specifications at the same time.
  4. On the Configuration confirmation page, select I agree to the Customer Agreement and Privacy Statement, and click Buy Instance.

    The instance creation takes about 15 to 25 minutes. After the instance is created, the instance status is Available in Resource.

    If the ROMA Connect instance fails to be created, delete the failed instance and create a new one. If the creation still fails, contact technical support.

Parent topic: Instance Management