Scenarios
This document uses the custom configuration method as an example to guide you on how to create a CVM instance.
Prerequisites
Before creating a CVM instance, you need to complete the following tasks:
- Create a cloud platform account.
- To create a CVM instance with a network type of VPC, you need to create a VPC in the target region and a subnet in the target AZ within the VPC.
- If you do not want to use the system's automatically created default security group, you need to create a security group in the target region and add security group rules that meet your business needs.
- If you need to bind an SSH key pair when creating a Linux instance, you need to create an SSH key in the target project.
- If you need to create a CVM instance with a custom image, you need to create a custom image or import an image.
Operation Steps
- Log in to the cloud platform, select Cloud Virtual Machine > CVM List, and click New to enter the Cloud Virtual Machine purchase page.
- Custom configuration: suitable for use in specific scenarios, making it convenient for users to purchase CVM instances that meet their specific needs.
- Follow the on-page prompts to configure the following information:
| Category | Required/Optional | Configuration Instructions |
|---|---|---|
| Region/AZ | Required | - Region: It is recommended to choose the region closest to your customers to reduce latency and improve access speed. - AZ: Select according to your actual needs. If you need to purchase multiple CVM instances, it is recommended that you choose different AZs to achieve disaster recovery. For more information about selectable regions and AZs, see Regions and AZs. |
| Network | Required | It represents a logically isolated network space built on the cloud platform. A VPC consists of at least one subnet. The system will provide a default VPC and subnet for each region. If the existing VPC/subnet does not meet your requirements, you can create one in the VPC console. Note: - Resources within the same VPC communicate with each other by default. - A CVM instance must be created within a subnet that has the same AZ attribute as the CVM. - When you manually allocate private IP addresses, the number of editable IP addresses in the IP address input box is related to the quantities of CIDR in the subnet. |
| Instance | Required | Based on different underlying hardware, the cloud platform currently offers various instance types. For optimal performance, it is recommended to use the latest generation of instance types. For more details on instances, see Instance Specification. |
| Image | Required | The cloud platform provides public images, custom images, and shared images. You can choose based on Image Types. |
| System disk | Required | Used to install the operating system. The default size is 50 GB. Different regions will affect the available types of cloud disks. Please select based on the actual prompts on the page. For more information about cloud disks, please see Cloud Disk Types. |
| Data disk | Optional | Used to expand the storage capacity of CVM instances and provide efficient and reliable storage devices. By default, no cloud data disk is added. For more information about cloud disks, please see Cloud Disk Types. |
| Scheduled snapshot | Optional | The snapshot service provides regular backup of cloud disk data to deal with risks such as virus infection and accidental data deletion. |
| Public IP address | Required | If you need to assign a public network IP address to an instance, select Allocate Now. The IP address allocated in this way cannot be unbound from the instance, but the public IP address can be converted into an elastic public IP address and then unbound. For more information about elastic IP addresses, see Elastic Public IP. |
- Click Next: Set Security Group and Host to proceed to the configuration page.
- Follow the on-page prompts to configure the following information:
| Category | Required/Optional | Configuration Instructions |
|---|---|---|
| Security group | Required | - If you do not have an available security group, you can select Create Security Group. - If you have an available security group, you can select Existing Security Group. For more information about security groups, please see Security Group. |
| Instance name | Optional | User-customized, indicating the name of the CVM instance to be created. - If you do not define an instance name, the instance name after creation will be "Unnamed". - If an instance name is defined, it must be within 60 characters. Note: This name is only displayed in the console and is not the hostname of the CVM instance. |
| Login method | Required | Set the method for users to log in to the CVM instance according to actual needs. - Set password: Customize the password for logging in to an instance. - Associate Key Immediately (Linux Instances Only): Associate an SSH key for a more secure login to the CVM instance. If you do not have a key or the existing key is not suitable, you can click Create Now to create one. For more information on SSH keys, see SSH Key. - Automatically generate password: The automatically generated password will be sent through the message center. |
| Security reinforcement | Optional | If this option is selected, the HSS security product will be installed to help users build a server security protection system and prevent data leakage. |
| Cloud Monitor | Optional | Cloud service monitoring is enabled free of charge by default. Install components to obtain host monitoring metrics and display them in the form of monitoring icons. It also supports customizing alarm thresholds. It also provides three-dimensional CVM instance data monitoring, intelligent data analysis, real-time fault alarms, and personalized data report configuration, allowing users to accurately control the health of their business and CVM instances. |
| Automation Tools (TAT) | Optional | After purchasing TAP-related features, you can use the capabilities of the Cloud Platform Automation Tool. This is a native Ops deployment tool for CVM, which allows for automated batch execution of Shell commands without remote connection to instances. It can complete tasks such as running automation Ops scripts, installing/uninstalling software, updating applications, and installing patches. |
| Advanced settings | Optional | Instances can be further configured according to actual needs. - Host name: Users can customize the computer name inside the CVM operating system. After the CVM instance is successfully put into operation, you can check it by logging in to it. - Placement group: Instances can be added to a placement group as needed to improve business availability. For detailed setup, see Placement Groups. Note: If the type of the instance you created is set by the administrator as not supporting placement groups, this feature will be unavailable. If modification is needed, please contact the administrator. - Custom data: Specify custom data to configure an instance, that is, run the configured script when the instance starts. If more than one CVM instance is purchased at a time, custom data runs on all of them. The Linux operating system supports the Shell format, and the Windows operating system supports the PowerShell format, up to 16 KB of raw data. For more details, see Setting Custom Data (Linux Cloud Virtual Machine). Note: Custom data configuration is only supported by certain public images with cloud-init services. For details, see Cloud-Init and Cloudbase-Init. |
- Click Next: Confirm Configuration to proceed to the Confirm Configuration page.
- Review the information about the CVM you are purchasing and understand the cost details of each configuration.
- Click Open to complete the creation. After the creation is completed, you can go to the CVM console to check your CVM instance.
- The instance name, public IP address, private IP address, login name, initial login password, and other information of the CVM instance will be sent to your account via Message center. You can use this information to log in and manage the instance. Please change your CVM login password as soon as possible to ensure host security.