• Elastic Cloud Server

ecs
  1. Help Center
  2. Elastic Cloud Server
  3. User Guide
  4. Getting Started
  5. Creating an ECS

Creating an ECS

Scenarios

ECSs are more cost-effective than physical servers. Within minutes, you can obtain ECS resources from the public cloud. ECS resources are flexible and on-demand. This section describes how to create an ECS.

Step 1: Switch to the Create ECS Page

  1. Log in to the management console.
  2. Click in the upper left corner and select the desired region and project.
  3. Under Computing, click Elastic Cloud Server.
  4. Click Create ECS.
    The ECS creation page is displayed.
    NOTE:

    SAP High-Performance Analytic Appliance (HANA) is a high-performance real-time data computing platform based on memory computing technologies. The public cloud provides high-performance IaaS services that comply with SAP HANA requirements. These services include applying for HANA ECSs and public IP addresses as well as installing and configuring SAP HANA. Such services facilitate applications on the public cloud platform of resources required by SAP HANA, improving the efficiency of user operations, reducing operation costs, and enhancing user experience.

    HANA ECSs are dedicated for SAP HANA. If you have deployed SAP HANA on cloud servers, you can create HANA ECSs.

    For more information about HANA ECS application scenarios and creation methods, see SAP HANA User Guide.

