Create Windows Instance

Products

Virtual Machines

2022-02-25 14:40:34

Create Windows instance

  1. Visit Instance console, or visit JD Cloud & AI console and click on the left Navigation bar [Elastic Compute] - [Virtual Machine] - [Instance] to enter the Instance List page.

  2. Select the region where the instance belongs and click the "Create" button to enter the Virtual Machine purchase page. We suggest you select region where the instance is located in according to your business situation, for details about JD Cloud region, please refer to Region and Availability Zone.

  3. Select Billing model: Via annual/monthly subscription and by configuration. Annual/monthly subscribers pay for services by month, and users choosing the billing by configuration pay by hour for actually consumed duration (accurate to the second). Regarding the difference between the two billing methods, please refer to the billing rules.

  4. Select region and availability zone: In this step, you can still select the regions (cn-north-1, cn-south-1, cn-east-1, and cn-east-2) and availability zones corresponding to the instance. Please note that "resource intranets cannot be intercommunicated across regions, or changed after creation". If the quota of the region selected is full, you can increase the quota through [Submit a ticket] 3 .

  5. Select the creation method: There are three creation methods: Create customized instance, Create with instance template, Create instance in Availability Group. For the latter two, you need to create instance template and availability group in advance. Unless otherwise specified, keep the default option "Create customized instance".

  6. Select an image: Images are divided into the cloud disk system disk ones and local disk system disk ones. The former ones only support creating instances where the system disk is a cloud disk, and the latter ones only support creating instances where the system disk is a local disk. In addition, either category provides the following image types: Official image, private image, shared image, and marketplace image. For details, please refer to Image overview.

    For users who use JD Cloud & AI for the first time, they can choose the "Public Image" provided by JD Cloud & AI. You can select the corresponding system and the appropriate version according to your needs.

    If you have created your own instance and configured the corresponding environment, you can make a private image with this instance, create hosts with the same system and environment configuration in batches based on this image, and share this private image with other JD Cloud & AI users.

  7. Select an instance type: The instance type is user-defined, from the smallest 1-core CPU and 1G memory (such as g.s1.micro) to 72C576GB (such as m.n2.18xlarge). Users can select the instance type and corresponding configuration for different business scenarios. For details, please refer to Instance type.

  8. Configure the instance storage:

  • Virtual machine system disk: Support local disks and cloud disk, of which the local disk is 40GB for free and its capacity cannot be changed. The cloud disk system disk supports 40GB~500GB.

  • Virtual Machines Data Disk: If the system disk is a local disk, 8 data disks can be attached. If the system disk is a cloud disk, 7 cloud disks can be attached as data disks. General Type SSD Cloud Disk, Performance Type SSD Cloud Disk, Capacity Type HDD Cloud Disk are selective. After the cloud disk is attached to a VM, it needs to access the Virtual Machines operating system to attach cloud disk.

    You can create an empty disk of a specified type and capacity with the instance, or create a data disk based on an existing cloud disk snapshot. Please refer to Device name assignment rules for data disk device name assignment rules.

