Creating a Nacos Engine

Restrictions

• Cluster nodes in the registry/configuration center are evenly distributed to different AZs. A failure of a single node does not affect external services.
• 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.
• 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.
• By default, a maximum of five ServiceComb engines can be created for each project. ServiceComb engines share quotas (five engines) with Nacos engines.

Prerequisites

• The login account has the permission to create a microservice engine. For details, see Creating a User and Granting CSE Permissions.
• A Nacos engine runs on a VPC. Before creating a Nacos engine, ensure that VPCs and subnets are available. For details, see "Creating a VPC with a Subnet" in Virtual Private Cloud User Guide.
• The user has the CSE FullAccess and DNS Full Access permissions.

Creating a Registry/Configuration Center

1. Log in to CSE.
2. In the left navigation pane, choose Registry/Configuration Center and click Buy Registry/Configuration Center Instance.
3. 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	Select the project where the Nacos engine is located. You can search for and select the required enterprise project from 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 . By default, default is selected. After a registry/configuration center Nacos engine is created, you can remove Nacos engine resources out of the current enterprise project and into a new enterprise project. For details, see "Removing Resources from an Enterprise Project" in Enterprise Management User Guide and "Adding Resources to an Enterprise Project" in Enterprise Management User Guide.
   *Name	Enter a Nacos engine name. The name contains 3 to 24 characters, including letters, digits, and hyphens (-), and starts with a letter but cannot end with a hyphen (-). The name cannot be default.
   *Registry/Configuration Center Instance	Select Nacos.
   *Instances	Select the required capacity specifications.
   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, create one on the VPC console. For details, see "Creating a VPC with a Subnet" in Virtual Private Cloud User Guide.
   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.

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