Help Center/ Cloud Service Engine/ User Guide/ Registry/Configuration Center/ Creating a Registry/Configuration Center
Updated on 2024-10-15 GMT+08:00
View PDF
Share

Creating a Registry/Configuration Center

This section describes how to create an engine whose registry/configuration center is Nacos.

Nacos engines are supported only in CN East 2, CN-Hong Kong, AP-Singapore, ME-Riyadh, and LA-Mexico City2.

Prerequisites

  • A Nacos engine runs on a VPC. Before creating a Nacos engine, ensure that VPCs and subnets are available. For details about how to create a VPC and subnet, see Creating a VPC.
  • The user has the CSE FullAccess and DNS Full Access permissions.

Creating a Registry/Configuration Center

  1. Go to Buy Registry/Configuration Center Instance.
  2. Set parameters according to the following table. Parameters marked with an asterisk (*) are mandatory.

    Parameter

    Description

    *Billing Mode

    Billing mode. Currently, Pay-per-use is supported.

    *Enterprise Project

    Project where the Nacos engine locates. You can search for and select an enterprise project in the drop-down list.

    Enterprise projects let you manage cloud resources and users by project.

    An enterprise project can be used after it is created and enabled. For details, see Enabling the Enterprise Project Function. By default, default is selected.

    *Name

    Name of a Nacos engine. The name contains 3 to 64 characters, including letters, digits, and hyphens (-), and starts with a letter but cannot end with a hyphen.

    NOTICE:

    Nacos engine name cannot be default.

    *Registry/Configuration Center Instance

    Select Nacos.

    NOTE:

    Cluster nodes in the registry/configuration center are evenly distributed to different AZs. A failure of a single node does not affect external services. The registry/configuration center does not support AZ-level DR but provides host-level DR.

    *Instances

    Select the required capacity specifications.

    NOTE:

    To create a Nacos engine with more than 2,000 microservice instances, submit a service ticket.

    Version

    Only the latest version can be created.

    *Network

    Select a VPC and subnet to provision logically isolated, configurable, and manageable virtual networks for your engine.

    • To use a created VPC, search for and select a VPC created under the current account from the drop-down list.
    • To use a new VPC, click console to go to the Virtual Private Cloud page and create one. For details, see Creating a VPC.
    NOTE:
    • You cannot use a shared VPC to create a Nacos engine. Otherwise, the engine fails to be created.
    • The VPC cannot be changed once the Nacos engine is created.

    Tag

    Tags are used to identify cloud resources. When you have multiple cloud resources of the same type, you can use tags to classify them based on usage, owner, or environment.

    Click Add Tag. In the Add Tag dialog box, enter a tag key and value. For details about tag naming rules, see Managing Tags. In the Add Tag dialog box, you can click Add Tag to add multiple tags at a time, or click next to a tag to delete the tag.

  3. Click Buy. The page for confirming the engine information is displayed.
  4. Click Submit. When the status becomes Available, the engine is created.

    • After the Nacos engine is created, its status is Available. For details about how to view the Nacos engine status, see Viewing Nacos Engine Information.
    • You may fail in buying an engine for insufficient underlying resources. To prevent this, delete engines in time so that you will not be charged if your engines restore upon sufficient underlying resources.