Step 2: Perform Basic Configurations

  1. Select a region.

    ECSs in different regions cannot communicate with each other over an intranet. For low network latency and quick resource access, select the nearest region.

  2. Select an AZ.

    An AZ is a physical region where power and networks are physically isolated. AZs in the same region can communicate with each other over an intranet.

    • To enhance application availability, create ECSs in different AZs.
    • To shorten network latency, create ECSs in the same AZ.
  3. Set DeH.

    This configuration is optional. This parameter is available only when you click Create ECS on the Dedicated Host page. It is unavailable when you click Create ECS on the Elastic Cloud Server page.

    DeH refers to physical host resources dedicated for a specified user. You can deploy ECSs on DeHs for better isolation, security, and performance of your ECSs. You can continue using your existing server software licenses of ECSs on DeHs to reduce costs. For more details, see Dedicated Host User Guide.

  4. Set Specifications.

    The public cloud provides various ECS types for different application scenarios. You can view released ECS types and flavors in the list. Alternatively, you can enter a flavor (such as c3) or specify vCPUs and memory size to search for the desired flavor.

    Latest generations show the types and specifications of newly released ECSs, and All generations show the types and specifications of all ECSs provided by the public cloud.

    NOTE:
    • Before selecting an ECS type, learn the introduction and notes on each type of ECSs. For details, see section ECS Types.
    • Local Disk: specifies the local storage of the physical host where the ECS is deployed. Only Hard Disk Driver (HDD) disks are supported. If the ECS of the selected type (such as Disk-intensive) uses local disks, the system automatically attaches the local disks to the ECS and displays the information of the local disks.

      For example, if Local Disk is 3x1,800 GB (HDD), three HDDs are attached to the ECS and the capacity of each HDD is 1800 GB.

  5. Click Image.
    • Public image

      A public image is a standard, widely used image. It contains an OS and preinstalled public applications and is available to all users. You can configure the applications or software in the public image as needed.

      For more information about public images, see Public Images Introduction.

    • Private image

      A private image is an image available only to the user who creates it. It contains an OS, preinstalled public applications, and the user's private applications. Using a private image to create ECSs removes the need to configure multiple ECSs repeatedly.

      You can also select an encrypted image. For details, see Image Management Service User Guide.

      If you have used a CSBS backup to create a private image (full-ECS image), you can use the full-ECS image. However, the EVS disk in the image does not support disk creation using a data disk image, and disk attributes (such as SCSI/VBD and data encryption) cannot be modified. For more details about how to use CSBS backups to create images, see section "Using Backups to Create Images" in Cloud Server Backup Service User Guide and section "Creating a Full-ECS Image Using a CSBS Backup" in Image Management Service User Guide.

    • Shared image

      A shared image is a private image shared by another user.

    • Marketplace image

      The Marketplace is a store where you can purchase third-party images that have the OS, application environment, and software pre-installed. You can use the images to deploy websites and application development environments with a few clicks, and no additional configuration operation is required.

      If you use a Marketplace image, after you click Marketplace image, the system displays Marketplace images for you to select. For example, if the image product is name1 (test_001), name1 is the image name, and test_001 is the product name. You can search for your desired Marketplace image by image name or product name. Alternatively, you can click the image name to view more information about the product. For more information about Marketplace images, see Marketplace User Guide (for Tenants).

  6. (Optional) Set License Type.

    Specifies a license type for using an OS or software. If the image you selected is free of charge, this parameter is unavailable. If the image you selected is billed, this parameter is available.

    • Use license from the system

      Allows you to use the license provided by the public cloud platform. Obtaining the authorization of such a license is billed.

    • Bring your own license (BYOL)

      Allows you to use your existing OS license. In such a case, you do not need to apply for a license again.

    For more details, see section License Type.

  7. Set Disk, which can be a system disk or a data disk.
    • System Disk

      For details about the disk types supported by the ECS, see section Storage. For more information about EVS disks, see Elastic Volume Service User Guide.

      If the image based on which an ECS is created is not encrypted, the system disk of the ECS is not encrypted. If the image based on which an ECS is created is encrypted, the system disk of the ECS is automatically encrypted. For details, see section (Optional) Encryption-related parameters.

      The system disk of a P1 or P2 ECS must be greater than or equal to 15 GB. It is recommended that the system disk be greater than 40 GB.

    • Data Disk

      You can create multiple data disks for an ECS and configure sharing and encryption for each data disk. When creating an ECS, you can add up to 24 disks with customized sizes to it. After the ECS is created, you can add up to 60 disks to such a newly created ECS.

      • SCSI: indicates that the device type of the data disk is SCSI. For more information about SCSI disks and the ECSs that can be attached with SCSI disks, see section Storage.
      • Share: indicates that the EVS disk is shared. Such an EVS disk can be attached to multiple ECSs.
      • Encryption: indicates that the data disk is encrypted. For details, see section (Optional) Encryption-related parameters.
      • Create Disk from Data Disk Image: If you have created a data image on the Image Management Service page, when using a Windows or Linux image to create an ECS, you can use a data disk image to create a disk for the ECS.

        Click Create Disk from Data Disk Image. In the dialog box that is displayed, select your data image.

        NOTE:
        • One data disk image can be used only for one data disk.
        • When you use a data disk image to create a disk, SCSI, Encryption, and Share are unavailable.
        • For instructions about how to create a data image, see Image Management Service User Guide.
    • (Optional) Encryption-related parameters

      To enable encryption, click Create Xrole to grant KMS access rights to EVS. If you have rights granting permission, grant the KMS access rights to EVS. If you do not have the permission, contact the user having the security administrator rights to grant the KMS access rights. For details, see section Who Can Use the Encryption Feature?

      • Encrypted: indicates that the EVS disk has been encrypted.
      • Create Xrole: grants KMS access rights to EVS to obtain KMS keys. After the rights are granted, follow-up operations do not require granting rights again.
      • KMS Key Name: specifies the name of the key used by the encrypted EVS disk. By default, the name is evs/default.
      • Xrole Name: EVSAccessKMS: specifies that rights have been granted to EVS to obtain KMS keys for encrypting or decrypting EVS disks.
      • KMS Key ID: specifies the ID of the key used by the encrypted data disk.
  8. Click Next: Network Configuration.

