# Service Portal Cloudeka Cloudeka is a Cloud Computing platform that provides various cloud services including computing, storage, networking, and more. Cloudeka is supported by self-service through the dashboard service portal with features to configure, create projects, check billing, view and create rules in the organization. users can choose carefully from these services to develop new applications, or run existing applications on Cloudeka. Users can choose carefully the services to develop new applications, or to run existing applications on Cloudeka. There are two types of projects: **Prepaid** and **Postpaid**. 1. **Prepaid** For the Prepaid type, it is used for personal needs that use personal email addresses and can only have one project so that the subscription period is relatively short without a letter of contract. For payment methods using **Virtual Account, LinkAja, OVO, Credit Card**. At the beginning of registration, the deposit must be at least IDR 50,000.00. Make sure that the deposit is enough to be able to use a new service subscription, if the daily requirement used is above IDR.50,000,00, then at least the deposit content is as big as the daily requirement. This type is calculated using three methods: **PPU (Pay Per Use), Monthly, and One Time.** 2. **Postpaid** The Postpaid type is used for companies and registers using the company's email address so that the subscription period is relatively long and there is a contract letter. For payment methods using **Virtual Account and Credit Card.** # Starter Guide Deka Flexi ## Introduction Cloudeka is a cloud computing platform that provides a variety of cloud services including computing, storage, networking, and others. Cloudeka is supported by self-service through the service portal dashboard with features for configuring, creating projects, checking billing, viewing, and creating rules within an organization. Users can choose carefully the services to develop new applications or to run existing applications on Cloudeka. ## Cloudeka Configuration To be able to use Cloudeka services, you need to perform several steps including listing corporate accounts to log in and out of Cloudeka portal services, configuring VPC Network, creating a Virtual Machine instance, configuring IP floating, and configuring route firewall security ### Sign Up To enjoy the Cloudeka portal service, you first register an account by accessing Cloudeka in your browser, and then the Sign in Now! page. will be displayed, and click the Sign Up button.

After that you will be asked to fill in the fields below.

The following is an explanation of the fields in the form Sign Up

Column	Description
Full Name	User's full name
Email	Used when signing in, email currently only supports corporate email
Password	Consists of a minimum of 16 characters using a combination of uppercase, lowercase, numbers and symbols. This is made for customer data security. If the password created is not in accordance with the existing conditions, a warning will appear, for example:must Include symbol
Phone Number	User's telephone number
NPWP Number	NPWP number of prospective users
Upload NPWP	Upload a photo of the user's NPWP
Upload KTP	Upload a photo of the user's KTP

Click Check Box Term of Services and click the Sign Up button. Then will pop up Congratulations Your account has been successfully created! Please check your email for your account verification.

For email verification, you can click the Verify Your Email Address button and follow the next steps. However, if the Verify Your Email Address button cannot be used, click the available link or copy the link to your browser.

If the email is verified, the Verification Successfull pop up appears! You have succeededfully email verification. Now you can login to Lintasarta.

Now you already have an account on Cloudka's portal service. For the next time, if you want to access the cloud portal service you can Sign In. Access the Clodeka in the browser, and the Sign In Now page displays! To log in to the Cloudka portal service, fill in the Email Address and Password fields that you previously registered, and click the Sign In button.

For new users, you will be prompted to fill in the Create Organization form and click the Create Organization button. You have to fill in all the columns. After all the columns are filled in, click the Create Organization button.

Column	Description
Name of Organization	Organization Name
Details	Organization Description
Address	Organization Address
Phone Number	Organization Phone Number

After creating an organization, you will be asked to create a new project by filling out the Create New Project form. You must fill in all fields. After all the fields are filled in, click the button Create Project. It forms the basis for using all portal services Cloudeka.

Column	Description
Project Name	Project name
Description Project	Description about the project

If Sign In has succeeded, Cloudeka portal service will display project list information such as Project, Project ID, Region, Description, Activation Date, and Payment Method.

If you want to add a project, click Create New Project on the right, and then display Add New Project page. There are several columns available: 1. **Project Name** is the name used to identify projects with other projects, such as the Project Name, 2. **Project ID** is a unique identifier used to identify a project, 3. **Region**, there are three regions in TBS Jakarta, JAH Jawa Barat, and TKP Banten, 4. **Status** is the condition of a project in Active or Inactive. 5. **Activation Date** is the time the project can be used. 6. **Payment Method**, there are two types: * Prepaid is used for project types with personal email accounts that use relatively short periods without a letter of the contract. * Postpaid is used for a type of project with a corporate email account that uses relatively long subscription periods and a letter of contract. 7. **Type** is the type of project used, currently in the Cloudeka portal service there are two types, namely Deka Flexi and Deka Prime. When you have finished using the Cloudeka service portal, you can quit the Cloudeka portal service by clicking the customer name at the top right, and click the Logout button.

Then you will return to the page Sign In.

### Create VPC Network VPC Network (virtual private network) is a virtual version of the physical network architecture implemented in the portal service Cloudeka. VPC Network ensures secure traffic between any resources such as instances, kubernetes clusters, database clusters and load balancers. Any resources you create within the VPC can communicate securely through private IP addresses. To create a VPC Network, you first open the page Network.

On the VPC tab click the button Create VPC.

Select the Wizard Simple tab and fill in the create vpc network standard form.

The following is an explanation in the Create VPC Network column.

Column	Description
Name	Name of VPC Network.
Desciption	A brief description of VPC.
Billing Type	For payment types according to project type. Fixed Pay Per Use Trial
Configure IP Range	Enter Private IP Address also the subnetmask, The Internet Assigned Number Authority (IANA) has assigned several address ranges to be used by private networks. Address ranges to be use by private network are: - Class A: 10.0.0.0 to 10.255.255.255 - Class B: 172.16.0.0 to 172.31.255.255 - Class C: 192.168.0.0 to 192.168.255.255 An IP address within these ranges is therefore considered non-routable, as it is not unique. Any private network that needs to use IP addresses internally can use any address within these ranges without any coordination with IANA or an Internet registry. Addresses within this private address space are only unique within a given private network.
VPC Type	There are two types available on the VPC: Simple support services that need to be connected to the internet and have access to resources outside the VPC. Isolated is used to fully isolate resources and data from the internet or other resources outside the VPC. VPC type difference is the simple type you can add Floating IP to the network configuration.

* After filling out all the forms in the VPC Network, click Create VPC Network.

### Create VM Instances A Virtual Machine (VM) is a virtual version of a physical computer. VM can run programs and operating systems, store data, connect to networks, and perform other computing functions. You can add disks and define network interfaces according to system requirements. To create an instance, click the Instance menu.

Click the button Create Instance.

The Create Instance page displays. Select operating system. Then fill in the Select Operating System & Version column by clicking the Select Operating System column, version, bit version.

Create Instance - Select Operating System

In the Zone column select Arjuna.

Then choose Billing Type. There are three types of billing types among them PPU(Pay Per Use), Fixed, and Other according to the type of project used.

Select a previously created VPC Network.

Select the type of Processor that will be used, Intel Processor or AMD Processor with High Core or High CPU.

Select Choose a Plan to specify the type of machine and specify the CPU and Memory size that your virtual machine will use.

Column	Description
General	VM size provides a balanced CPU to memory ratio.
Compute Optimized	Delivers the highest performance CPU in Compute Engine and is optimized for compute-intensive workloads.
Shared	Provides a cost-effective method for running small applications that are not resource-intensive.
Memory Optimized	Provides a high memory to CPU ratio, optimized for memory-intensive workloads.

Type	Description	vCPU/RAM
Shared	Based on 1 vCPU	1 vCPU/1GB, 1 vCPU/3GB, 1 vCPU/4GB
General	CPU:RAM eq 1:2, 1:3	2vCPU/4GB, 2vCPU/6GB, 4vCPU/8GB, 4vCPU/12GB, 8vCPU/16GB, 8vCPU/24GB, 16vCPU/32GB, 16vCPU/48GB, 32vCPU/64GB, 32vCPU/96GB
Compute Optimized	CPU:RAM eq 1:1	2vCPU/2GB, 4vCPU/4GB, 8vCPU/8GB, 16vCPU/16GB, 32vCPU/32GB
Memory Optimized	CPU:RAM eq 1:4	2vCPU/8GB, 2vCPU/16GB, 4vCPU/16GB, 4vCPU/32GB, 8vCPU/32GB, 16vCPU/64GB, 32vCPU/128GB

Select the type of storage for the root disk, there are 2 options among them Standard Column SSD with 750 - 2500 IOPS or Premium SSD Volumes with 2250 - 4500 IOPS.

On column Instance Root Disk, enter or select a size to determine the size of your OS disk. Minimum root disk size 20 GB. You can adjust the root disk requirements according to your needs.

Create Instance - Instance Root Disk Size

Select storage for disk data, there are 2 options among them Standard Volume SSD with 750 - 2500 IOPS or Premium SSD Volumes with 2250 - 4500 IOPS.

Create Instance - Data Disk Storage Type

Enter the size for the volume type that will be used then click the button Add.

Create Instance - Instance Data Disk Size

Click button Add Custom Data Disk if you want to add additional storage to the VM (beyond the root disk/OS disk).

Create Instance - Add Instance Data Disk Size

There are **two methods** for **authentication** namely, using **SSH Keys** or use **Password**, this authentication is used to log into the virtual machine. 1. **SSH Keys**, are more secure than standard passwords. You must generate an SSH Key before you can use this method. * Select SSH Keys for the authentication method, then click Add New SSH Keys

* Paste the Public Key you previously obtained, type the name of your key and click Add SSH Key.

* Check the SSH Key Checklist that you just added.

2. **Password**, use the default password for the authentication method.

On Instance Name, type your VM name, this instance name is also your VM hostname. The Instance Name cannot use special characters either, and click Create Instance. Check the Term of Service and click the Create Instance button.

There is a notification Building Instance (nama-instance) that states that the instantiation process is being carried out.

Create Instance - Build Instance Notification

After the building instance is successful, there will be a success notification Instance (nama-instance) has been successfully created.

### Create Floating IP Floating IP is a public static IP address used by VM in instances that provides access from an external network to VM in instances without a public network interface. If your instance requires a public IP address for Internet access. You can assign a Floating IP by clicking the Network menu then selecting the Floating IP tab.

In section Floating IP Type according to your needs, there are two Floating IP Types, namely: 1. Type **Non**-**Reserved** when you Reassign Instance, the IP used will be deleted from the Floating IP list 2. Type **Reserved** if you Reassign Instance then the IP used remains on the Floating IP list so you can use the IP for other instances in your project.

Select Billing Type which will be adjusted.

On Resource Type select Instance.

On Resource Type column select the previously created Instance and in the VPC Port column select the previously created VPC.

After filling in all columns on the Floating IP tab click Assign Floating IP.

If the assigned floating IP is successful, the floating IP will appear on the floating IP list.

### Security Firewall Rute Security Firewall permits or denies connections to or from a VM based on a predefined configuration. Components allow you to target specific types of traffic, based on traffic protocol, destination ports, sources, and destinations. To create a route firewall security click the Security menu and click Create Security button.

Then fill in the Create Security form, which is the Name, and Description column.

In the Inbound Rule section press the New Rule key to add a rule.

The following is an explanation of the form create security above

Column	Description
Name	Nama Security.
Description	Is a column to make a description of the security created.
Inbound Rule	Specify traffic allowed to instances on which ports and from which sources.
Outbound Rule	Specify traffic that is allowed to leave the instance on which port and to which destination.

Then select Apply to Instance (for which instance this security was created), click the Create Security Firewall button to continue with the process.

There will be a notification if the Firewall has been successfully created.

## Conclusion This is a guide to the initial configuration of using the Cloudeka portal service, from how to register your co-portate account to logging in or out into the Cloudeka portal service, to configuring the VPC Network, creating VM instances, creating IP floating, and security firewall routes. It is hoped that this guide will help you understand and perform the initial configuration for your use of Cloudeka portal services. For more complete use of Cloudka portal services, you can read the instructions on [Documentation Cloudeka](/cloudeka_portal_service). # Introduction # Sign Up To be able to access the Services Portal Cloudeka you must first have an account. It only takes one time Sign Up in the following way, access [Cloudeka](https://cmd.cloudeka.id/) on your browser, then the Sign In Now! page will open. * Then click the **Sign Up** button.

After that you will be asked to fill in the fields below:

Column	Description
Fullname	Customer's full name.
Email	Which will be used when you Sign In, the email currently only supports corporate email.
Password	Consist of a minimum of 16 characters using a combination of uppercase, lowercase, numbers & symbols. It is made for the security of customer data. If the password created does not match the existing provisions, a warning will appear, for example: must include the symbol.
Phone Number	Customer's phone number.

* Click **Check Box Term of Services** and click the **Sign Up** button. then a pop up will appear **Congratulations Your account has been successfully created!. Please check your email for your account verification.**

* For email verification, you can click the **Verify Your Email Address** button and then follow the next steps. However, if the **Verify Your Email Address** button cannot be used, then you can use the provided link, by clicking the link or copying it to your browser.

* If it is finished, a pop up will appear **Verification Successfull! You have successfully email verification. now you can login to Lintasarta**

* Now you have an account in Services Portal Cloudeka. For further, if you want to access Service Portal Cloudeka you can Sign In. # Sign In If you already have an account on the Service Portal Cloudeka, then all you need to do is access [Cloudeka](https://cmd.cloudeka.id/) on your browser, it will open the Sign In Now! page. To Sign In, fill in the **Email Address** and **Password** fields that you registered earlier, enter the **CAPTCHA code shown,** then click the **Sign In** button. {% hint style="warning" %} Users who are unable to **Sign In** will be redirected to the new [**Service Portal Cloudeka**](https://ai.cloudeka.id/). The system will display a notification informing users that the system has been updated. Users can use their existing account to sign in to the new platform. {% endhint %}

For new users, you will be asked to fill in the Create Organization form, namely:

Column	Description
Name of Organization	Your Organization name
Details	Details or description of your Organization
Address	The address of your Organization
Phone Number	Phone number of your Organization

You must be fill the fields, after all the fields are filled, click the **Create** button.

* After creating Organization, new customers will be asked to create a new project by filling out the Create New Project form, namely.

Column	Description
Project Name	The name of your project
Description Project	Description of your project

You must be fill the fields, after the fields are filled, then click the **Create Project** button. This Project is the basis for using all Cloudeka services.

* If Sign In has been successful, the Service Portal Cloudeka will display project list information such as project name, project ID and a brief description of the project.

# Sign Out When you have finished using the Service Portal Cloudeka, you can exit the application by: * Click the customer's name on the top right

* Select the **Logout** button.

* After that, you will return to the **Sign in** page.

# Forgot Password If you forget the Password used when you will Sign In in the Service Portal Cloudeka. You can use the **Forgot Password** button to recover the password, customers can do the following ways: * Click **Forgot Password** button.

* Fill in the email field, then click the **Submit** button.

* Then a pop up will appear **"Request Success, Please check your email to change your password"**

* To change the password, click the **Reset Password** button that the Cloudeka application sent to your email. However, if the Reset Password button cannot be used, then you can use the link provided.

* You will be asked to fill in the form **Create New Password**. fill the fields, namely:

Column	Description
New Password	Type your new password, the password cannot be the same as before, consist of a minimum of 16 characters using a combination of uppercase, lowercase, numbers & symbols. It is made for the security of customer data. If the password created does not match the existing provisions, a warning will appear, for example: must include the symbol
Confirm New Password	Re-type your new password

* Then click the **Create Password** button.

* If the process of changing password is successful, you can Sign In by using a new Password. # Project The Project menu is the basis for creating, activating, and using all services in the Cloudeka application. # Create a New Project On this page, you can create a new project that will be registered in the Cloudeka application. Customers can create more than one project. * Click the **New Project** menu.

* Fill the fields in the Add New Project window.

Column	Description
Project Name	The name of your project
Description Project	Description of your project

You must be fill the fields, then click the **Create** button.

* If the new project has been successfully created, a pop up will appear **"Data has been saved! Your data has been submitted. Please wait if the data has not appeard".**

# List Service If you have been successfully create a project, you can see the information of project service limit. The service limit are usage status **Instance, Storage, Object Storage** and **Network**. * On project list page, click the project name that you want to see it service limit information. **For example**, click **demo-cloudeka.**

* The project detail will be appear, and then click **List Service** button.

* The information of service limit of the project will be display

# Delete Project If you want to delete existing project data in the Cloudeka application, you must delete all existing services first. Please follow the steps below. * On the main page there is a list of projects stored in the Cloudeka application. Select the project name to delete.

* Project details will appear, then click the **Settings Project** button

* Click the **Delete Project** button.

* Select the **Delete Project** button to continue the process of deleting the project or the Cancel button if you want to cancel the process of deleting the project.

* A warning will appear regarding the deletion of project data, if you are sure and know all the consequences, please type the name of the project to be deleted in the column provided: type \[Project Name], example **\["Test Project"]**, then click the button **"I understand the consequences, delete this repository"**.

* Deleted data will no longer appear on the main page.

# Profile Setting This menu is used to manage your profile, such as changing your password or changing your profile by following these steps: * On the top right side of the main page, click **your name**, then select the **My Profile** menu.

* The **My Account Settings page will appear**. On this page there are 2 button options, namely **Change Password** and **Edit Profile**. If you want to change the password, then click the **Change Password.**

* Complete the **Change Password** form, namely.

Column	Description
Old password	Your current password
New password	Your new password, Consist of a minimum of 16 characters using a combination of uppercase, lowercase, numbers & symbols. It is made for the security of customer data. If the password created does not match the existing provisions, a warning will appear, for example: must include the symbol
Confirm new password	Re-type your new password

Then click the **Update** button if you want to continue changing the Password or click the Cancel button if you don't want to change the password.

* You can already use the new password. * If you want to edit the data, click the **Edit Profile** button.

* Then fill in the data you want to change such as. | Column | Description | | ---------------- | -------------------------------------------- | | **Full Namme** | Customer full name | | **Phone Number** | Customer phone number | | **Address** | Customer address | | **Email** | Customer email, this email cannot be changed | When finished, click the **Update Profile** button to save the data or **cancel** if you want to cancel the data changes.

* The updated data will appear on the My Account Settings page. # Multi Factor Authentication **Multi Factor Authentication (MFA)** is a security method that requires more than one proof of identity during the user authentication process to protect access. In general, MFA combines multiple authentication factors, in the Service Portal AI using **TOTP (Time-based One-Time Password)**. This guide will explain about enabling the MFA feature. ## Enable Multi Factor Authentication {% hint style="success" %} You cannot disable the MFA feature once you have enabled it. If you have not enabled this feature, you cannot use Service Portal Cloudeka. {% endhint %} **Enable Multi-Factor Authenticator** is one of the features available on the Service Portal Cloudeka to increase account security against hacking or data theft. After Multi Factor Authentication, you are required to go through the process of entering TOTP as an additional verification every time you log into the AI Portal Service. In the **Service Portal Cloudeka**, you can activate the MFA feature by select your account name and click **My Profile**.

You will be redirected to the Profile page. On the **Multi-Factor Authentication** section, there is **Enroll New Code you can swipe right to enable** the feature.

A **Confirm Password** window will appear. Ensure that the password entered matches the password you use to access the **Service Porta Cloudeka**. Click the **Confirm** button to enable Multi-Factor Authentication.

The screen will display as shown below. Make sure to securely save your account name and secret key as a backup in case you need them later.

