1. Open Instances tab and click Create Instance.
2. Select the region where you want to deploy the instance.
Regions can be of two types: Core and Edge. A region determines the equipment specifications.
Core | Edge* | |
---|---|---|
Equipment generation | The latest | Different |
Designed for high scalability on the fly | Yes | Not |
Available resources | 1000 cores and 30 TB of RAM | Up to 300 cores and 1 TB of RAM |
Ports for user traffic and storage | Separate | Shared |
Price | Higher | Lower |
* We can always transform an edge region to core upon your request.
3. Configure the image.
Select the type of hardware architecture on which your instance will be running:
Your choice of hardware architecture will affect the available OS options and instance flavors. Choose an OS distribution, a volume, a snapshot, a custom image, or a template from the marketplace.
4. Configure the instance type.
Select the appropriate CPU generation:
Choose one of the available flavors.
5. Configure Volumes.
Enter a volume name, choose its type and set its size in GiB
Availability: Amsterdam, Frankfurt, London, Luxembourg, Luxembourg-2, Manassas, Paris-2, Singapore
Availability: all regions
Availability: Luxembourg
Availability: Luxembourg
Availability: Amsterdam-2, Frankfurt, Hong Kong, Luxembourg-2, Manassas, Tokyo
(optional) Add an Attachment Tag.
6. Add one or multiple interfaces in Network settings.
If you select a public interface, you can turn on the Use Reserved IP toggle and assign a reserved IP address to your instance.
If you select a private interface, configure a network and a subnetwork according to the steps below.
To configure a network, select an existing network from the drop-down list or create a new one by clicking Add a new network. If you choose the latter, the new window will open:
Enter the network name.
(optional) Turn on the Bare Metal Network toggle to connect bare metal servers to the network
(optional) Turn on the Add tags toggle to add metadata to the network.
Click Create network.
To create a subnet, select an existing subnet from the drop-down list or create a new one by clicking Add a new subnetwork. If you choose the latter, the new window will open:
Enter the subnet name.
Set CIDR between ranges: 10.0.0.0 - 10.255.255.255, 172.16.0.0—172.31.255.255, 192.168.0.0—192.168.255.255. Set the mask between 16 and 24.
(optional) Turn on the Enable DHCP toggle to automatically assign IP addresses to machines in the subnet.
(optional) Turn on the Non-routable subnetwork toggle to block access to the subnet from external networks and other subnets. If you keep the network routable, you can specify the Gateway IP address. Otherwise, a random IP address will be assigned.
(optional) Enter Custom DNS servers to add specific DNS servers**.**
optional) Turn on Add tags to add metadata to the subnetwork.
Click Create subnetwork.
Optionally, you can turn on the Use Reserved IP toggle to assign a reserved IP address to your instance and/or turn on the Use Floating IP toggle to assign a floating IP address to your instance.
7. For Firewall settings, select the default firewall or create a new one by clicking Add firewall.
If you keep the default firewall, the incoming traffic will be allowed over ICMP, TCP (SSH) and RDP protocols.
If you want to create a new firewall, refer to the article: Add and configure a firewall.
8. Configure an SSH key for a remote SSH connection. You can add an existing SSH key or generate a new one. For instructions on how to generate and configure the key, check out this guide: Connect to an instance via SSH.
In addition to SSH keys, you can also set up a password for your instance, as described in step 9. Setting a password is necessary if you want to connect to a Linux instance from the Customer Portal.
8. Configure Access by setting a password for the Admin user.
Your password must contain between 8 and 16 characters, including at least one lowercase letter (a-z), one uppercase letter (A-Z), one number (0-9), and one special character (!#$%&’()*+,-./:;<=>?@[]^_{|}~).
You can use passwrod to connect to a Windows instance from the Gcore Customer Portal or from your computer using RDP (Remote Desktop Protocol).
9. (optional) Configure Additional options.
cloud-init
agent.You can configure your password to connect to your Linux instance from your Control Panel or via SSH. To do it, insert the following code to the field, replacing **your password**
with your chosen password:
#cloud-config
password: **your password**
chpasswd: { expire: False }
ssh_pwauth: True
On Cloud instances with Windows OS, you can't use the password
parameter both in the “Access” and “User data” fields. Since the "Access" field is required, configuring user data on Windows instances is not possible.
Read more about the allowed instance parameters in our API docs.
You can configure the password hash—a machine-readable set of symbols. It’ll protect your real password from being compromised. To generate a hash, use the Python script:
#!/usr/bin/env python3
\# based on [https://stackoverflow.com/a/17992126/117471](https://stackoverflow.com/a/17992126/117471)\# pip3 install passlib
import sys
from getpass import getpass
from passlib.hash import sha512_crypt
passwd = input() if not sys.stdin.isatty() else getpass()
print(sha512_crypt.hash(passwd , rounds = 5000 ))
If an instance is only in a private subnet, DHCP must be enabled in the settings of this subnet, so you can log in with a password.
You can place your virtual machine in one of three types of groups:
Affinity groups assemble virtual machines on the same hardware. Machines launched in one affinity group will exchange data faster because they are located on the same server.
Anti-affinity groups work the opposite way: All virtual machines in this group will be separated across different physical hardware. This increases fault tolerance of a cluster: Even if something happens to one server, machines on the other(s) will remain available.
Soft anti-affinity groups encourage, but don't strictly enforce, the separation of virtual machines. Unlike a strict anti-affinity policy, where machines may never be placed together, soft anti-affinity allows placement on the same hardware when it is necessary due to factors like resource constraints or high demand. It is suitable for users who want to use the anti-affinity policy by default while also avoiding machine creation failures if an unused host was not found.
You can add the instance to an existing placement group or create a new one by clicking Add placement group.
10. Specify the number of machines with the same configuration you need and give them names.
The maximum number is limited by your quotas.
For names, use Latin characters, underscores, spaces, and dots.
11. Click Create virtual machine.
Your server will be transitioned to the Building status. The system will allocate resources for your virtual machine.
After that, the server will be automatically moved to the Power on status. Your machine is ready to run!
Was this article helpful?
Discover our offerings, including virtual instances starting from 3.7 euro/mo, bare metal servers, AI Infrastructure, load balancers, Managed Kubernetes, Function as a Service, and Centralized Logging solutions.