Step 3: Perform Network Configurations

  1. Set Network by selecting an available VPC and subnet from the drop-down list and specifying a private IP address assignment mode.

    VPC provides a network, including subnet and security group, for an ECS.

    You can select an existing VPC or create a desired one. For more information about VPC, see Virtual Private Cloud User Guide.

    NOTE:
    • Ensure that DHCP is enabled in the VPC to which the ECS belongs.
    • When you use VPC for the first time, the system automatically creates a VPC for you, including the security group and NIC.
  2. (Optional) Add an extension NIC. You can add multiple expansion NICs to an ECS and specify IP addresses for them (including primary NICs).
    NOTE:

    When you specify an IP address for a NIC, if multiple ECSs are created in a batch:

    • This IP address serves as the start IP address.
    • Ensure that the IP addresses required by the NICs are within the subnet, consecutive, and available.
    • This subnet cannot duplicate a subnet with a specified start IP address.
    • MTU Settings: optional

      If your ECS is of M2, large-memory, H1, or D1 type, you can click MTU Settings to configure the maximum transmission unit (MTU) for a to-be-added extension NIC for improving network performance. An MTU can only be a number, ranging from 1280 to 8888.

  3. Set Security Group by selecting an available security group from the drop-down list or creating a new one.

    A security group controls ECS access within or between security groups by defining access rules. This enhances ECS security.

    When creating an ECS, you can select multiple (recommended not more than five) security groups. In such a case, the access rules of all the selected security groups apply on the ECS.

    NOTE:

    Before initializing an ECS, ensure that the security group rule in the outbound direction meets the following requirements:

    • Protocol: TCP
    • Port Range: 80
    • Remote End: 169.254.0.0/16

    If you use the default security group rule in the outbound direction, the preceding requirements are met, and the ECS can be initialized. Default security group rules in the outbound direction are as follows:

    • Protocol: ANY
    • Port Range: ANY
    • Remote End: 0.0.0.0/16
  4. Set EIP.

    An EIP is a static public IP address bound to an ECS in a VPC. Using the EIP, the ECS provides services externally.

    The following options are provided:

    • Do not use

      Without an EIP, the ECS cannot access the Internet and is used only in the private network or cluster.

    • Automatically assign

      The system automatically assigns an EIP for the ECS. The EIP provides dedicated bandwidth that is configurable.

    • Specify

      An existing EIP is assigned for the ECS. When using an existing EIP, you cannot create ECSs in batches.

  5. Click Next: Advanced Configuration.

Step 4: Perform Advanced Configurations

  1. Set ECS Name.

    The name can be customized but must comply with the following naming rules: 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.

  2. (Optional) Specify the description of the ECS.
  3. Set Login Mode.
    The login mode is Key pair, which allows you to use a key pair for login authentication. You can select an existing key pair, or click Create Key Pair and create a desired one.
    NOTE:

    If you use an existing key pair, make sure that you have saved the key file locally. Otherwise, logging in to the ECS will fail.

  4. Configure Auto Recovery.

    Once a physical host accommodating ECSs breaks down, the ECSs with automatic recovery enabled automatically migrate to a functional host. This minimizes user service interruption. These ECSs will restart in this process. If automatic recovery is not enabled, the affected users must wait for the system administrator to recover ECSs after the physical host becomes faulty. For more information about automatic recovery, see section Automatically Recovering ECSs.

    NOTE:

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

    • Local disk
    • Passthrough FPGA
    • Passthrough InfiniBand NIC
  5. To use functions listed in Advanced Settings, select Configure. Otherwise, do not select it.
    • File Injection

      Enables the ECS to automatically inject a script file or other files into a specified directory on an ECS when you create the ECS. This configuration is optional.

      For example, if you activate user root permission using script file injection, you can log in to the ECS as user root.

      For details about file injection, see section Injecting Files into ECSs.

    • User Data Injection

      Enables the ECS to automatically inject user data when the ECS starts for the first time. This configuration is optional.

      For example, if you activate user root permission using script file injection, you can log in to the ECS as user root.

      For detailed operations, see section Injecting User Data into ECSs.

    • ECS Group

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

    • Tag

      Tags an ECS, facilitating ECS identification and management. This configuration is optional. You can add up to 10 tags to an ECS.

      NOTE:

      Tags added during ECS creation will also be added to the created EIP and EVS disks (including the system disk and data disks) of the ECS. If the ECS uses an existing EIP, the tags will not be added to the EIP.

      After creating the ECS, you can view the tags on the pages providing details about the ECS, EIP, and EVS disks.

      For detailed operations, see section Tags.

    • 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 rights 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.

  6. Configure the number of ECSs to be created.

    After the configuration, click Price Calculator to view the ECS configuration fee.

  7. Click Next: Confirmation.

Step 5: Confirm Order

  1. On the Confirmation page, view the ECS configuration details.

    To learn more about the price, click Pricing details.

  2. Confirm the specifications and click Create Now.

Follow-up Procedure

  • After an ECS with an EIP bound is created, the system automatically generates a reverse domain name in the format of "ecs-xx-xx-xx-xx.compute.xxx.com" for each EIP address by default. In the format, "xx-xx-xx-xx" indicates the EIP, and "xxx" indicates the domain name of the cloud service provider. You can use the reverse domain name to access the ECS.
    Use one of the following commands to obtain the default reverse domain name of an EIP:
    • ping -a EIP
    • nslookup [-qt=ptr] EIP
    • dig -x EIP
  • After an ECS with automatic recovery enabled is created, you can check whether this function has been enabled by viewing Failures. For details, see section Viewing Failures.