Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
Help Center/ ServiceStage/ User Guide/ Microservice Engine/ Creating a Microservice Engine

Creating a Microservice Engine

Updated on 2024-10-31 GMT+08:00

This section describes how to create a microservice engine.

Prerequisites

A microservice engine runs on a VPC. Before creating a microservice engine, ensure that a VPC and subnet are available.

You have created a VPC. For details, see Creating a VPC.

If the engine is created using an account with the minimum permission for creating engines, for example, cse:engine:create in the fine-grained permission dependencies of microservice engines, the default VPC security group cse-engine-default-sg needs to be preset by the primary account and the rules listed in Table 1 need to be added.

For details, see Adding a Security Group Rule.
Table 1 cse-engine-default-sg rules

Direction

Priority

Policy

Protocol and Port

Type

Source Address

Inbound

1

Allow

ICMP: all

IPv6

::/0

1

Allow

TCP: 30100–30130

IPv6

::/0

1

Allow

All

IPv6

cse-engine-default-sg

1

Allow

TCP: 30100–30130

IPv4

0.0.0.0/0

1

Allow

ICMP: all

IPv4

0.0.0.0/0

Outbound

100

Allow

All

IPv4

0.0.0.0/0

100

Allow

All

IPv6

::/0

Creating a Microservice Engine

  1. Go to the Buy Exclusive Microservice Engine page.

    NOTE:
    • By default, a maximum of five exclusive microservice engines can be created for each project. To create more exclusive microservice engines, submit a service ticket to increase the quota. For details, see Creating a Service Ticket.
    • For details about projects, see Projects.

  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

    Select the project where the microservice 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 Enabling the Enterprise Project Function. By default, default is selected.

    NOTE:

    When a microservice engine is in use, do not disable the enterprise project. Otherwise, the engine will not be displayed in the engine list, affecting normal use.

    *Specification

    Select the microservice instance quota.

    NOTICE:

    The specification cannot be changed once the microservice engine is created.

    *Engine Type

    Microservice engine type.

    If the engine type is cluster, the engine is deployed in cluster mode and supports host-level DR.

    *Name

    Name of a microservice engine. The name contains 3 to 24 characters, including letters, digits, and hyphens (-), and starts with a letter but cannot end with a hyphen. This name cannot be changed after the engine is created.

    NOTICE:

    Microservice engine name cannot be default.

    *AZ

    Availability zone.

    Select one or three AZs for the engine based on the number of AZs in the environment.
    • Select one AZ to provide host-level DR.
    • Select three AZs to provide AZ-level DR.
    NOTE:
    • The AZ of a created microservice engine cannot be changed.
    • The AZs in one region can communicate with each other over an intranet.
    • Multiple AZs enhance DR capabilities.

    *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 Create VPC in the drop-down list. For details, see Creating a VPC.
    NOTE:

    The VPC cannot be changed once the engine is created.

    Description

    Click and enter the engine description.

    Authentication Mode

    The exclusive microservice engine with security authentication enabled provides the system management function using the role-based access control (RBAC) through the microservice engine console.

    • Select Enable security authentication:
      1. Determine whether to enable Authenticate Programming Interface.

        After it is enabled, you need to add the corresponding account and password to the microservice configuration file. Otherwise, the service cannot be registered with the engine.

        After it is disabled, you can register the service with the engine without configuring the account and password in the microservice configuration file, which improves the efficiency. You are advised to disable this function when accessing the service in a VPC.

      2. Enter and confirm the password of user root.

        Keep the password secure.

    • Select Disable security authentication:

      Disable security authentication. You can enable it after the instance is created.

  3. Click Buy. The page for confirming the engine information is displayed.
  4. Click Submit and wait until the engine is created.

    NOTE:
    • It takes about 31 minutes to create a microservice engine.
    • After the microservice engine is created, its status is Available. For details about how to view the microservice engine status, see Viewing Microservice Engine Information.
    • If the microservice engine fails to be created, view the failure cause on the Operation page and rectify the fault. Then, you can perform the following operations:
      • In the Microservice Engine Information area, click Retry to create an engine again.
      • If the retry fails, delete the microservice engine that fails to be created. For details, see Deleting an Exclusive Microservice Engine.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback