Vultr VX1™ Cloud Compute delivers industry-leading price-performance with dedicated CPU resources. VX1™ supports booting from high-performance Vultr Block Storage and can also leverage local NVMe for high-speed scratch storage.
Follow this guide to provision a Vultr VX1™ Cloud Compute instance using the Vultr Console or Vultr API.
VX1™ is available in select locations and expanding to more regions. To verify availability, navigate to the Deploy Instance page in the Vultr Console, select the required VX1™ plan, and verify that it is available in your preferred location.
Navigate to Products and click Compute.
Click Deploy.
Choose Dedicated CPU as the instance type.
Select your desired Vultr location to deploy the instance.
Select VX1 from the sidebar plan categories.
Select a plan from the available options:
General Purpose (vx1-g-*): Provide a balanced combination of vCPUs and memory, suitable for most workloads including web servers, application servers, development environments, container workloads, and moderate database deployments.
Memory Optimized (vx1-m-*): Provide a higher memory-to-vCPU ratio, ideal for workloads requiring large in-memory datasets such as caching engines, analytics workloads, JVM applications, high-memory web services, and large databases.
Plans ending with -###s suffix (such as vx1-g-4c-16g-240s) include local NVMe storage.
Click Configure Software.
Select Boot Disk Settings:
Local NVMe: Boot from high-speed local NVMe storage.
Bootable Block Volume: Boot from Vultr Block Storage. Select an existing bootable block volume or click Create Bootable Block Volume to create a new one. When creating a bootable block volume, select the operating system, storage size, and label.
Select a cloud image to install on your instance based on the following options:
Select optional Server Settings to apply on the instance.
Enter a new hostname in the Server Hostname field and a descriptive label in the Server Label field to identify the instance.
Configure Additional Features for the instance.
linuxuser non-root user with sudo privileges as the default user account instead of root.Click Deploy to provision the instance.
0 Comments
Be the first to comment and share your perspective with the community.