It supports the attachment of encrypted cloud disks to Virtual Machines (which is not supported by the first generation of instance specification). The cloud disk encryption attribute may be specified at the time of creating a null disk. If the disk is created from snapshot, the cloud disk encryption attribute is inherited from the snapshot side. After the creation of a cloud disk, its encryption attribute cannot be modified. For details, refer to [Encryption of Cloud Disk](//docs.jdcloud.com/en/virtual-machines/encryption-of-cloud-disk). 

It supports Pay By Configuration, and the attribute of deletion on instance termination may be set for the non-multi-point attached cloud disk. If the attribute is checked, the disk will be deleted when the instance is deleted.  

You can specify the cloud disk snapshot policies at a single disk granularity. You can specify different or identical snapshot policies for different cloud disks according to your backup needs, and JD Cloud & AI will automatically back up your cloud disk on a regular basis according to the policy you specify. For details, please refer to [Customize snapshot policies](https://docs.jdcloud.com/cn/cloud-disk-service/snapshotpolicy).

The cost of cloud disk is independent from instance. See [Cloud Disk Price](http://docs.jdcloud.com/cn/cloud-disk-service/billing-rules) for specific price information.

  1. Configure the instance network:

    • Select Virtual Private Cloud and Subnet: You are required to create a VPC and subnet first. After selecting Subnet, the system can judge the number of VMs that can be created under the Subnet; if there is no Subnet currently, you can create a new Subnet through fast entrance and select in "Virtual Machine Network". Please refer to Virtual Private Cloud and Subnet for details.
    • Select the allocation method for intranet IP: If there is no special requirement for the intranet IP address, you may specify none and the system will automatically assign one within the available network segment of the subnet. If you want to specify one, please enter it in the prompt range and the system will check if it is available. It should be noted that if you choose to customize the intranet IP address, you cannot create instances in batches.
    • Select the security group: An instance must be bound to a security group when it is created. If no custom security group has been created in the current region, you can select one of the three default security groups created by the system to associate with the instance (After each VPC is successfully created, three default security groups will be created automatically.), or you can go to the security group pageCreate a security group through the quick entry. Since the firewall in the official image system is disabled by default, it is recommended to associate with a security group that only opens port 22 (Linux) or port 3389 (Windows). After the instance is created, create a new security group and associate with it according to the access requirements.
  2. Configure the public network bandwidth:

  • Bandwidth billing method: JD Cloud & AI provides EIPs with two bandwidth billing methods: by fixed bandwidth and by traffic. For the billing by fixed bandwidth, the user pays according to the bandwidth set upon the purchase, with nothing to do with the bandwidth actually used for access to the public network. For the billing by traffic, the user pays according to the traffic actually consumed for access to the public network.
  • Line: Elastic public network IP lines are divided into: BGP and non-BGP. If you need a faster and more efficient network access, BGP is preferred.
  • Bandwidth range: 1Mbps~200Mbps. You can temporarily not purchase a public IP in the process of creating a host, and then associate a public IP after the host is created. The cost of elastic IP bandwidth is independent from those of the instance. See Elastic IP Price for specific price information .
  1. Set the instance name, description, and label bound to the instance: You need to set the hostname to be created. The name cannot be left empty. Only Chinese characters, numbers, upper and lower case letters, English underscore "", line-through "-" and dot "." are supported, 128 as maximum. If the purchase is created in batches, the names will be displayed in order of “xxx1” and “xxx2”. Adding description to the instance is also supported. The description can be left empty, but if added, it may contain 256 characters as maximum. Also, you can optionally add tags to the host created. Each tag consists of 1 "key" and 1 "value". The tag's key value cannot start with "jrn:" or "jdc-", which only supports Chinese, uppercase and lowercase English letters, numbers, and such symbols as ".,:/=+-@". Up to 10 tags can be bound to the host currently created. For purchase created in batches, the tag will be bound to each host batch created. Please refer to Edit tag for the tag editing operations.

    • Default hostname configuration rules: It is now not supported to customize the hostname when the host is created. The system will set the hostname by taking the hostname under the premise that the instance name conforms to the rules of RFC-952 and RFC-1123. If the instance name does not conform to the specification, the system will convert some characters. If it becomes conforming after conversion, it will be truncated (not more than 63 characters for Linux, and not more than 15 characters for Windows) before configuring the hostname. Otherwise it will be configured with the default hostname , in the default format of "server-<instance-id>".
  2. Set password: You can select "Set Now" or "Set Later" (the system will send the default password via SMS and email). The password is used not only for SSH login to the instance, but also for the console login to the instance via VNC.

  3. Confirm the quantity of virtual machines and the duration Purchase quantity is limited by your container, cloud disk, EIP quota in the region and the amount of IP remaining on the selected subnet. If the quota is not enough, you can increase the quota by open ticket.
    If you purchase a monthly package instance, the purchase duration shall be set, which is 1 month at shortest and 2 years at longest. you can enjoy one-year service if you pay ten month. Please [open ticket] if you need longer service duration3.
    When purchasing an instance via annual/monthly subscription, you can directly configure automatic renewal for it and its associated resources (CDS and EIP). The automatic renewal duration is seen by default the same as the duration purchased. For later adjustment, you can adjust in the renewal management console at any time.

Related References

Regions and availability zones

Billing Rules

Image overview

Instance type

Device name assignment rules

Encryption of cloud disk

CDS price

Virtual private cloud

Subnet

Create security group

EIP price

Edit tag

Feedback

开始与售前顾问沟通

可直接拨打电话 400-098-8505转1

我们的产品专家为您找到最合适的产品/解决⽅案

在线咨询 5*8⼩时

1v1线上咨询获取售前专业咨询

点击咨询
企微服务助手

专业产品顾问,随时随地沟通