Esta página ainda não está disponível no idioma selecionado. Estamos trabalhando para adicionar mais opções de idiomas. Agradecemos sua compreensão.

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
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
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Scalable File Service Turbo
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
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
On this page

Step 3: Configure Advanced Settings

Updated on 2024-11-27 GMT+08:00

Advanced Settings

  1. Set ECS Name.

    The name can be customized but can contain only letters, digits, underscores (_), hyphens (-), and periods (.).

    If you want to create multiple ECSs at a time, the system automatically sequences these ECSs.

    If multiple ECSs are created at a time, the system automatically adds a hyphen followed by a four-digit incremental number to the end of each ECS name. For example, if you enter ecs, the ECSs will be named ecs-0001, ecs-0002, ... If you create multiple ECSs again, the numbering of the new ECS names continues from the highest existing value. For example, if the ECS with the highest number in name is ecs-0010. If you enter ecs, the names of the new ECSs will be ecs-0011, ecs-0012, ... When the value reaches 9999, it will start over again from 0001.

    Allow duplicate name: allows ECS names to be duplicate. If you select Allow duplicate name and create multiple ECSs in a batch, the created ECSs will have the same name.

    The ECS Name set in this step will be the initial host name in the ECS OS.

    NOTE:

    The naming rules of hostnames comply with RFC 952 and RFC 1123.

    When you set the ECS name and hostname, you are advised to use letters (a-z), digits (0-9), and hyphens (-) to prevent unknown issues. In the ECS:

    • Periods (.), hyphens (-), Chinese characters, or underscores (_) at the beginning of the name will be ignored.
    • If periods (.) and Chinese characters are not at the beginning, they and the content following them will be ignored.
  2. Set Login Mode.
    • Password

      A username and its initial password are used for ECS login authentication.

      The initial password of user root is used for authenticating Linux ECSs, while that of user Administrator is used for authenticating Windows ECSs.

      The passwords must meet the requirements described in Table 1.
      Table 1 Password complexity requirements

      Parameter

      Requirement

      Password

      • Consists of 8 to 26 characters. For specific requirements on the password length, see the information displayed on the console.
      • Contains at least three of the following character types:
        • Uppercase letters
        • Lowercase letters
        • Digits
        • Special characters for Windows: $!@%-_=+[]:./,?
        • Special characters for Linux: !@%-_=+[]:./^,{}?
      • Cannot contain the username or the username spelled backwards.
      • Cannot contain more than two consecutive characters in the same sequence as they appear in the username. (This requirement applies only to Windows ECSs.)
      NOTE:

      The system does not periodically change the ECS password. It is recommended that you change your password regularly for security.

    • Image password

      If you use a Linux private image to create an ECS, you can use the image password for login authentication. Make sure that a password has been set for the selected private image.

    • Set password later

      The password for logging in to the ECS is not configured during the ECS creation. After the ECS is created, select Reset Password in the Operation column, set a password for the ECS as prompted, and log in to the ECS.

  3. Set Cloud Backup and Recovery.

    Cloud Backup and Recovery (CBR) provides backup protection for EVS disks and ECSs, and uses backups to restore the EVS disks and ECSs. After you set Cloud Backup and Recovery, the system binds the target ECS to the cloud backup vault and associates the ECS with the selected backup policy to periodically back up the ECS.

    The following options are provided:

    • Create new
      1. Set the name of the cloud backup vault, which consists of 1 to 64 characters, containing only letters, digits, underscores (_), and hyphens (-). For example, vault-f61e. The default naming rule is vault_xxxx.
      2. Enter the vault capacity, which is required for backing up the ECS. The vault capacity cannot be smaller than that of the ECS to be backed up. Its value ranges from the total capacity of the ECS to 10,485,760 in the unit of GB.
      3. Select a backup policy from the drop-down list, or log in to the CBR console and configure a desired one.
    • Specify
      1. Select an existing cloud backup vault from the drop-down list.
      2. Select a backup policy from the drop-down list, or log in to the CBR console and configure a desired one.
    • Do not use

      Skip this configuration if CBR is not required. If you need to enable CBR after creating an ECS, log in to the CBR console, locate the target vault, and bind the ECS to the vault.

  4. Set ECS Group (Optional).

    An ECS group applies the anti-affinity policy to the ECSs in it so that the ECSs are automatically allocated to different hosts. This configuration is optional. For instructions about how to create an ECS group, see Managing ECS Groups.

    NOTE:

    An existing ECS attached with a local disk cannot be added to an ECS group. To use ECS group functions, select an ECS group when creating an ECS.

  5. Configure automatic recovery.

    If a physical server accommodating ECSs breaks down, the ECSs with automatic recovery enabled will automatically be migrated to a functional server to minimize the impact on your services. During this process, the ECSs will restart. If automatic recovery is not enabled, the affected users must wait for the system administrator to recover ECSs once the physical server becomes faulty. For more information about automatic recovery, see Automatically Recovering ECSs.

    NOTE:

    An ECS with any of the following resources cannot be automatically recovered:

    • Local disk
    • Passthrough FPGA
    • Passthrough InfiniBand NIC
  6. To use functions listed in Advanced Options, select Configure now. Otherwise, do not select it.
    • User Data

      You can specify the user data. The user data will be automatically passed to the ECS when the ECS starts for the first time. This configuration is optional.

      For example, if you activate user root permission by passing a script file to an ECS, you can log in to the ECS as user root.

      For detailed operations, see Passing User Data.

    • Agency

      This configuration is optional. When your ECS resources need to be shared with other accounts, or your ECS is delegated to professional personnel or team for management, the tenant administrator creates an agency in IAM and grants the ECS management permissions to the personnel or team. The delegated account can log in to the cloud system and switch to your account to manage resources. You do not need to share security credentials (such as passwords) with other accounts, ensuring the security of your account.

      If you have created an agency in IAM, you can select the agency from the drop-down list and obtain specified operation permissions. For instructions about how to create an agency, see Identity and Access Management User Guide.

  7. Click Next: Confirm.

Usamos cookies para aprimorar nosso site e sua experiência. Ao continuar a navegar em nosso site, você aceita nossa política de cookies. Saiba mais

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback