This is the multi-page printable view of this section. Click here to print.
Documentation
- 1: Compute
- 1.1: Types of VPS
- 1.2: Custom VPS Config
- 1.3: Create VPS
- 2: Network
- 2.1: VPC
- 2.1.1: Create VPC
- 2.2: VPC-Network
- 2.2.1: Create VPC-Network
- 2.3: Network ACL (NWACL)
1 - Compute
VPS is a virtual machine (VM) that is allocated resources like vCPU, RAM, and disk storage.
In Cozeon Cloud Platform, all VPS have following underlying hardware, by default:
- Premium AMD EPYC CPUs
- 3200 MHz DDR4 RAM
- NVMe-SSD storage
- Additional storage can be NVMe-SSD or HDD (RAID)
1.1 - Types of VPS
A VPS could be one of two types:
- Shared vCPU
- Dedicated vCPU
VPS (Shared vCPU)
This type of VPS gets a shared vCPU.
There is only one VPS configuration for this type of VPS:
VPS-SHRCPU: 1vCPU, 512MB RAM, 12.5GB NVMe-SSD, 500MB Data Transfer out
Since this type of VPS has shared vCPU, it is ideal for running moderate to low workloads.
It’s also the least configuration available, for a VPS, in Cozeon Cloud Platform.
Higher configurations cannot be created using shared vCPU configuration (VPS-SHRCPU).
For VPS pricing, take a look at the Pricing page
VPS (Dedicated vCPU)
This type of VPS gets a dedicated vCPU.
These are ideal for running heavy workloads, 24/7.
Again, there is only one VPS configuration, to start with, for this type of VPS:
VPS-DEDCPU: 1vCPU, 1GB RAM, 25GB NVMe-SSD/125GB HDD, 1TB Data Transfer-Out
This configuration (VPS-DEDCPU), is the base VPS configuration and can be used as it is, and it also serves as the building block for all the custom higher configurations you may choose for deploying VPS.
To know more about custom VPS configurations, take a look at the Custom VPS Config
1.2 - Custom VPS Config
VPS configuration could be one of two types:
- VPS-SHRCPU (for Shared vCPU)
- VPS-DEDCPU (for Dedicated vCPU)
VPS-SHRCPU
This configuration is for VPS with a shared vCPU.
Following are the details of this VPS configuration:
VPS-SHRCPU: 1vCPU, 512MB RAM, 12.5GB NVMe-SSD, 500MB Data Transfer out
It’s the least configuration available, for a VPS, in Cozeon Cloud Platform.
VPS-DEDCPU
This configuration is for VPS with a dedicated vCPU.
Following are the details of this VPS configuration:
VPS-DEDCPU: 1vCPU, 1GB RAM, 25GB NVMe-SSD/125GB HDD, 1TB Data Transfer-Out
This configuration is the base VPS configuration and can be used as it is, and it also serves as the building block for all the custom higher configurations you may choose for deploying VPS.
Higher configurations can be created using Dedicated vCPU configuration (VPS-DEDCPU).
Higher VPS Configurations
Higher VPS configurations are created, using the base configuration (VPS-DEDCPU), along with additional RAM and disk storage, as per requirement.
For e.g, if you need a VPS with following configuration: 2vCPU, 4GB RAM, 120GB NVMe-SSD
VPS-DEDCPU (base config) = 1vCPU, 1GB RAM, 25GB NVMe-SSD/125GB HDD, 1TB (DTO)
2 x VPS-DEDCPU = 2vCPU, 2GB RAM, 50GB NVMe-SSD, 2TB (DTO)
Additional RAM required to make 4GB = 2GB
Additional storage required to make 120GB = 70GB NVMe-SSD
Custom Config = 2-VPS-DEDCPU-2GR-70GSD
RAM and Storage can only be added to base VPS configuration.
RAM and Storage cannot be reduced from base VPS configuration.
1.3 - Create VPS
To create a VPS, you need to perform the following steps, or take a look at the tutorial video at the end of this article.
-
Login to the Cozeon Cloud Console.
-
After login, click on “Virtual Machine”, on the left side bar.
-
Click on “Create new VM”.
-
Select a VPS configuration, and click “Next”. This will open up “Create New VPS” wizard.
-
Select an Operating System (OS) from the “Select Operating System” drop down, and click “Next”.
-
Enter a tag/name for the VPS in the “Add Tag (for VPS)” box, and click “Next”.
-
Select a VPC from the “Select VPC” drop down
- Select a Network from the “Select Network” drop down.
- This will display the “Start IP” and “End IP” values in the “Selected Network Details” column.
- Click “Next”.
-
Verify the data before submitting.
- Click “Previous” if you need to modify the entered data.
- Click “Previous” if you need to modify the entered data.
-
Click “Finish” to create VPS.
Tutorial Video
2 - Network
Cozeon Cloud Platform provides comprehensive networking options, for creating custom network Architectures, including network segments via VPC and VPC-Networks, and fine-grained Network Access Control via Network ACLs (NWACLs).
2.1 - VPC
In Cozeon Cloud Platform, a VPC (Virtual Private Cloud) allows logical isolation of resources (VPS, Networks) from those in other VPCs, in your account, as well as from those of other customers.
A VPC consists of one or more VPC-Networks.
More information on VPC-Networks can be found here
2.1.1 - Create VPC
To create a VPC, you need to perform the following steps, or take a look at the tutorial video at the end of this article.
-
Login to the Cozeon Cloud Console.
-
After login, click on “Virtual Private Cloud”, on the left side bar.
-
Click on “Create new VPC”.
-
Enter a name and a description, for the new VPC, in the corresponding text boxes.
-
Enter a Name, for the Default Public Network, of the new VPC.
-
Click “Next”.
-
Select Number (quantity) of IPs needed for the Default Public Network, of the new VPC.
-
Select Subnet Prefix for the Default Public Network, of the new VPC.
-
Select Subnet for the Default Public Network, of the new VPC.
-
Click “Next”.
-
Verify the selected/entered info.
- Click “Previous” if you need to modify the entered info.
- Click “Previous” if you need to modify the entered info.
-
Click “Finish” to create a new VPC.
Tutorial Video
2.2 - VPC-Network
A VPC-Network resides within a VPC. Each VPC-Network inter-connects two or more VPSs.
Also, each VPC-Network is isolated from other VPC-Networks within the same VPC, VPC-Networks in other VPCs in your account, as well as VPC-Networks in VPCs belonging to other accounts/tenants.
A VPC-Network could be one of two types:
Private Network
A Private VPC-Network isolates VPSs from all other VPC-Networks.
By default, a VPS in a Private VPC-Network does not have a Public IP assigned to it.
Hence, such a VPS is not reachable from any other Network, either a VPC-Network or the Internet. However, it does get assigned a Private IP.
All VPSs in a Private VPC-Network can access each other via their assigned Private IPs.
Also, a VPS in a Private VPC-Network cannot initiate communication with any other VPS in other VPC-Networks, through Private IPs.
However, Private VPC-Networks allow outgoing traffic to Internet. Hence, a VPS in a Private VPC-Network can:
- access any Public IP on the internet, while still not being reachable from anywhere on the internet.
- access VPSs in any other Public VPC-Network, provided the target VPS has a Public IP.
Public Network
A VPS in a Public VPC-Network is assigned a Public IP, by default.
Hence, all VPSs in a Public VPC-Network are reachable, on their Public IPs, from any other Network, either a VPC-Network or the Internet.
A VPS in a Public VPC-Network is also assigned a Private IP. However, a VPS in a Public VPC-Network will be unreachable on it’s Private IP, from outside the VPC-Network.
2.2.1 - Create VPC-Network
To create a VPC-Network, you need to perform the following steps, or take a look at the tutorial video at the end of this article.
-
Login to the Cozeon Cloud Console.
-
After login, click on “Networks”, on the left side bar.
-
Click on “Create new Network”
-
Enter a Name and a Description, for the new Network, in the corresponding text boxes.
-
Select a Parent VPC.
-
Select Network Type.
-
Click “Next”.
-
Select Number (quantity) of IPs needed for the new Network.
-
Select Subnet Prefix for the new Network.
-
Select Subnet for the new Network.
-
Click “Next”.
-
Verify the selected/entered info.
- Click “Previous” if you need to modify the entered info.
- Click “Previous” if you need to modify the entered info.
-
Click “Finish” to create a new VPC-Network.
Tutorial Video
2.3 - Network ACL (NWACL)
A Network ACL (NWACL) is associated with a VPC-Network, and provides fine-grained Network Access Control, for your VPC-Network.
Each Network ACL (NWACL) consists of a list of Rules (NWACL Rules), similar to firewall rules, and can be used to “Allow” or “Deny”, “Incoming” or “Outgoing” network traffic.
NWACL Rule
Each NWACL Rule is automatically assigned an “ID” by the system, and cannot be modified.
Also, for each NWACL rule you can:
- specify a Name
- specify a Sequence number
- Sequence numbers determine the order of execution of rules.
- Lesser Sequence numbers, have higher priority, and are executed first.
- select either “Allow” or “Deny” network traffic
- select either “Incoming” or “Outgoing” network traffic
- select Protocol -> TCP/UDP/Ping
- specify application Port number (22, 80, 8080 etc.)
- specify Network IP(s) or Subnets.
Following operations are permitted on NWACL Rules:
- Add new Rule(s)
- Copy an existing Rule to create a new Rule, which will automatically be assigned a unique “ID”.
- Delete a Rule (Saved or Submitted).
- Modify a non-Submitted Rule.
- Save a modified Rule.
- A “Saved” Rule is not applied to your VPC-Network.
- It needs to be “Submitted” to be applied to your VPC-Network
- Submit a Rule
- A “Submitted” Rule is applied to the Network.
- A “Submitted” Rule cannot be:
- modified.
- re-Submitted.
- A “Submitted” Rule can be:
- deleted.
- copied to create a new un-Submitted and un-Saved Rule.