In the next step, you can download an authentication app on your smartphone. This guide only demonstrates the use of Google Authenticator and Microsoft Authenticator. For Android smartphone users, here are the links for [Google Authenticator](https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2) and [Microsoft Authenticator](https://play.google.com/store/apps/details?id=com.azure.authenticator). For iOS smartphone users, here are the links for [Google Authenticator](https://apps.apple.com/us/app/google-authenticator/id388497605) and [Microsoft Authenticator](https://apps.apple.com/us/app/microsoft-authenticator/id983156458). # Using MFA Google Authenticator # Using MFA Microsoft Authenticator If you have already downloaded and installed **Microsoft Authenticator** on your smartphone, open **Microsoft Authenticator** on your smartphone.

On the **Microsoft Authenticator** main page, tap the **plus icon** at the top. There are three types of accounts that can be added: **Personal Account**, **Work or School Account**, and **Other Accounts (Google, Facebook, etc.)**. You should select **Other Accounts (Google, Facebook, etc.)**. There are two methods to add an account in **Microsoft Authenticator**: 1. Scan QR Code If you select **Other Accounts (Google, Facebook, etc.)**, you will automatically be directed to the **Scan QR Code** page. Point your camera at the saved QR Code. 2. Enter code manually If you do not have the QR Code saved, you can tap the **Enter code manually** button on the **Scan QR Code** page. This will open the **Add Account** page, where you need to enter the **Account Name** and **Secret Key** that you obtained when activating Multi-Factor Authentication in the **Deka GPU Portal Service**. # Organization The Organization menu is the root node in the Cloudeka resource hierarchy and is the super node in the project hierarchy. # Manage Role Organization This menu is used to grant/set user permission to do tasks in the Cloudeka application. This helps the organization assign/deploy tasks to the right people. There are basically 2 roles on Cloudeka, namely: 1. **Owner**, can view and change all features. 2. **Member,** default role for each organization, this role only allows you to see all features. ## Create New Role Allows you to create custom roles that help you determine the principle with the lowest privilege, it helps ensure that your principles only have the permissions they need. To create a New Role, click the **Organization** menu then select the **Manage Role** menu.

* On the **Manage Role** page, click the **Create New Role** button.

* Fill in the form Create Role there are:

Column	Description
Role Name	Role name that will be create
Description	Role description, ex: admin member
Privileges	To determine the service permission to be given to the user assigned the role

On **Privileges**, there are also the following fields:

Column	Description
Access	To determine what services will be granted access
Permission	To determine whether or not permission is granted for the service
Editor	If you tick in the editor field, then it gives access to full access
Viewer	If you tick in the viewer field, then it gives access to read-only

If you have finished filling out the form, click the **Save Role** button to save or **cancel** if you don't want to create a role.

* The new role will appear on the **Manage Roles page**.

## Edit Role If you want to change the Role data, on the **Manage Role** page there is an Action column, click the **Edit** button.

Change the data as you need, there are: | Column | Description | | --------------- | ----------------------------------------------------------------------------- | | **Role Name** | Role name that will be create | | **Description** | Role description, ex: admin member | | **Privilage** | To determine the service permission to be given to the user assigned the role | Then click the **Save Role** button to save the changed data or click **cancel** if you don't want to change the data.

After that it will return to the Manage Role page.

## Delete Role If you want to delete a Role on a **Manage Role** page that contains an **Action** column, click the **Delete** button.

* A warning will appear, if you really want to delete click the **Delete** button, if you don't want to delete click the **Cancel** button.

* A pop up will appear "Data has been deleted!. Role data has been deleted".

* When finished deleting will Return to page Manage Role.

# Setting Organization This menu is used to manage organizational data that is already stored in the Cloudeka application. ## Edit Organization The following are the steps if a customer wants to make changes to organizational data. * Click the **Organization** menu then select **Setting Organization**.

* On the Setting Organization page there is User Organization information, namely.

Column	Description
Name	User name in Organization
Project	Project name in Organization
Role	Role of user
User Status	Status of the user is it verified or not
Status	Status of the user is it active or inactive
Created Date	User creation time
Action	To perform an action on a user, such as edit or delete user

* Then click the **Edit Organization** button.

* Fill in the data to be changed on the Edit Organization form namely.

Column	Description
Details	Description of Organization
Address	Organization address
Phone Number	Organization phone number
NPWP Number	Organization Taxpayer Identification Number, but the NPWP number cannot be changed

Then click the **Update** button if you want to save the data changes or click the **Cancel** button to return to the Setting Organization page without saving.

* If the data is successfully saved, a pop up will appear **"Data has been saved! Your data has been submitted. Please wait if the data has not appeard".**

## Add New User Organization This menu is used to create new users in the organization. * Click the **Organization** menu then select **Setting Organization**.

* On the **Setting Organization** page, click the **Add New User** button.

* Fill in the Add New User form, namely.

Column	Description
User Name	Name of user.
Email	Email address of user.
Phone Number	Phone number of user.
Select Project	To determine which project will be assigned to the user.
Select Role	To determine the role member.

After that click the **Add** button to save the new member data or click the **Cancel** button if you don't want to create new data.

* If the data is successfully saved, a pop up will appear **"Data has been saved! Your data has been submitted".**

* Then you will be asked to create a new password.

Column	Description
Password	Consist of a minimum of 16 characters using a combination of uppercase, lowercase, numbers & symbols. It is made for the security of customer data. If the password created does not match the requirements, a warning will appear, for example: must include the symbol.
Confirm New Password	Re-type your new password

* Click the **Create Password** button to save the new password.

* If the new password is successfully saved, a pop up will appear **"Success. New password has been created"**

* After that, the new member data will appear on the Setting Organization page.

## Edit User Organization Edit User Organization is used to change user data in the organization. Here are the steps. * Click the **Organization menu** then select **Setting Organization**.

* In the Action column, click **More**, then select **Edit**.

* Fill in the Edit Member form, namely

Column	Description
Member Name	Name of user.
Email	Email address of the user.
Phone Number	Phone number of the user
Select Project	To determine which project will be assigned to the user.
Select Role	To determine the role user.

Then click the **Save** button to save the changed data or **Cancel** if you don't want to save the data.

* If the data is successfully saved, a pop up will appear **"Data has been saved! Your data has been submitted. Please wait if the data has not appeared"**.

## Delete User Organization Delete User Organization is used to delete user data in the organization. Here are the steps. * Click the **Organization** menu then select **Setting Organization**.

* In the **Action** column, click **More**, then select **Delete**.

* Click the **Yes** button to delete member data or click the **Cancel** button if you don't want to delete member data.

# Check Audit Log This menu is used to view all Cloudeka application user log activities. * Click the **Organization** menu then select **Audit Log**.

* On the Activity page, all user activities will appear.

Column	Description
Event	The main activity of the user contains login, create, delete, etc
IP address	The IP address of the activity
Project	The name of the project used
Date	The date the activity was carried out

Users can also download activity logs on the Cloudeka application. Here are the steps. * Click the **Download** button.

* Select the data to be downloaded, by clicking the **Select Project** column and the **Days** column.

* Select all or one of the available projects in the Select Project column.

* Select the desired number of days, whether 1 day, 7 days, 20 days, or 30 days.

* If both columns have been selected, click the **Download** button to download the data or **Cancel** if you cancel downloading the data.

* The downloaded data will be saved in your Computer in Ms.Excel format. Click the data, then the downloaded data will appear. The data displayed is Time, ID, Action, Actor IP, Resource, Organization, Project and Metadata.

# Broadcast This menu is use to view broadcast messages sent by Administrator, containing information related to the Cloudeka Service Portal related to users. * Click the **Broadcast** tab to view the recent broadcast messages.

* There will appear the broadcast messages, it's at the top of the list. Then, click the broadcast message you want to see.

* The detail of the broadcast message will be displayed, click the **Back** button to redirect to the previous page.

# Voucher On the Cloudeka Portal Service, the voucher menu is in the Organization menu. Currently, there are two types of Vouchers available, including the following: 1. [Vouchers Trial ](/cloudeka_portal_service/voucher/voucher-trial) 2. [Vouchers Credit ](/cloudeka_portal_service/voucher/voucher-credit) 3. [Vouchers Discount ](/cloudeka_portal_service/voucher/voucher-discount) # Voucher Trial This menu is used to view the trial voucher used by the project. There are several things that an Admin User should know about vouchers: * Admin User can receive a reminder email from `info@cloudeka.id` if the trial voucher expires. * Admin Users can combine several trial vouchers to be able to try the Cloudeka Portal Service. * If the trial voucher has expired, it will be automatically deleted from the voucher page, so Cloudeka Portal Services that use a trial voucher cannot be used. * The credit voucher that has been claimed displays the following data:

Column	Description
1. Voucher Name	Is the label given to the voucher to identify the voucher.
2. Voucher Code	A unique code used to identify the voucher.
3. Limit Service	is a service limit for service instances, vCPU, Memory, Root Disk, Data Disk, Data Disk Size, Object Storage, Object Storage Size, Snapshot, Snapshot Size, VPC, Floating IP, and Load balancer that can be used.
4. Project Name	Is the project name that uses a trial voucher.
5. Validity Period	Is the period of time in which the voucher can be used.

You can claim a Trial Voucher by following these steps: * Click the **Organization** menu then select **Voucher**.

On the Voucher page select the **Voucher Trial** tab. Enter the Voucher code that was given to you then click Claim.

* The Select Project pop-up appears, select the project that will use the voucher then click **Save**.

* **Voucher has been successfully claimed!** that the voucher has been successfully claimed and can be used by the **My First Project with Prepaid project**.

* The voucher can already be used. You can see the voucher that has been claimed. You have a service Instance, vCPU, Memory, Root Disk Size, and VPC.

# Voucher Credit This menu is used to view the Credit Voucher used by the project and claim the voucher if you have a Credit Voucher code. The credit voucher that has been claimed displays the following data:

Column	Description
1. Voucher Name	The name of the project voucher used.
2. Voucher Code	A unique code that is used to identify the credit voucher.
3. Voucher Data	There are several: - Project Name the name of the project using the voucher credit. - Type there are two types of credit vouchers, including one-time vouchers and recurring credit vouchers. - Status there are two statuses on the voucher, namely Available and Unavailable. - Amount is the voucher price that must be paid by the user. - Disbursement Dateis the date on which funds or payments from the voucher will be given or distributed to the recipient of the voucher.
4. Validity Period	The date on which funds or payments from the voucher will be given or distributed to the recipient of the voucher.

If you have a Credit Voucher code, you can claim a Credit Voucher by following these steps: * Click the **Organization** menu then select **Voucher Credit**.

* Enter the **Voucher code** that you gave, then click **Claim**.

* The Select **Project pop-up** appears, **select the project** that will use the voucher then click **Save**.

* The notification **Voucher has been successfully claimed!** that the voucher can be used by the **Tech Writer** project.

# Voucher Discount This menu is used to view the Voucher Discount used by the project and claim vouchers if you have a Voucher Discount code. On the claimed Voucher Discount displays the following data:

Column	Description
1. Voucher Name	Name of the discount voucher used.
2. Voucher Code	It is a unique code used to identify discount vouchers.
3. Voucher Data	Contains the name of the project that uses and the type of discount voucher used.
4. Service Discount	Usable discount service.
5. Validity Period	Voucher validity period.

If you have a Voucher Credit code, you can claim a Voucher Credit by following these steps: * Click the **Organization** menu and select **Voucher**.

* On the Voucher page select the **Voucher Discount** tab. Enter the **Voucher code** you have and click **Claim**.

* Show a **Select Project** pop-up, **select Project** that will use the voucher and click **Save**.

* Show notification **Voucher has been successfully claimed!** that vouchers can already be used by project **Tech Writer**.

# Deka Flexi # Deka Flexi: Instance # Introduction **Deka Flexi: Compute** is an Infrastructure component of Cloudeka services that allows you to create and run virtual machines on Cloudeka Infrastructure with various types of operating systems, such as Linux (Debian, Ubuntu, Suse, Red Hat, CentOS, Alma Linux, Rocky Linux) and Windows Server, you can also run your virtual machine with CPU and Memory as needed. # Machine Type **Deka Flexi: Compute** provides various types of Virtual Machines (VM) which have been classified based on Memory, Storage, and Compute types. If you want to create a Virtual machine on Deka Flexi, you must first examine your application and workload system then you be able to select a VM machine based on the available machine types. The following types of machines are available in Deka Flexi: 1. **General**, VM size provides a balanced CPU-to-memory ratio. 2. **Compute Optimized**, delivers the highest performance CPU on Compute Engine and is optimized for compute-intensive workloads. 3. **Shared,** this provides a cost-effective method for running small applications that are not resource intensive. 4. **Memory Optimized**, provides a high memory to CPU ratio, optimized for memory-intensive workloads. # Operating Systems Deka Flexi provides an open source and closed source based operating system for your application and system platform needed. The following is a list of operating systems provided by Cloudeka: 1. **Windows Server**, an Enterprise class operating system created specially by Microsoft for use on servers. Available versions **Windows Server 2016, 2019, 2022.** 2. **CentOS**, is a free operating system derived from Red Hat Enterprise Linux (RHEL). Available versions **CentOS 6,7,8.** 3. **OpenSUSE**, is a free operating system developed and supported by [www.openSUSE.org](http://www.openSUSE.org/). Available versions **Leap-15.2, Leap-15.3, Leap-15.4.** 4. d. **Red Hat Enterprise Linux**, is an enterprise Linux operating system developed by Red Hat for the commercial market. Available versions **Red Hat 7.6, 7.7, 7.8, 7.9, 8,0, 8.1, 8.2, 8.3, 8.4.** 5. **Fedora**, a Linux distribution developed by the community supported by the [Fedora Project](https://getfedora.org/). Available versions **Fedora 34-1.2.** 6. **Debian**, is a free and open-source Linux distribution, developed by a supported community [Debian Project](https://www.debian.org/). Available versions **Debian 9.13.25, 10.10.1**. 7. **Ubuntu**, a linux distribution based on Debian and mostly free and open source, developed and supported by [Ubuntu](https://ubuntu.com/). Available versions **Debian 16.04, 18.04, 20.10, 21.04, 22.04**. 8. Rocky Linux is an open source Linux distribution and functionality similar to Red Hat Enterprise Linux (RHEL). Avaible version **Rocky Linux 8.7, 9.1**. 9. cPanel, a web-based application that provides a graphical interface for managing website and server hosting. Available version **cPanel 11.88**. 10. Alma Linux, is an operation source Linux distribution and functionality similar to Red Hat Enterprise Linux (RHEL). Available version **Alma Linux 8.7, 9.1**. # Server Group This document explain how to create Server Group according to predetermined policies. Server Group allows users to group Instances together to provide further control over how all instances can be managed in the Cloudeka portal service. There are several policies that can be added to the Cloudeka portal service:

Column	Description
Affinity	This policy directs Instances to be located on the same or physically adjacent hosts in the cloud infrastructure.
Anti Affinity	This policy directs the Instance to thus helping system resilience and availability by ensuring that if one host fails, its associated instances are not affected.
Soft Affinity	This policy directs Instances to be scheduled on hosts that do not fully satisfy affinity requirements, depending on availability, other factors.
Soft Anti Affinity	This policy directs instances to schedule unrelated instances on different hosts, but with greater discretion than the Anti Affinity policy.

# Create Server Group {% hint style="danger" %} Server Groups are provided in the Cloudeka portal service which must be created first before creating an Instance/VM. Please note, if you fail to add a Security Group configuration to the Instance, make sure you have increased the Server Group limit via the Super Admin account. {% endhint %} The first step in creating a Server Group is to click the Instance menu.

* On the Instances page, press the Server Group button.

* Click the Create Server Group.

* The Create Server Group window appears, two columns are available, namely Name and Policy. For an explanation of the Policy, see sub-section [Server Group](/deka_flexi/deka_flexi_compute/security-group). Click the Add button to add the Server Group configuration.

* Wait until the process is complete and the notification "New Server Group has been successfully created" appears.

# Detail Server Group Here are steps to view details of Server Group data that is already in use: * On the Server Group page, select the server configuration for which data details are displayed by clicking the More button and selecting Details.

* The Server Group window appears, displaying the Name used by the Server Group, the Policy used, and the Instances that use the Server Group.

# Delete Server Group {% hint style="danger" %} To delete a Server Group, make sure no instances are using the Server Group configuration. {% endhint %} The following are the steps for deleting the Server Group configuration: * On the Instance menu page in the Cloudeka portal service, press the Server Group button.

* In the Manage Server Group table, select the server configuration to be deleted by pressing the More button and selecting Delete.

* The Delete Server Group window appears, press the Delete button to continue the process of deleting the Server Group configuration.

* Wait until the process is complete, and the notification "Server Group has been successfully deleted" appears.

# Create a VM Instance {% hint style="danger" %} Before creating an instance or VM, you need to create a Virtual Private Cloud (VPC) network in [Create VPC Network](/deka_flexi/deka-flexi-network/6.1_vpc_network/create-vpc-network), and create a Server Group first in [Create Server Group](/deka_flexi/deka_flexi_compute/security-group/create-security-group). {% endhint %} This section describes how to create Virtual Machine. Virtual Machine (VM) is a virtual version of a physical computer. Virtual machine software can run programs and operating systems, store data, connect to networks, and do other computing functions. ## Create Instance from Public Image Public Image is provided by Cloudeka by default all customers have access to this image and can use it to create instances. The first step in creating a VM instance is to click the Instance menu. * Click the Create Instance button.

* On the Create Instance page there are five stages to complete the Instance creation. In the first stage, namely Details, there is Instance Name, Type Operating System or Instance Image, Zone, and Instance Billing Type.

* Determine the unique name that the VM will use in the Instance Name column, and select the Type Operating System. Then fill in the Select Operating System & Version column by clicking the Select Operating System, version, bit version column.

* Determine the Zone that will be used to select the data center location used on the VM. Select the Instance Billing Type that will be used. For further explanation regarding billing, you can see the Billing Page. Press the Next button to continue to the next step.

* In the second stage, namely Volume, there is the Processor, Storage Type, Default Instance Data Disk, and Custom Instance Data Disk.

* In Processor there are Intel and AMD processors. This guide uses an Intel Processor.

* Select Choose a plan to determine the type of VM machine that will be used.

	Description
General	The VM size provides a balanced CPU to memory ratio.
Compute Optimized	Delivers the highest performance CPU in Compute Engine and is optimized for compute-intensive workloads.
Shared	It provides a cost-effective method for running small applications that is not resource intensive.
Memory Optimized	Provides high memory to CPU ratio, optimized for memory-intensive workloads.

* Select the Instance size to determine the CPU & RAM resources on the VM that will be created.

Type	Description	vCPU/RAM
General	CPU:RAM eq 1:2,1:3	In General there are several Instance size options including: o1.medium.rc with the size 2vCPU and memory 6 GB, e1.medium.rc with the size 2vCPU and memory 4 GB, o1.large.rc with the size 4vCPU and memory 12 GB, e1.large.rc with the size 4vCPU and memory 8 GB, o1.xlarge.rc with the size 8vCPU and memory 24 GB, e1.xlarge.rc with the size 8vCPU and memory 16 GB, o1.cclarge.rc with the size 16vCPU and memory 48 GB, e1.xxlarge.rc dengan 16vCPU and memory 32 G, o1.qlarge.rc with the size 32vCPU and memory 96 GB, e1.qlarge.rc with the size 32vCPU and memory 64 GB.
Compute Optimized	CPU:RAM eq 1:1	In Compute Optimized there are several Instance size options including: c1.medium.rc with the size 2vCPU and memory 2GB, c1.large.rc with the size 4vCPU and memory 4GB, c1.xlarge.rc with the size 8vCPU and memory 8GB, c1.xxlarge.rc with the size 16vCPU and memory 16GB, c1.qlarge.rc with the size 32vCPU and memory 32GB
Shared	Berdasarkan 1 vCPU	In Shared there are several Instance sizes that can be used: s1.small.rc with the size 1vCPU and memory 4 GB, o1.small.rc with the size 1vCPU and memory 3 GB, c1.qsmall.rs with the size 1vCPU and memory 2 GB, c1.small.rc with the size 1vCPU and memory 1 GB.
Memory Optimized	CPU:RAM eq 1:4	In Memory Optimized there are several Instance sizes that can be used: o1.xxxxlarge.rc with the size 2vCPU and memory 32 GB, o1.xxxLarge.rc with the size 2vCPU dan ukuran memori 16 GB, s1.medium.rc with the size 2vCPU and memory 8 GB, c1.sxLarge.rc with the size 4vCPU and memory 64 GB, c1.xxxLarge.rc with the size 4vCPU dan ukuran memori 32 GB, s1.large.rc with the size 4vCPU and memory 16 GB, q1.xlarge.rc with the size 8vCPU and memory 128 GB. s1.sxlarge.rc with the size 8vCPU and memory 32 GB. s1.xlarge.rc with the size 8vCPU and memory 32 GB. s1.xxlarge.rc with the size 16vCPU and memory 64 GB, s1.qlarge.rc with the size 32vCPU and memory 128 GB, a1.xxxlarge.rc with the size 64vCPU and memory 512 GB.

* There are two types of storage, Standard Volume SSD with 750 - 2500 IOPS and Premium Volume SSD with 2250 - 4500 IOPS. Select the type of storage used.

* In the Instance Root disk column, enter or select the size for the OS disk to be used. The minimum usable root disk size is 20 GB.

* There are two types of Volume Type, namely Standard Volume SSD with 750 - 2500 IOPS and Premium Volume SSD with 2250 - 4500 IOPS. Select the Volume type to be used for disk data. The data disk is used to add additional storage to the VM (outside the root disk/OS disk), then press the Add button.

* After the Instance Data Disk is added, it will appear in the Custom Instance Data Disk section. You can add a Data Disk by pressing the Add Custom Data Disk button or delete the Data Disk configuration that has been added by pressing the Delete button. If you have configured the Data Disk, press the Next button to go to the next stage.

Create Instance - Custom Instance Data Disk

* In the third stage, namely Network, there is a VPC Network. Make sure you have created the VPC that the VM will use. For further explanation of the VPC that will be used, please [click here](https://docs.cloudeka.id/deka_flexi/deka-flexi-network/6.1_vpc_network).

* Determine the VPC to use. Press the Next Button to go to the next stage.

* In the fourth stage, namely Server Group, there is a Server Group column. Make sure you have created the Server Group that the VM will use. For further explanation of the Server Group that will be used, please [click here](https://docs.cloudeka.id/deka_flexi/deka_flexi_compute/security-group).

* Determine the Server Group to be used. Press the Next button to move the process to the next stage.

* In the fifth stage, namely Authentication, there are two authentication methods that can be used to enter the VM. The authentication methods that can be used are SSH Keys and Passwords.

1. **SSH Keys**, more secure than standard passwords. To be able to use authentication you must first create an SSH Key before you can use this method. For further explanation of the steps for creating an SSH key, see this chapter in sub-chapter 2.6 Create SSH Key for Auth Method. Following are the steps to add an SSH key: Select SSH Keys for the authentication method, then click New SSH Key.

Create Instance - Authentication - SSH Key

Paste the Public Key you got earlier, type your key name, then click Add SSH Key.

☑ Checklist the SSH Key you just added.

2. **Password**, enter the default password for the authentication method.

* After determining the authentication that will be used, press the Submit button for the VM creation process in the Instance.

* The Create Instance window appears, press the Yes, I Agree button to continue the process.

* After building the Instance successfully, a success notification appears "Instance (instance name) has been successfully created".

## Create Instance from Custom Image Custom images are only available for your Cloud project, you need to import your Custom Image into Cloudeka first in the custom image. For further explanation on importing custom images press [this link](https://docs.cloudeka.id/deka_flexi/deka_volume_images/custom-image). Then, use custom images to create the instance. The following are the steps for creating an instance using a custom image on the Cloudeka portal service: * On the Instances page, click Create Instance.

* On the Create Instance page there are five stages to complete creating an Instance using a Custom Image. In the first stage, namely Details, there is Instance Name, Instance Image, Zone, and Instance Billing Type.

* Determine the unique name used by the VM in the Instance Name column, and select the Operating System Type. Then fill in the Select Operating System & Version column by clicking the Select Operating System, version, bit version column.

* In the second stage, namely Volume, there is Processor, Storage Type, Default Instance Data Disk, and Custom Instance Data Disk.

* In Processor there are Intel and AMD processors. This guide uses an Intel Processor.

* Select Choose a plan to determine the type of VM machine that will be used.

	Description
General	The VM size provides a balanced CPU to memory ratio.
Compute Optimized	Delivers the highest performance CPU in Compute Engine and is optimized for compute-intensive workloads.
Shared	It provides a cost-effective method for running small applications that is not resource intensive.
Memory Optimized	Provides high memory to CPU ratio, optimized for memory-intensive workloads.

* Select the Instance size to determine the CPU & RAM resources on the VM that will be created.

Type	Description	vCPU/RAM
General	CPU:RAM eq 1:2,1:3	In General there are several Instance size options including: o1.medium.rc with the size 2vCPU and memory 6 GB, e1.medium.rc with the size 2vCPU and memory 4 GB, o1.large.rc with the size 4vCPU and memory 12 GB, e1.large.rc with the size 4vCPU and memory 8 GB, o1.xlarge.rc with the size 8vCPU and memory 24 GB, e1.xlarge.rc with the size 8vCPU and memory 16 GB, o1.cclarge.rc with the size 16vCPU and memory 48 GB, e1.xxlarge.rc dengan 16vCPU and memory 32 G, o1.qlarge.rc with the size 32vCPU and memory 96 GB, e1.qlarge.rc with the size 32vCPU and memory 64 GB.
Compute Optimized	CPU:RAM eq 1:1	In Compute Optimized there are several Instance size options including: c1.medium.rc with the size 2vCPU and memory 2GB, c1.large.rc with the size 4vCPU and memory 4GB, c1.xlarge.rc with the size 8vCPU and memory 8GB, c1.xxlarge.rc with the size 16vCPU and memory 16GB, c1.qlarge.rc with the size 32vCPU and memory 32GB
Shared	Berdasarkan 1 vCPU	In Shared there are several Instance sizes that can be used: s1.small.rc with the size 1vCPU and memory 4 GB, o1.small.rc with the size 1vCPU and memory 3 GB, c1.qsmall.rs with the size 1vCPU and memory 2 GB, c1.small.rc with the size 1vCPU and memory 1 GB.
Memory Optimized	CPU:RAM eq 1:4	In Memory Optimized there are several Instance sizes that can be used: o1.xxxxlarge.rc with the size 2vCPU and memory 32 GB, o1.xxxLarge.rc with the size 2vCPU dan ukuran memori 16 GB, s1.medium.rc with the size 2vCPU and memory 8 GB, c1.sxLarge.rc with the size 4vCPU and memory 64 GB, c1.xxxLarge.rc with the size 4vCPU dan ukuran memori 32 GB, s1.large.rc with the size 4vCPU and memory 16 GB, q1.xlarge.rc with the size 8vCPU and memory 128 GB. s1.sxlarge.rc with the size 8vCPU and memory 32 GB. s1.xlarge.rc with the size 8vCPU and memory 32 GB. s1.xxlarge.rc with the size 16vCPU and memory 64 GB, s1.qlarge.rc with the size 32vCPU and memory 128 GB, a1.xxxlarge.rc with the size 64vCPU and memory 512 GB.

* There are two types of storage, Standard Volume SSD with 750 - 2500 IOPS and Premium Volume SSD with 2250 - 4500 IOPS. Select the type of storage used.

* In the Instance Root disk column, enter or select the size for the OS disk to be used. The minimum usable root disk size is 20 GB.

* Determine the VPC to use. Press the Next Button to go to the next stage.

* Determine the Server Group to be used. Press the Next button to move the process to the next stage.

* In the fifth stage, namely Authentication, there are two authentication methods that can be used to enter the VM. The authentication methods that can be used are SSH Keys and Passwords.

Paste the Public Key you got earlier, type your key name, then click Add SSH Key.

☑ Checklist the SSH Key you just added.

2. **Password**, enter the default password for the authentication method.

* After determining the authentication that will be used, press the Submit button for the VM creation process in the Instance.

* The Create Instance window appears, press the Yes, I Agree button to continue the process.

* After building the Instance successfully, a success notification appears "Instance (instance name) has been successfully created".

# Details Instance This guide explains how to view instance details such as CPU usage, RAM usage, private IP address, gateway, floating IP, reboot instance, and more. Here's how to view instance details. * Click on an **Instance Name.**

* On the Instance Details page there are several menus, namely Deka Agent, Power, Storage, Resize, Networking, Snapshot, and Delete.

# Deka Agent Deka Agent used to monitor virtual machines (VM) in Deka Flexi on the Cloudeka service portal. Currently, Deka Agent can only be used on virtual machines that use the Linux operating system. For further, explanation of the stages of installing Deka Agent, click [this link](/deka_flexi/deka-agent).

# Power On Instance Power on is turning on an instance previously turned off, allowing the VM instance to run the required applications or services. This process involves booting the operating system, and once active, you will be charged based on resource usage such as CPU, memory, and network. To turn on the Instance, click the More button, and select Turn On.

Wait until the startup process is complete and a notification appears "Instance \[vm-name] has been successfully turned on.

# Power Off Instance Power off is the process of turning off a VM instance that is no longer in use. When you shut down a VM from the control panel, we first try to shut it down gracefully. If it fails, we perform a forced shutdown, which can corrupt data. To ensure data integrity, it is best to shutdown from the command line by turning off the power. When shutdown, the VM stops using CPU and memory, but data on storage remains intact. You will still be billed for disabled VMs. To end billing, delete the Instance. Pada halaman Instance pilih Instance yang akan dimatikan. To turn off the instance, select the Power menu, and in the Turn Off Instance menu, click the Turn Off button.

The Turn Off Instance window appears which explains that when you turn off the instance via the control panel, the system will try a graceful shutdown first. If it fails, the system will perform a forced shutdown, which risks data corruption. To maintain data integrity, it is recommended to shut down the instance via the command line using the poweroff command. Click the Power Off button to continue the process of shutting down the VM.

Wait until the process is complete, and a notification appears "Instance \[vm-name] has been successfully turned off".

On the VM Instances page the icon turns red.

# Reboot Instance To reboot the instance, you can do 2 reboots of which **Soft Reboot** is used to slowly restart your VM system by stopping all running processes one by one while **Hard Reboot** is used to force restart the system when your instance is already showing no response. * To get **Soft Reboot** and **Hard Reboot**, click the **Power** menu. This can be seen in the menu section **Reboot.**

* To restart the VM system by stopping all running processes one by one, click the **Soft Reboot** button, while to restart the VM system by force stopping click the **Hard Reboot** button.

* A confirmation window will appear to **Reboot**. Then click **Yes**.

* There is a **Restarting the instance** notification that your VM is being restarted.

* If your VM is successfully restarted there will be a notification **Instance \[your-instance name] has been successfully restarted.**

# Resize Instance You can change the existing machine type if it doesn't suit the workload you are running on the VM. You can change the VM machine type to match the amount of vCPU and memory as your workload changes.

* In the **Action** column, click **More**, then select **Resize Instance**.

* Select the [machine type](/deka_flexi/deka_flexi_compute/machine_type) and adjust the cpu and memory as needed, then click the Resize button.


Type	Description	vCPU/RAM
Shared	Based on 1 vCPU	1 vCPU/1GB, 1 vCPU/3GB,1 vCPU/4GB
General	CPU:RAM eq 1:2,1:3	2vCPU/4GB, 2vCPU/6GB, 4vCPU/8GB, 4vCPU/12GB, 8vCPU/16GB, 8vCPU/24GB, 16vCPU/32GB, 16vCPU/48GB, 32vCPU/64GB, 32vCPU/96GB
Compute Optimized	CPU:RAM eq 1:1	2vCPU/2GB, 4vCPU/4GB, 8vCPU/8GB, 16vCPU/16GB, 32vCPU/32GB
Memory Optimized	CPU:RAM eq 1:4	2vCPU/8GB, 2vCPU/16GB, 4vCPU/16GB, 4vCPU/32GB, 8vCPU/32GB, 16vCPU/64GB, 32vCPU/128GB

* If the data has been successfully changed, there will be a notification **"Instance flavor has been successfully changed"**.

Resize Instance - Successful Notification

# Resize Root Disk You can increase the disk root size when your VM instance needs additional storage space. You can only resize the root disk to increase its size, you cannot reduce the size of the root disk. * In the **Action** column, click **More**, then select **Resize Root Disk**.

* Enter the size of the **Root Disk** as needed, but the root disk cannot be below **20GB**. then click **Resize Root Disk** to save or **cancel** if you don't change the root disk size.

* There will be a process of expanding the size of the root disk.

Instance Page - Process Increase Root Disk

* New data that has been saved is automatically updated in the Instance list.

# Attach Interface On virtual machines in the Cloudka portal service, you can attach or detach VPC interfaces and Ports that are used by the virtual machine manually by specifying the IP address for your Instance to use. To attach a VPC make sure that you have created a VPC for the VPC creation step in sub-section VPC Network. Here are the steps to attach a VPC-based interface used by a virtual machine: * On the Cloud services portal page select the Instance menu in Deka Flexi.

* Click the Attach Interface button in the More column.

* You can choose by port or by VPC.

1. **by VPC** If you choose by VPC then you must select VPC and enter the IP address that the Instance will use.

2. **by Port** If you choose by Port but there is no Port available then you can add a port in the VPC which can be seen in sub-chapter Add Port.

* After filling in all the columns, press the Attach button and the notification "Interface has been successfully attached!"

# Detach Interface Here are the steps to detach the interface used by a virtual machine in the Cloudeka portal service: * On the Cloudeka portal service page, select the Instance menu on Deka Flexi.

* Click the Detach Interface button in the More column.

* Select the interface to detach and press the Detach button.

* The notification "Interface has been successfully detached!" that releasing the interface was successful.

# Connect to VM Instance This document describes how to connect to a VM instance. you can access it securely from your computer using Remote Desktop Protocol (RDP) for Windows Server instance or Secure Shell (SSH) for Linux instance or Cloudeka portal, here's how to access it. {% hint style="success" %} Before you connect, make sure the following prerequisites are met: * Your VM instance has a Public IP/Floating IP, if you want access from the public. * Your Cloudeka Firewall rule allows TCP inbound traffic from your client's public IP address to your instance using port 3389 for Remote Desktop Protocol (RDP) & port 22 for Secure Shell (SSH). {% endhint %} # Connect to VM Instance via Cloudeka Portal This menu explains how to connect to the virtual machine using Cloudeka Console. Access to the console in the following way, on the Instance page in the **Action** column, click **More** then select **Access Console**.

* Customers will be directed to the following page.

# Connect to Windows VM Instance via RDP (Remote Desktop) This menu describes how to connect to a Windows Virtual Machine Instance by using RDP. Access to RDP in the following way. * On your computer, open the Remote Desktop Connection application or you can use a third party tool such as mRemoteNG or another tool.

* Type the **Public IP Address** of the VM you want to remote/access, then click **Connect**.

* Fill in your VM credential, then click **ok**.

* A certificate will appear for connection verification, click **Yes**.

* Now you can access your VM.

# Connect to Linux VM Instance via SSH If you are using Windows, you will have to use a third party tool. The following instructions show how to connect to a Linux VM using [PuTTY](https://www.putty.org/)*.* * Open **PuTTY** on your computer.

* In the **Host Name** field, enter the **Public IP Address** of the VM you want to connect to, as well as the port number if you are using your VM's custom port, then click **Open**.

* If this is your first time using PuTTY to log in to your VM with SSH, there is a warning similar to the following, click **Accept**.

* After you receive the warning, the terminal asks for your username and password. Type in your **Username and Password**, then press **Enter**.

# Connect to Linux VM Instance via SSH Key If you using Windows, you must use a third-party tools. The following instructions show how to connect to Linux VM using PuTTY with SSH key. * Open **PuTTY** on your computer.

* In the **Host Name** field, enter the **Public IP Address** of the VM that you want to connect, also the port number.

* In the category list, **Expand SSH** and click **Auth**.

* Click **Browser**, choose private key that you saved before. Then click **Open**.

* After that, click **open** to connect to your VM Instance.

* It will be open the login session to your VM.

* Try login with user root and enter your passphrase key.

Login VM - Type User Root and Passphrase

* If there is a notification **“Please login as the user “centos” rather than the user “root””**, so you only can login using “centos” user.

* Please try login using “centos” user, now you can login to your VM instance.

# Create SSH Keys SSH key for authentication method more secure than standard password, if you want use SSH key for authentication you need to create the key first, follow instructions below to create SSH key. * In this tutorial we use **PuTTYgen** for generate the key. on your Windows computer open **PuTTYgen** program.

* In **PuTTY Key Generator** window, please make sure type of key to generate is **RSA**, then click **Generate**.

* After you click the **Generate** button, move your mouse in the area below the progress bar.

* When the progress bar is full, **PuTTYgen** generates you key pair.

* Type a passphrase in the **Key passphrase** field. Type the same **passphrase** in the Confirm **passphrase** field. you can use a key without a passphrase, but this is not recommended.

* Click the **Save Private Key** button to save the private key. You must save the private key, you will need it to connect to your VM instance.

*PuTTY Key Generator - Save Private Key*

* Right-click in the text field labeled **Public Key** for pasting into OpenSSH authorized keys file and choose **Select All**.

* Right-click again in the same text field and choose **Copy**.

*PuTTY Key Generator - Public Key - Copy*

* Paste it on the SSH Key Content field in the steps create VM instance using SSH Key for authentication method.

# Delete VM Instance {% hint style="danger" %} Before deleting an Instance or VM, you need to unassign the following services first: * Unassign Floating IP * Detach Storage * Unassign Security {% endhint %} The following is a list of VM instance contained in the application, for example i.e. **Centos-Test**.

In the **Action** column, click **More**, then click **Delete Instance**.

Click **Delete Instance** to delete or **Cancel** if you don't want to delete the VM instance

Deleted VM instance data no longer appears in the instance list.

# Deka Volume: Storage **Deka Volume: Storage** is the data disk you can attach to the VM. Block storage is used to host a database, support random read/write operations, and keep system files of the running virtual machines. If you need additional storage for your VM you can use Cloudeka Block Storage, a non-root disk. With block storage, it is easier to modify files because you have access to the specifically required blocks in the volumes. Block storage is mounted as a storage device on the server with underlying file system protocols such as NTFS, ext3/ext4, FAT, and others designed specifically for file operations. # Creating & Attaching a Storage or Disk You can create a blank disk and attach it to your VM instance. This is a non-root disk. * On the main page of the Cloudeka application, select the **Storage** menu.

* Click the **Create Storage** button.

* Fill in the Create Storage form, namely:

Column	Description
Storage Type	- Premium Volume SSD with 2250 - 4500 IOPS - Premium Volume SSD with 750 - 2500 IOPS
Select Volume Size	To determine size of storage that you need
Do you want to attach this storage to an instance or not?	You can choose yes if you want attach the storage to an instance, or choose not if you want attach the storage later
Select Instance	Select an instance to specify on which VM this storage will be attached
Name Volume	Name for the volume
Billing Type	According to the type of project used.
Zone	Zone to be used on Storage.

Then click the **Create Storage** button to save the data or **Cancel** if you don't want to save the data.

* There will be a notification if the data is saved successfully **"Storage has been successfully created"**.

# Formatting a Disk After you create and attach the new disk to a VM, you must format and mount the disk, so that the operating system can use the available storage space. # Formatting & mounting a disk on Windows * Open your Windows VM, right-click the Windows Start button and select **Disk Management**. {% hint style="info" %} Disk Management is a system utility in Windows that enables you to perform advance storage tasks. Here are some of the things Disk Management is good for: * To set up a new drive * To extend a volume into space that's not already part of the volume on the same drive * To shrink a partition, usually so that you can extend a neighboring partition * To change a drive letter or assign a new drive letter {% endhint %}

* Disk Management will appear, right click on **Disk 1**, then click **Online**. You must bring it online before you can initialize it or create volumes on it. The fields in Disk Management include:

Column	Description
Volume	Partition and logical drives are known as volumes
Layout	The type of the volume
Type	The type of Disk
File System	The types of file system. Disk Management only supports 3 types of file system: FAT,FAT32, and NTFS
Status	The status of volume
Capacity	The capacity of each volume in MB or GB
Free Space	The free space of each volume in MB or GB
% Free	The free space of each volume in %
Disk 0	The single physical drive you have in your system
Disk 1	another single physical drive that you just attached

Disk 0 and Disk 1 are physically different hard disk.

* Right click on **Disk 1**, then click **Initialize Disk**. Initialize Disk erases everything on it and prepares it for use by Windows, You need initialize it before using it. You can only initialize a drive that's not yet formatted.

* Disk Management prompts you to select a partition scheme for the new disk. Select **GPT** and click OK. {% hint style="info" %} Disk can be divided up into multiple chunks called partition. Each partition has to have a partition style, GPT or MBR. Windows uses the partition style to understand how to access the data on the disk. {% endhint %}

Column	Description
GPT (GUID Partition Table)	The newer GPT partition table style is required on your boot drive by newer computers that use UEFI instead of BIOS. GPT is more robust and allows for volumes bigger than 2TB, and also GPT supports up to 128 partitions on the same hard drive
MBR (Master Boot Record)	Old format partition that is used by 32-bit PCs, older PCs, and removable drives such as memory cards. One of these limitations is that MBR only supports up to 4 primary partitions, the next limitation is that partitions using the MBR format have a maximum size of 2TB

* After the disk is initialized, right-click the **Unallocated Disk Space** and select *New Simple Volume*.

* Follow the instructions in the New Simple Volume Wizard to configure a new volume.

* In the Specify Volume Size pop-up, click the **Next** button. The field in Specify Volume Size include:

Column	Description
Maximum disk space in MB	The maximum size you can use.
Minimum disk space in MB	The minimum size you can use
Simple volume size in MB	Specify the volume size as needed.

New Simple Volume Wizard - Specify Volume Size

* Then on **Assign Drive Letter or Path**, select **Assign the following drive letter**, then click **Next**. {% hint style="info" %} The field in Assign Drive Letter or Path include: * Assign the following drive letter, this option if you want assign the volume to a drive letter. * Mount in the following empty NTFS folder, you can mount (make a drive accessible) in a folder rather than a drive letter if you want. This makes the drive appear as just another folder. You can mount drives only in empty folders on NTFS volumes. * Do not assign a drive letter or drive path, You can choose this option if you don't want to assign a drive letter or drive path. {% endhint %}

New Simple Volume Wizard - Assign Drive Letter or Path

* Next is Format Partition, select **Format this volume** with the following settings, you can use any partition format you like, but for this example choose **NTFS**. Also, click the **checklist** on Perform a quick format to speed up the process. Then click **next**.

New Simple Volume Wizard - Format Partition

* The last step is to click **Finish.**

* After you have completed the format wizard and volume, check the Status column in the list of mounted disks to make sure that the new disk has a **Healthy**. Now the disk is ready to use.

# Formating & mounting a disk on Linux * On your Linux VM, to do this we need to be the root user and run the following command: **fdisk -l**, as we can see the new hard drive, 10GB, is assigned to the path **/dev/vdb**.

* After the new hard disk has been identified, the next step is partitioning, for this, we will use the following syntax: ```linux fdisk /dev/vdb ``` {% hint style="info" %} Common fdisk parameter are: * n: Create a new partition. * P: Print the partition table. * d: Remove a partition. * q: It leaves without saving the change. * w: Save the changes and exit the command. With this in mind we will perform the following process once the **fdisk /dev/vdb** command has been executed: Enter the letter n to create the new partition. - Enter the letter p to define as a primary partition - Number 1 to establish a single partition of the new disk. - Establish the value of the first sector which is 2048 by default. - Establish the value of the last sector which is 20971519. - Save the changes using the letter w. {% endhint %}

* We can see that the process is executed correctly. If we run **fdisk -l** we can look at the changes in the new disk (/dev/vdb).

* Next step is to format the new hard drive with the desired file system using the command ```linux mkfs.ext4 /dev/vdb1 ``` {% hint style="info" %} **mkfs** is make file system {% endhint %}

* After that we need to create a new directory, in this tutorial we create a new directory called /data: ```linux mkdir /data ```

* The Next step is to mount the new disk in the desired location, in this tutorial we have created a new directory called /data. use command ```linux mount /dev/vdb1/ /data ```

* If we want that partition to be mounted permanently, it will be necessary to edit the file /etc/fstab using the preferred editor and to enter the following line. We keep the change. ```linux /dev/vdb1 /data ext4 default 0 0 ```

* After that, use **df -h** command to see mounted hard drive.

# Increase Storage You can increase the size of your storage disk when your VM instance requires additional storage space. But, You can only resize a storage disk to increase its size, you cannot decrease the size of storage disk. You need to detach the storage from your VM before you Increase the storage. * Open the **Storage** page, by selecting the **Storage** menu.

* In the **Action** column, click **More** then select **Detach from Instance**.

* Click the **Confirm** button to start the detach storage process.

* There will be a notification if the detach storage process is successful **"storage has been successfully detached"**.

* On the **Storage** page in the **Action** column, click **More** then select **Increase Size**.

* Select the desired storage size, minimum size **20GB**. Then click the **Resize Volume** button to continue the resizing process or click **Cancel** if you don't want to change any data.

* There will be a notification if the resizing process is successful **"storage has been successfully increased"**.

* On the **Storage** page in the **Action** column, click **More** then select **Attach to Instance**.

* Select **Instance** then click **Confirm** to continue the process or **Cancel** to return to the Storage page.

* There will be a notification if the attach is successful **"storage has been successfully attached"**.

# Delete Storage Before you delete storage, make sure to *detach* your storage from the instance first. * On the **Storage** page in the **Action** column, click **More** then select **Delete**.

* Click the **Confirm** button to start the process of deleting data storage or **cancel** if you don't want to continue the process.

* If the Storage is successfully deleted, a pop up will appear **"Storage has been successfully deleted".**

# Deka Volume: Images **Deka Volume: Image** is a service available on Cloudeka to do a snapshot for instance or storage, backups, and create custom images.
# Snapshot Snapshot is the state of a system at particular point in time. You can use a snaphot as a point in time backup. You can take a snapshot for instances or storage data disk. # Take a Snapshot for Instance This guide describes how to take a snapshot for an instance. You can take a snapshot while the instance running {% hint style="warning" %} Before doing a snapshot for an Instance, you must have first have an Instance. If you don't have an Instance yet, you can deploy an Instance in [Create VM Instance](/deka_flexi/deka_flexi_compute/create-a-vm-instance). {% endhint %} * Click **Images** menu, then go to **Snapshot** page.

* Fill in the form Take a Snapshot for Instance

Column	Description
Billing Type	Several types of billing are Fixed, Pay Per Use (PPU) according to the payment on your project.
Choose An Instance	Choose an instance that you want take a snapshot, for example techWriter-windows
Enter Snapshot Name	Enter the name of the snapshot, for example techwriter-win-snapshot

After all the fields are filled, click the **Take Snapshot** button.

* A pop-up appears **Take a snapshot** click the **Yes, I Agree** button.

* If it is successful there will be a notification **"Snapshot {snapshot instance name} has been successfully created"**. A list of snapshots instance will appear, namely: \\

Column	Description
Name	Snapshot name
Status	Snapshot state "Active" or "Not Ready Yet"
Instance Name	The name of the instance being snapshot
Size	Snapshot size
Created Date	Snapshot creation time
Action	Option for restore or delete the snapshot

# Restore a snapshot for Instance To restore an instance, you must turn off your instance. * In the **Action** column, select **More** then click **Restore Instance.**

* Select the **instance** you want to restore (eg **"techWriter-windows"**), then click the **Restore Instance** button.

* A pop up will appear to confirm that you want to restore the instance, select **Restore Instance** for restore or **Cancel** if you want to restore.

# Delete a snapshot for Instance * Select the Images menu. The Images page of the Snapshot column will appear.

* In the **Action** column, select **More** then click **Delete**.

* A pop-up will appear to confirm whether you really want to delete the snapshot or not. Click the **Delete** button if you want to delete or **Cancel** to cancel deleting the snapshot.

* There is a notification if the snapshot has been successfully deleted **"Snapshot has been successfully deleted"**.

# Take a snapshot for Storage This guide describe how to take a snapshot for a storage. You can create snapshot a storage even while they are attached to running instances. {% hint style="warning" %} Before doing a snapshot for Storage, you must first have a Storage. If you don't have a Storage yet, you can create a Storage in Create Block Storage {% endhint %} * Go to **Snapshot** page. Under the Take a snapshot for instance form, there is a Take a snapshot for storage form.

* Fill in the form **Take a Snapshot for Storage**.

Column	Description
Billing Type	Billing type option is Fixed or trial
Choose A Storage	Choose storage that you want to take snapshot, for example storage-windows-test
Enter Snapshot Name	Enter the name of the snapshot, for example storage-win-snapshot

After all the fields are filled, click the **Take Snapshot** button.

* If it is successful there will be a notification **"Snapshot win\_snap\_storage has been Successfully Created"**. A list of snapshots storage will appear, namely:

Column	Description
Name	Snapshot name
Status	Snapshot state "active" or "Not Ready Yet"
Storage Name	The name of storage being snapshot
Size	Snapshot size
Created Date	Snapshot creation time
Action	Option for create or delete the snapshot

# Delete a snapshot for Storage * On the **Snapshot** page choose the snapshot storage that you want to delete, in the **action** column click **more**. then click the **Delete** button.

* A pop up will appear to confirm whether you really want to delete the snapshot or not. Click the **Delete** button if you want to delete or **Cancel** to cancel deleting the snapshot.

* There is a notification **"Snapshot has been successfully deleted"**.

# Backups This guide describe how to backup an instance. A backup is an automatic snapshot of your instance. Backup are made once a week and retained for four weeks. Once enabled, backup add 20% to monthly instance cost. {% hint style="info" %} **Please note** : the project has enough storage for daily backups. Volume needed = total vm volume \* (retention day + 1). {% endhint %} {% hint style="warning" %} Before doing a Backup Instance, you must have an Instance first. If you don't have an Instance yet, you can deploy an Instance in Create VM Instance {% endhint %} To backup your instance, follow the steps below: * Click **Images** menu, then go to **Backups** page.

* Fill in the form **Enable Backups**.

Column	Description
Instance	Choose an instance that you want to backup
Backup Time	To determine the time when the backups starts
Duration	To determine the retention time of your backups, the duration options are: - 7 Days - 14 Days - 30 Days - 90 Days - 365 Days
Backup Name	Name of your backups

After all the fields are filled, click the **Enable Backups** button.

* If it is successful there will be a notification **"Instance backup scheduler has been successfully enabled"**. A list of backup scheduler will appear, namely:

Column	Description
Name	The name of your backup
Instance	The instance that you are backing up
Backup Time	The schedule time to backup the instance
Duration	Retention time of your backup
Number of Backup	Total number of your backup
Created At	Backup schedule creation time
Action	Options to delete the backup scheduler, create and restore instance from the backup

# Custom Image Custom images are available only to your Cloud project, you can import your custom images to Cloudeka. Then, use the custom image to create an instance. to create custom image, follow the steps below: * Click **Images** menu, then go to **Custom Image** page, On the Custom Images page click **Import Via URL** button.

* In the **Import an Image via URL** form, fill the form then click **Import**.

Column	Description
Image Name	Name of your image (example custom-test1)
Version Number	Version number of your image
Image URL	URL of your image that you want to import

* Importing custom image will take some time based on the size of your image.

* After importing custom image is successful, there will be a success notification **"custom-test1 has been successfully imported"** and the image status is active.

# Deka Flexi: Network This menu is used to create VPC Network, and assign floating IP. # VPC Network VPC Network (Virtual Private Network) is a virtual version of the physical network architecture implemented in Cloudeka cloud environments. The VPC Network ensures secure traffic between any resource such as Instance, Kubernetes cluster, database cluster, and load balancer. Any resource that you create in a VPC can communicate securely through a private IP Address. In the VPC Network configuration, you can add the Port and Subnet configuration to use. # Create VPC Network This guide explains how to create a VPC Network. VPC Network is also the basis for creating a Virtual Machine, you must create a VPC Network before creating a Virtual Machine. * Go to **Network** page.

* Click **Create VPC** button.

* Select the Wizard Simple tab and Fill in the Create VPC Network form.

Column	Description
Name	Name of VPC Network
Description	Description of VPC Network
Billing Type	- PPU - Fixed
IP Address	Enter Private IP Address also the subnetmask, The Internet Assigned Number Authority (IANA) has assigned several address ranges to be used by private networks. Address ranges to be use by private network are: - Class A: 10.0.0.0 to 10.255.255.255 - Class B: 172.16.0.0 to 172.31.255.255 - Class C: 192.168.0.0 to 192.168.255.255 An IP address within these ranges is therefore considered non-routable, as it is not unique. Any private network that needs to use IP addresses internally can use any address within these ranges without any coordination with IANA or an Internet registry. Addresses within this private address space are only unique within a given private network.
VPC Type	There are two types available on the VPC: a.Simple support services that need to be connected to the internet and have access to resources outside the VPC. b.Isolated is used to fully isolate resources and data from the internet or other resources outside the VPC. VPC type difference is the simple type you can add Floating IP to the network configuration.

* After filling out all the forms in the VPC Network, click **Create VPC Network.**

* There will be a notification if the VPC Network is successfully created **"VPC network has been successfully created".**

# Edit VPC Network You can only edit VPC Network for the **Name** and **Description**, you cannot change the IP Address Configuration. * On the **Network** page, click the **Edit** button.

* You can only change the **Name** and **Description**. For Region, Billing Type, and IP Configuration can not be changed. Then, click the **Save** button.

* There will be a notification if the VPC Network is successfully created **"VPC network has been successfully updated".**

# Add/EditPort You can add ports to a VPC for other instances to use. * On the Network page, select the VPC that you want to add the port to.

* Select the Ports tab and press the Add Port button.

* The Add VPC Port window appears, with three columns that you must fill in.

Column	Description
Name	Port name used. The minimum name length is 5 characters.
IP Address	IP address used. For example, if the IP address on the network that uses a class C IP address is 198.18.1.0/24, then you must fill in the IP Address column with the host address starting from 198.18.1.2 to a maximum of 192.18.1 254.
MAC Address	A unique address used to identify a device. This column is optional to fill in, because when you add a port your port automatically gets a MAC Address.
Port Security	Two options are available: a.Enabled can be directly used by Instances b.Disabled is available in the VPC Port list but cannot be used by the Instance.

* After filling in all the columns, the next step is to press the Add button to continue the process of adding ports to the VPC.

* A notification "VPC port has been successfully added" appears and the port is available in the VPC Port list.

To be able to update the data used by the port on the VPC Details page, press the More button and select Edit.

You can only change the port configuration that has been added to VPC Ports, namely Name and Port Security.

# Delete Port {% hint style="danger" %} Before you delete a port in the VPC, make sure there are no instances using the port you want to delete. {% endhint %} * On the Ports tab on the VPC Details page press the Delete button in the More column.

* Click the Delete button to continue the deletion process.

* The notification "VPC Port has been successfully deleted!" that the port configuration has been successfully deleted.

# Add/Edit Subnet The Cloudeka portal service provides multiple subnet function that can be used to divide VPC network into several distinct subnets without having to change existing subnets. Here are the steps to add to the subnet configuration used in VPC configuration: * On the Network page of the VPC tab, select the VPC configuration to which you want to add a subnet, then click on the configuration Name column.

* Select the Subnets tab and click the Add Subnet key.

* The Add VPC Subnet window displays, fill in the available columns. Click the Add key to add the Subnet configuration.

Column	Desccription
Name	Name of the subnet to be listed.
IP Address	The subnet address to use.
IP Address - Size	Number of IP addresses that can be used on that subnet.

* Wait until the process is complete and the "VPC Subnet has been successfully added".

You can upgrade the saved Subnet configuration at the beginning of VPC creation or by adding the following steps to upgrade the saved Subnet configuration. * Select the subnet configuration for which the data will be updated by pressing the More key and selecting Edit.

* The Edit VPC Subnet window displays, there are several columns that you can update, and you can check "Enable DHCP" if you do not want to enable DHCP functionality.

Column	Description
DNS Name Servers	To add the DNS Server configuration to use.
Host Routes	Used to define subnet routes for traffic to network segments. You can press the add icon to add Host Routes routes.

* The "VPC Subnet has been successfully updated" notice means that the recently updated data has been saved successfully.

# Delete Subnet You can only remove previously added subnets through the Add Subnet button. VPCs that use multiple subnets can be viewed in the Available IP column that has more than one IP address. Here are the steps to remove subnets in the Cloudka portal service: * On the Network page of the VPC tab select the VPC configuration from which to remove the subnet configuration.

* On the Subnets tab, select the subnet configuration to remove by click the More button, and select Delete.

* The Delete VPC Subnet window displays, press the Delete key to continue with the delete process.

* Wait until the process completes and the VPC Subnet notification has been successfully deleted.

# Delete VPC Network {% hint style="danger" %} Before you delete a VPC Network, you need to ensure there are no other instances or services connected to the VPC Network. {% endhint %} * On the **Network** page, click the **Delete** button.

* Click the **Confirm** button to start the process of deleting VPC Network data or **Cancel** if you don't want to continue the process.

* There will be a notification if the VPC Network is successfully deleted **"VPC network has been successfully deleted"**.

# Floating IP Floating IP is a public, static IP Address for instances that provide access from an external network to the instance without public network interface. To be able to use a Floating IP, when creating a VPC using the **Wizard Simple**, in the **VPC Type** section, select **Simple**. # Assign Floating IP If your instance require an external IP address for external access, you can assign a Floating IP by following these steps: * On the **Network** page select the **Floating IP tab**.

* In **Floating IP Type**, there are two Floating IP Types, namely **Reserved** and **Non Reserved**. In the **Non-Reserved** type when you **Reassign Instance** then the IP used will be deleted from the list in the Floating IP, while in the **Reserved** type if you **Reassign Instance** then the IP used will remain on the list in Floating IP so you can use the IP for other instances of your project.

Network Page - Floating IP - Floating IP Type

* On the **Billing Type**, there are two types of Billing Type, i.e **Fixed** and **Trial**.

Network Page - Floating IP - Billing Type

* On the **Resource Type**, there are two types of Resource Type, i.e **Instance** and **Load Balancer**.

Network Page - Floating IP - Resource Type

* If you choose **Instance** on Resource Type, then select the instance that you want to assign Floating IP. After that, click **Assign Floating IP**.

* In the **VPC Port** column, select the VPC used by the Instance and press the **Assign Floating IP** button.

* The Assign Floating IP window appears, press the Yes, I Agree button to continue the process.

* If the Floating IP is succesfully assigned, the Floating IP will be display in Floating IP list.

# Unassign Floating IP If you want to unassign or remove the Floating IP of your instance, please follow these steps. {% hint style="info" %} If you unassign Floating IP from your instance, so your instance doesn’t have external access anymore. However, you can reassign the Floating IP whenever you want. {% endhint %} * If you are already on the **Network** page and on the **Floating IP** tab, select the **Floating IP** in the **Action** column that you want to unassign from your instance. Click **More**, then select **Unassign**.

* If the Floating IP has been successfully unassigned, a pop up will appear **"Floating IP has been successfully unassigned!".**

# Reassign Floating IP You can reassign the Floating IP to the VM on the Instance that was previously created by following these steps: * In the Action column in the Floating IP that will be reassigned the Floating IP, press the More button and select Reassign.

* The Reassign Floating IP window appears, in the IP Address column select the VM and VPC that will add the Floating IP and press the Reassgin button.

* Wait until the process is complete and the notification "Floating IP has been successfully reassigned" appears.

# Delete Floating IP {% hint style="warning" %} Before you delete floating IP, you need to unassign the Floating IP first. You cannot delete it if the Floating IP still in use. {% endhint %} * In the **Action** column, choose **Floating IP** that you want to delete. click **More**, then select **Delete**.

* Click the **Confirm** button to start the process of deleting data Floating IP or **Cancel** if you don't want to continue the process.

* If the Floating IP has been successfully deleted, a pop up will appear **"Floating IP has been successfully deleted".**

# Deka Flexi: Security **Deka Flexi: Security firewall** is a cloud-native and intelligent network firewall security service that provides protection from threats. # Security Firewall Rule Firewall rules allow you to permit or deny connections to or from a virtual machine (vm) based on the configuration you specify. When you create a firewall rule, you define a set of components that determine what the rule does. Components allow you to target specific traffic types, based on traffic protocols, destination ports, sources, and destinations. {% hint style="warning" %} Before creating a Security Firewall Rule, you must first have an Instance. If you don't have an Instance yet, you can deploy an Instance in Create VM Instance {% endhint %} Here are the steps to create a Security Firewall Rule: * On your **Cloudeka Portal**, select the **Security** menu then click the **Create Security** button.

* Fill in the Create Security form:

Column	Description
Name	Name of your security.
Inbound Rule	Define the traffic allowed to the instance on which ports and from which sources.
Outbound Rule	Define the traffic allowed to leave the instance on which ports and to which destinations.

* Click **Delete** button to delete the security. Select **Apply to Instance** (for the instance where Security is created), Click the **Save** button if you want to continue creating the firewall or **Cancel** if you don't want to continue the process.

* There will be a notification if the Firewall has been successfully created **"Firewall has been successfully created"**.

# Edit Security Firewall Rule This guide is used if there is Security Firewall Rule data that you want to change. * On the **Security** page, there are columns Name, Applied to, Rules and Action. In the **action** column, click **Edit**.

* Fill in the data you want to change such as:

Column	Description
Name	The name of firewall rules
Inbound Rule	Define the traffic allowed to the instance on which ports and from which sources
Outbound Rule	Define the traffic allowed to leave the instance on which ports and to which destionations
Protocol type	Supported protocols are: - SSH - HTTP - HTTPS - Custom TCP Rule, you can customize tcp rules and define specific ports according to your needs - Custom UDP Rule, you can cuztomize udp rules and define spesific ports according to your needs - All ICMP Rule
Ether type	Types of IP address, choose IPv4 or IPv6
Port Range	For the custom tcp and udp protocols rule, you can specify: - A single port - A range of ports by entering the starting and ending ports, eg. 3000-4000 - All ports by leaving the field blank
Source	For inbound rules, which lets you restrict the source of incoming connections by entering the individual IP address or entering a CIDR. for example, enter the CIDR 182.23.45.0/24 to a rule that allows incoming traffic from any IP address between 182.23.45.0 and 182.23.45.255. or leave the field blank if you want to allow it from any source.
Destination	For outbound rules, which lets you restrict the destionation of outgoing connections by entering individual IP address or entering CIDR or leave the field blank if you want to allow it to any destination
Apply to Instance	Choose a specific instance to that you want to apply the rule.

* Click the **Save** button if you want to continue changing the firewall data or **cancel** if you don't want to continue the process.

* There will be a notification if the Firewall has been successfully changed **"Firewall has been successfully updated"**.

# Delete Security Firewall Rule This guide is used if there is Security Firewall Rule data that you want to delete. * On the **Security** page, there is columns Name, Applied to, Rules and Action. In the **Action** column, click **Delete**.

* Click the **Destroy** button if you want to continue deleting firewall data or **Cancel** if you don't want to continue the process.

* There will be a notification if the Firewall has been successfully deleted **"Firewall has been successfully deleted"**.

# Deka SLB **Deka SLB** distributes network traffic to across multiple instances to improve service capability and application availability. Cloudeka Load Balancer provides several features, including. * **Multiple protocol Cloudeka** Cloudeka load balancer supports multiple protocols to meet your needs. Currently, several protocols are available: **a. TCP** **b. HTTP** **c. HTTPS** * **Health Check**, to periodically check the state of the backend instance. This will automatically stop sending traffic to the non-responsive instances. * **Certificate Management**, provides certificate management for HTTPS requests to ensure transmission reliability and security. \ In load balance, there are 3 algorithm methods used, including the following.

Column	Description
Roundrobin	It is a load method that is given sequentially from one server to another so that it forms a round.
Least Connection	It is a load method that is given based on the server that has the fewest connections in the lists of servers available.
Source	The method selects the server to use based on the hash of the source IP address from which the user made the request so that in this method ensures that the same user will connect to the same server

Before creating a Load Balancer, you must first have an Instance. If you don't have an Instance yet, you can create an Instance first. For an explanation about creating a [Create VM Instance](/deka_flexi/deka_flexi_compute/create-a-vm-instance#create-instance-from-public-image). # Create Load Balancer You can enjoy a Load Balancer in Cloudka Portal Services, you must create a Load Balancer earlier, following these steps: * On the Cloudeka portal, open the **Network** menu, select **Load Balancer**, and click **Create Load Balancer**.

* The Create Load Balancer page appears in the **Tier** section, select **Server Load Balancer** and fill in the **Name**, **Flavor** and **VPC Network** fields, then click Create Load Balancer.

Column	Description
Name	Your name load balancer.
Flavor	There are 3 size options that can be used including: c1.medium.rc 2VCPU / 2GB RAM c1.large.rc4VCPU / 4GB RAM c1.xlarge.rc8VCPU / 8GB RAM
VPC Network	The VPC network must be in the same segment as the instance to be load-balancing.

Column

Description

Name

Your name load balancer.

Flavor

There are 3 size options that can be used including:

c1.medium.rc 2VCPU / 2GB RAM
c1.large.rc4VCPU / 4GB RAM
c1.xlarge.rc8VCPU / 8GB RAM

VPC Network

The VPC network must be in the same segment as the instance to be load-balancing.

* The notification **Creating the Load Balancer** will appear and the Status column will show **ON-PROGRESS**.

* If the load balancer is successfully created, a notification will appear **Load balancer \[nama load balancer] has successfully created**.

Notification - Load Balancer has successfully created

# Configuration Deka SLB After creating Deka SLB, for the next steps, add backend configuration and frontend configuration. On the Load Balancer page, press the Configuration button.

The Load Balancer Configuration page will appear, displaying three tabs.

There are three tabs available on the Load Balancer Configuration page, namely the General tab, Backend tab, and Frontend tab. This section explains some configurations that can be performed. 1. **Add Configuration**, for further details, you can follow the steps in subsections [Add Backend Configuration](#add-backend-configuration) and [Add Frontend Configuration](#add-frontend-configuration). 2. **Edit Configuration**, for further details, you can follow the steps in subsections [Edit Configuration Backend](#edit-backend-configuration) and [Edit Configuration Frontend.](#edit-frontend-configuration) 3. **Delete** **Configuration**, for further details, you can follow the steps in subsections [Delete Configuration](#delete-configuration-backend-frontend). ## **Add Backend Configuration** Here are the steps to add Backend configuration in Deka SLB on the Cloudeka portal service: * Navigate to the Configuration Load Balancer page and click on the Backend tab, then click Create Backend.

* On the Create Backend page, fill in the available form.

Column	Description
Name	Configure the backend with a name adhering to the character restrictions of using only A-Z, a-z, and "_" underscore.
Load Balancer Method	In this column, there are three options available Roundrobin, Least Connection, and Source.
Mode	There are two modes to choose from: HTTP TCP

Column

Description

Name

Configure the backend with a name adhering to the character restrictions of using only A-Z, a-z, and "_" underscore.

Load Balancer Method

In this column, there are three options available Roundrobin, Least Connection, and Source.

Mode

There are two modes to choose from:

HTTP
TCP

If you select the HTTP protocol in the Mode column, the following columns will appear:

Column

Description

Advanced Check

If you choose HTTP in column Mode, click httpchk.

Http Check Method

You will have 2 options:

GET, used to request data to retrieve information..
POST, used to request the creation of new data.

Http Check URI

This column is used to determine whether the server is active or inactive. In this section, type /_health.php

If you choose the TCP protocol in the Mode column, the following columns will appear.

Column

Description

Advanced Check

There are 2 options available:

SSL Hello Check used to ensure that an SSL connection to the backend server can be successfully established.
TCP Check used for checking the availability or health of a TCP connection between two devices or nodes in the network.

After determining the protocol to be used, in the Server section, you can add more than one server if your backend configuration involves multiple VMs or instances. This allows you to configure load balancing for multiple servers, distributing traffic among them based on the chosen algorithm and health check settings.

Column	Description
Servers - Server Name	VM instances that have been deployed to the VPC connected to Deka SLB.
Servers - Server Port	The port that the server will use.
Servers - Max Connection	The maximum number of connections accepted by the server.
Servers - Weight	The load that will be received by the server.

* After filling out all the forms on the Create Backend page, click the Create Backend button.

* A notification will appear "Backend Configuration has successfully created!"

## **Add Frontend Configuration** After you have configured the backend, the next step is to configure the frontend by following these steps: * On the Configuration Load Balancer page click on the Frontend tab, and then click Create Frontend.

* On the Create Frontend page, fill in the available form.

Column	Description
Name	The name of the frontend configuration, and the allowed characters for frontend naming are only A-Z, a-z, and "_" underscore.
Default Backend	Select the previously created backend.

If you want to add a Backend configuration press the Add Backend button.

Column	Description
Backend Name	Backend configuration name.
ACL Name	To define rules that control access or behavior for specific traffic.
Criteria	To determine whether a request should be directed to a specific backend or not. There are 3 options, namely: req.hdr(Host) this criterion checks the value of the Host header in the HTTP request. path_beg this criterion checks whether the URL path of the request starts with a specific value. path_end this criterion checks whether the URL path of the request ends with a specific value.
Value	These criteria are adjusted based on your selection in the Criteria column. req.hdr(Host) as an example www.example.com path_beg for paths starting with “/”. Example: “/example.php” path_end for paths ending with a specific file extension. Example: “.php”
Condition	There are two options: Equal used to check if a value is equal to the value entered in the ACL Column. Not Equal used to check if a value is not equal to the value entered in the ACL column.
Action	There is a Delete button to remove added Backend configurations.

After determining the Backend configuration to be used, there are other columns that need to be filled.

Column

Description

Bind Address

There are 2 options:

Internet
Internal

Mode

There are 3 options:

HTTPS
HTTP
TCP

If you choose HTTPS in the Mode column, the following columns will appear:

Column	Description
Bind Port	By default, it uses port 443.
Certificate File	You can upload the certificate file you possess. If you are usign the Cloudeka Portal Service, namely Deka SSL, you can download the file in the SSL menu under the Manage Module.
Key File	You can upload the key file you possess. If you are using the Cloudeka Portal Service, namely Deka SSL, you can download the file in the SSL menu under the Manage Module.

If the Mode column selects the **HTTP** or **TCP** protocol, the following columns will appear.

Column

Description

Bind Port

Adjusting to the protocol used:

If the HTTP Protocol is selected, it will be automatically filled with port 80.
If the TCP Protocol is selected, specify the port to be used.

* After filling out all the forms on the Create Backend page, click the Create Backend button.

* If the HTTPS load balancer frontend is successfully created, a notification will appear “Frontend Configuration has successfully created!”.

## **Edit Backend Configuration** You can modify the backend configuration you've created by following these steps: * On the Backend tab of the Configuration Load Balancer, select Backend configuration you want to update by clicking the Edit button.

* The Edit Backend page, you can modify the Load Balance Method, Advanced Check, Http Check Method, Http Check URI, and add Servers by click Add Servers. Then click Update Backend.

* A notification will appear Backend Configuration has successfully updated!

## **Edit Frontend Configuration** Here are steps to modify the existing Frontend configuration: * On the Configuration Load Balancer, click on the tab Frontend. Select the frontend configuration you want to update by click the Edit button.

* The Edit Frontend page will appear, you can modify Default Backend, Additional Backend if you want to add another backend, click the Add Backend button, Bind Address, and Bind Port. Then click Update Frontend.

* A notification will appear Frontend Configuration has successfully updated! indicating that the frontend Load Balancer configuration has been successfully modified.

## **Delete Configuration Backend/Frontend** To delete the backend and frontend configuration in the Deka SLB configuration. The initial step is to delete the frontend configuration and then delete the backend configuration. On the **Configuration Load Balancer page**, on the **Frontend** tab, select the **Delete** button.

The **Delete Frontend window** appears, **enter the frontend configuration name** and click the **Confirm** button to continue the configuration deletion process.

Wait until the process is complete and the notification "**Frontend configuration has been successfully deleted**!" appears.

After successfully deleting the frontend configuration, the **next step** is to **delete the backend configuration**. **If you haven't deleted the frontend configuration, a notification will appear "Please detach default backend from frontend configuration!"** On the **Backend** tab, select the **Delete button**.

The **Delete Backend** window appears, **enter the frontend configuration name** and press the **Confirm** button to continue the configuration deletion process.

Wait until the process is complete, and a notification will appear “**Frontend configuration has successfully deleted!**”

# Delete Load Balancer You can delete a Load Balancer that is no longer in use, follow these steps: * On the **Load Balancer** page, select the Load Balancer that you want to delete. In the **Action**, column, click **Delete**,.

* Input **lb-tw3** in the column and click the **Confirm** button to continue with the process.

* A **"Load balancer has been successfully deleted"** notification appears if Load Balancer is successfully removed.

# Example Use Case This section explains an example case of **Deka SLB** configuration using the **Roundrobin** method type with two VM Instances in the Cloudeka portal service. There are several stages that will be carried out in the case of using the Deka SLB configuration on the Cloudeka portal service. ## **VPC Configuration** The first step is to add VPC configuration on the project that will be created by Deka SLB, you can click for further explanation on how to create a VPC [this link ](/deka_flexi/deka-flexi-network/6.1_vpc_network/create-vpc-network)to go to the Create VPC module.

## **VM Configuration** The next step is to **Add two VM in the Instance** using the same VPC, which is **vpc-demo-slb**. For further explanation on how to create a VM, you can press [this link](/deka_flexi/deka_flexi_compute/create-a-vm-instance#create-instance-from-public-image) to go to the Create VM module.

The VM on the instances that have been created are demo-slb1 and demo-slb2, console access on the demo-slb1 and demo-slb2 VMs. Press the More button then select Access Console.

Enter the username and password used to log in to the virtual machine.

Enter the following command to update the package management version that the VM will use. ``` sudo apt-get update ```

Enter the following command to install the Apache HTTPServer package on the VM. ``` sudo apt-get install apache2 ```

Type Y to continue the installation process.

Press Enter to continue the installation process and wait until the process is complete.

After you have finished installing Apache, next, check the status that Apache has been installed, enter the command below. ``` systemctl status apache2 ```

After Apache is running on each VM, the next step is to add a file to the html directory. Later, the file created in this html directory will be added to the Backend configuration in the Load Balancer under the Http Check URI column. Enter the following syntax to access the html directory. ``` cd /var/www/html ```

Enter the following command syntax to create a file in the html directory. ``` sudo nano [name-file].[ekstensi-file] ```

Enter the contents of the file in each VM

To exit the configuration file main.php, on the keyboard press the CTRL key and the X key simultaneously. Press the Y and Enter keys to save the file contents. ## **Deka SLB Configuration** The next step is to add a load balancer configuration using the Server Load Balancer type via the Network menu.

It can be seen that after adding the Deka SLB configuration, the IP address is 109.199.214.217 which will later be added to the Security Firewall. In the SLB configuration, add HTTP configuration to the backend and frontend.

## **Security Configuration** On the Security menu, press the Create Security button, in the Inbound Rule section, press the New Rule button to add the IP address obtained after successfully creating the Deka SLB configuration.

For the Apply to Instance section, add it to the previously created VM.

## Result After completing all the configurations above, check whether the web server is running according to the configuration. Open the browser on your computer, enter the IP address obtained in the load balancer configuration, namely **109.190.214.217** and the name of the file created in the html directory, namely main.php. Enter the following syntax in your browser. ``` 109.190.214.217/main.php ```

# Deka VPN **Deka VPN** allows you to create a secure connection between your device and the Cloudeka Portal service. Before creating a VPN, make sure you first [create a VPC.](/deka_flexi/deka-flexi-network/6.1_vpc_network/create-vpc-network) # Create VPN Here are the steps to create a VPN: * On the Network menu select the VPN tab, click the Create VPN button.

* The Create VPN page appears. Enter a Name and select the VPC Network that will be used then click Create VPN.

* Wait for the VPN creation to complete.

* A notification appears "VPN Pfsense \[VPN name] has been successfully created!" which means the VPN was created successfully.

# OpenVPN Configuration OpenVPN is a virtual private network system used to create secure connections between devices. By using OpenVPN, data transmitted via this connection is encrypted, thereby maintaining the privacy and security of the information sent. # Create OpenVPN To create OpenVPN you will fill in several available columns including the following:

Column	Description
Username	The username that will be used to identify the user when connecting to the OpenVPN server.
Password	The password that the user will use to authenticate when connecting to the OpenVPN server.
Confirm Password	Confirm the password that has been entered.
Tunnel Settings - Protocol	The protocol that will be used in VPN connections is currently the UDP On IPV4 only protocol.
Tunnel Settings - Ports	The port number that will be used by the OpenVPN server is automatically filled in using port 1194.
Tunnel Settings - OpenVPN Client Network	The virtual network that users will use when connecting to an OpenVPN server.

Here are the steps to create OpenVPN: On the VPN page, in the More column, select Configuration.

* Select the OpenVPN tab, and click the Create OpenVPN button.

* The Create OpenVPN page appears, in the Create User OpenVPN section, fill in the Username, Password, Confirm Password, and Expiration Date.

* In the Tunnel Settings section, fill in the Protocol, Port, and OpenVPN Client Network sections.

* Click the Create button after filling in all the columns on the OpenVPN Create User page.

* Wait until the process is complete.

* The notification "OpenVPN configuration vpn-for-tw has been successfully created" appears and the status changes to Created.

# Add OpenVPN User On OpenVPN on the Cloudeka portal service, you can add users by following these steps: * On the VPN page, in the More column, select Configuration.

* Select the OpenVPN tab in the OpenVPN User section, click the Add New User button.

* The OpenVPN Create User page appears, fill in Username, Password, Confirm Password, Expiration Date, and click the Create button to continue the process.

* New OpenVPN user accounts are now available in the OpenVPN User list.

# Edit OpenVPN User Configuration In the OpenVPN configuration on the Cloudeka portal service, you can update the password and change the validity period of the OpenVPN user account. Here are the steps to update your password: * On the OpenVPN page, in the OpenVPN User section, select Reset Password in the More column.

Edit OpenVPN User Configuration - Reset Password

* The Edit Password page appears, fill in the Password column, Confirm Password, and click Update to continue the process.

* A notification "OpenVPN user has been successfully updated" appears.

Here are the steps to change the validity period of an OpenVPN user account by following these steps: * On the OpenVPN page, in the OpenVPN User section, select Edit Expiration Date in the More column.

Edit OpenVPN User Configuration - Expired Date

* The Edit Expiration Date page appears, select the new validity period and click Update to continue the process.

* A notification "OpenVPN user has been successfully updated" appears.

# Download OpenVPN Cloudeka Portal Service provides installers for Windows and MacOS operating systems. Here are the steps to download OpenVPN on the Cloudeka Portal service: * On the Network tab VPN menu, press the More button and press the Configuration button.

* On the OpenVPN tab in the Client Export section:\ a. Download the OpenVPN installer with the Windows operating system.\ b. Download the OpenVPN installer with the MacOS operating system.

* Wait for the installer to finish downloading.

# Install OpenVPN on Windows Here are the steps for installing OpenVPN on Windows: * Run the downloaded OpenVPN for Windows installer by double-clicking.

* Press the Run button to continue the process of installing OpenVPN on your computer.

* Press the Installer Now button.

* Wait until the process is complete.

* Click the Close button. OpenVPN can now be run on your computer.

# Install OpenVPN on MacOS Here are the steps for installing OpenVPN on Windows: * Run the downloaded OpenVPN for MacOS installer.

* The Install OpenVPN Connect page appears, press the Continue button.

* Read the EULA and press the Continue button to continue the installation process.

* In Installation Type, press Install.

* Wait until the process is complete.

* Open the OpenVPN client application that you just installed in OpenVPN on your computer. Press the Agree and OK buttons. OpenVPN can now be run on your computer

# Connection with OpenVPN Here are the steps to connect to the VPN configuration on OpenVPN: * In the Action column, click the More button then select Configuration.

* To download the VPN configuration, select the OpenVPN tab, click Viscosity Inline Config and wait until the download process is complete until the notification Viscosity Inline config has been successfully downloaded appears.

* Run OpenVPN on the computer.

* On the taskbar in the right corner of the screen, click the openVPN icon, then right click and click Import File...

* Select the downloaded Viscosity Inline Config file and click Open.

* On the taskbar in the right corner of the screen, click the openVPN icon then click Connect.

* Enter the username and password you entered when you created OpenVPN and click OK to continue the process.

* If the username and password entered are correct, the notification viscosity-config-vpn-1-openvpn-byCloudeka is now connected will appear. You can see the IP used is 18.18.18.2

* To see the running status of OpenVPN, you can see the OpenVPN page

* The OpenVPN Status section displays several columns

Column	Description
Username	Username used to identify the connection to the OpenVPN server.
Real Address	The physical IP address that is connected to the OpenVPN server.
Virtual Address	A virtual IP address is used to communicate with other networks.
Connected Since	Displays the date and time when the user connected to the OpenVPN server.
Bytes Sent	Displays the total number of bytes a user has sent through an OpenVPN connection since connecting.
Bytes Received	Displays the total number of bytes that have been received by the user via the OpenVPN connection since connecting.
Ciphers	Displays the encryption algorithm used to protect data sent over an OpenVPN connection.

* In the OpenVPN Status section you can see that there is only one total connected client. The VPN username is the second test which is currently active using the real address 103.168.135.139, virtual IP address 18.18.18.2 which has been connected since May 31, 2023 at 04:32:05. The bytes that have been sent are 2896 while the bytes that have been received are 8221. Cipher is the encryption method used by AES-256-GCM (Advanced Encryption Standard 256-bit Galois/Counter Mode). \ The Routing Table list displays the name of the second test user with the original address and target network address used 103.168.135.139, and the last time used was May 31 2023 at 04:32:05.

* On the Cloudeka portal service, select the Security menu and click the Edit button in the Action column.

* Click the New Rule button.

* In the Type column select SSH.

* In the Sources column, enter the network address used when creating the VPN.

* Click the Save button to save changes

* Select the Instance menu, click See all IP Address to see the IP address used by the virtual machine that will be accessed. Make sure the VPC used is the same as the VPC used when creating the VPN.

* Test the connection from your computer to the virtual machine in the portal service by typing Ping 10.10.10.252. Produces a response within 13 milliseconds, and a Time To Live value of 62 which indicates the maximum number of network hops permitted on a packet.

To disconnect OpenVPN, on the taskbar in the right corner of the screen, click the OpenVPN icon then click Disconnect.

On the Cloudeka portal service page in OpenVPN status the OpenVPN connection is no longer active.

# Delete OpenVPN User Following are the steps to delete an OpenVPN user account on the Cloudeka portal service: * On the VPN page, in the More column, select Configuration.

* Select the OpenVPN tab, in the OpenVPN User section select the Delete button.

* Press the Confirm button to continue the OpenVPN User deletion process.

* A notification "OpenVPN user has been successfully deleted" appears.

--- [Next Page](/llms-full.txt/1)