Cloud Computing Service (C2S)

EPAM C2S is a core EPAM Cloud service providing cloud infrastructure and related resources as a high scale, multi-tenant private IaaS service. EPAM Cloud operates on the self-service basis with users deploying operating system images and running their applications as needed.

EPAM C2S features the industry's most advanced identity and permission scheme and distributed firewall to keep customers' workloads protected inside EPAM Cloud.

Have a Question?

The current page gives the general information on the service and the main workflows. However, while working with the services, our users encounter new questions they need assistance with. The most frequently asked questions on EPAM Cloud Services are gathered on the Cloud Services FAQ page.
Visit the page to check whether we have a ready answer for your question.

Elastic, Self-Service, Multi-Tenant Public IaaS Service

EPAM Cloud is your platform for creating virtual environments. Run virtual machines, deploy platform services, explore hybrid opportunities - all within the secure perimeter of EPAM Cloud private regions and the leading cloud providers - AWS, Microsoft Azure, and Google Cloud Platform.

Please note, that the new OpenStack regions have SSD disks available by the same price as the HDD ones. The ESX regions do not support SSD.

EPAM Cloud allows to run instances, based on three operating systems, each accompanied by a default system storage disk:

Base OS Default Storage
Windows 100 GB
Linux 40 GB
Mac (Virtual) 60 GB
Mac (Hardware) 300 GB

You can find the details on instances creation, available images, and other basic information on the service further on this page.

Please see below for the available regions, virtual machine configurations, supported images, and the basic pricing concepts.

This page is oriented on EPAM cloud general approaches. You can find the specifics of external cloud usage on the Hybrid Cloud page and in the respective document.

Specifics of EPAM Cloud Regions

EPAM Cloud regions have different geographical locations and are based on different virtualization types. For some regions, the virtualization type defines certain special features and limitations.


EPAM-MAC region is designed to enable Mac resources provisioning. No other instance types can be created here. The region hosts two types of instances - virtual and hardware, each having its own specifics.

Virtual. Virtual MacOS instances have a choice between MacOS 10.10 Yosemite, MacOS 10.11 El Capitan or MacOS 10.12 Sierra operating systems. The instance details are:

  • - Image name: MacOS_10.10_Yosemite, MacOS_10.11_EL_Capitan, MacOS_10.12_Sierra
  • - Shape: Any standard EPAM Cloud shape (recommended - MEDIUM)
  • - System Disk: 60GB
  • - Billing: Same as in EPAM-BY1 region
  • - Login: via VNC console with EPAM credentials
  • - Limitations: auto configuration service and checkpoints are not available

Hardware. The other type of resources that can be provided in EPAM-MAC region, are reusable hardware Macmini (OS X 10.12.x; OS X 10.15.x) servers that can be provided for project needs. The specifics of this kind of resources are:

  • - Image name: macmini_os_X
  • - Shape: Large (2CPU, 8GB RAM) only
  • - System Disk: 300GB, not extendable
  • - Billing: $30/Month, calculated hourly at 30/730.5 USD per hour
  • - Login: via VNC console with user/user credentials (we strongly recommend changing the default credentials after the first login)
  • - Instance operations are strictly limited: only or2run, or2kill, or2report, or2settag, or2din commands are available
  • - Limited number of available servers. To check whether there are Macmini instances available, use the or2vps command

OpenStack-Based Regions:


  • - EPAM-BY2 is the region where personal projects can be created (for more details, see the Account Management Guide)
  • - The Recycle Bin functionality is supported. This functionality allows restoring a terminated VM within 7 days after termination by sending a request to
  • - Shapes up to 3XL are supported
  • - Custom image can be created only from instances with no additional volumes


  • - Storage volumes are billed by provisioned, not by used, space
  • - Shapes up to 5XL are supported
  • - Graceful shutdown functionality is not available. The or2stop command acts as power-off
  • - The commands from other groups (as listed in Maestro CLI Reference Guide) are mostly available, but some are disabled.
  • - Viewing instance pool scope is not supported

Network specifics in OpenStack-based regions

  • All instances in project have IPs from internal net (
  • All instances have an assigned floating IP from EPAM network (10.6.)
  • All instances have hostname like, which can be resolved as an IP from EPAM network (for example,
  • If you try to resolve native hostname from instance in OpenStack you will get external IP, which does not belong to any network interface of instance

This can cause issues when you try to bind some process to hostname instead of instance IP.


EPAM Cloud Orchestrator is integrated with the Enterprise Cloud and supports EPAM-ENT region. Using the region differs from other regions supported in EPAM Cloud and has the following specifics:

  • The resources cannot be created and managed in terms of self-service. To order a virtual instance in the EPAM-ENT region, please address the Enterprise Admins team.
  • Using EPAM Cloud toolset (EPAM Cloud Management Console and Maestro CLI), you can review the existing resources, see their details, billing, and events audit.
  • The billing information is provided as given based on the data obtained from the Enterprise Cloud data source. Billing data is updated once a day.
  • Resource and billing quotas are not applied in EPAM-ENT region.

Requesting a Virtual Machine

If you are a member of a project activated in EPAM Cloud, you can use Cloud resources for your project purposes. By running a virtual machine of the selected configuration you will access the Cloud capacities and services corresponding to your project requirements.

While requesting a virtual machine, you have to consider the following basic parameters which will determine your machine performance and cost:

  • - Virtual machine shape determined by the number of vCPUs and the RAM volume
  • - Virtual machine image defining the operating system to be used. The available options are Windows, Linux and MacOS, with MacOS supporting hardware instances as well

The images and shapes available in EPAM Cloud are described below. Once you have selected the virtual machine configuration, use the Run Wizard on the Cloud Management Console or run the following command in Maestro CLI:

or2run -p project -r region -i image -s shape

By default, each C2S instance includes 100 GB Storage Volume for Windows Instances and 40 GB Storage Volume for Linux Instances by default. If your needs are above that, you can attach additional storage volumes, as described in Maestro CLI User Guide.

Existing Shape Sizes

Each virtual machine is created with a certain shape defining its capacity. The shape is determined by the number of vCPUs and the RAM memory volume. Instance shape is one of the factors influencing the cost of your virtual machine.

By default, the largest shape that can be activated in EPAM private regions in terms of self-service is Large (2 CPU and 8GB RAM). If you need more RAM for your instance, please submit a corresponding support request, or select the AWS-type region where these shapes are available by default. (see Maestro User Guide for details).

Below is the list of available shape sizes.

EPAM Cloud Shape CPU RAM, GB AWS Instance Type Microsoft Azure Instance Size Google Cloud Instance Type
MICRO 1 0.5 t3.nano A0 MICRO
MINI 1 1 t3.micro - MINI
SMALL 1 2 t3.small A1 SMALL
MEDIUM 2 4 t3.medium A2 MEDIUM
LARGE 2 8 t3.large A3 LARGE
XL 4 7.5 m5.large, m5a.large - -
2XL 4 16 r5.large, r5a.large - -
3XL 8 15 m5.xlarge, m5a.xlarge - -
4XL 6 23 r5.xlarge, r5a.xlarge - -
5XL 8 32 m5.2xlarge, m5a.2xlarge - -
5cXL 14 32 - - -
6XL 8 46 r5.2xlarge, r5a.2xlarge - -
7XL 8 61 m5.4xlarge, m5a.4xlarge - -
8XL 16 92 r5.4xlarge, r5a.4xlarge - -

For some shape, the AWS instance type selection depends on the region.

Instance types for which mapping is not available can be requested directly via the native cloud provider tools.

For OpenStack regions, the shape parameter also includes the disk type (SSD) and the possible custom flavors (the system disk size: 100, 200, 300, 500 GB). In case these parameters should be set, they are given as shapeName.diskType.flavor (for example: MEDIUM.SSD.300)

Windows Images

All Windows systems are available in Enterprise edition and Active Directory log-in type.

Below is given the list of Public Machine Images with Windows OS, and their availability in different types of regions and supported external cloud providers.

Image Description Alias/Image Name Private OpenStack AWS Azure Google
Windows 10 64-bit Enterprise* Win10-64 + - + -
Windows Server 2012 R2 Datacenter Edition W2012R2DC - - - +
Windows Server 2016 Standard W2016Std + + + +
Windows Server 2016 Datacenter Edition W20162DC - - - +
Windows Server Core 2019 Standard W2019CoreStd + - + +
Windows Server 2019 Standard W2019Std + - + +
Windows Server 2012 R2 Standard Edition W2012Std + + + +
Windows Server 2012 Standard Edition W2012R2Std - - + -
Microsoft Windows 2019 Datacenter edition with Containers W2019CoreStd - + - -
Microsoft Windows 2019 Datacenter edition W2019Std - + - -

Please note: Windows aliases in AWS, Azure and Google have descriptions other than those in private regions. The general approach is given in the table. However, the set of provided images can alter in specific regions.

Linux Images

Logging in to Linux instances if done using SSH and/or the standard domain credentials.

Below is given the list of Public Machine Images with Linux OS, and their availability in different types of regions and supported external cloud providers.

Image Description Alias/Image Name Private OpenStack AWS Azure Google
CentOS Linux 7 64-bit recommended by EPAM security CentOS7-se_64-bit + - - -
CentOS Linux 7 64-bit CentOS7_64-bit + + + +
CentOS Linux 8 64-bit CentOS8_64-bit + - + +
Oracle Linux 7 64-bit OracleLinux7_64-bit + - - -
Oracle Linux 8 64-bit OracleLinux 8_64-bit + - - -
Red Hat Enterprise Linux 7 64-bit RHEL7_64-bit - + + +
Red Hat Enterprise Linux 8 64-bit RHEL8_64-bit - + + +
Debian GNU/Linux 10 64-bit Debian 10_64-bit + - + -
Ubuntu 18.04 64-bit LTS Ubuntu18.04_64-bit + + + +
Ubuntu 20.04 64-bit LTS Ubuntu20.04_64-bit + + + +
FedoraCoreOS_64-bit CoreOS_64-bit + + + +
Amazone Linux 2 LTS Amazon_Linux + + - -

MacOS Images

EPAM Cloud supports two virtual MacOS images and two hardware MacOS images. Virtual MacOS systems are accessible with EPAM user credentials (without, and hardware MacOS systems - with the default "user/user" login/password that should be changed at first system start.

Below is the list of Public Machine Images with MacOS.

Image Description Alias/Image Name Type
MacOS 10.12 Sierra MacOS_10.12_Sierra Virtual
MacOS 10.13 HighSierra MacOS_10.13_HighSierra Virtual
MacOS 10.15.x Catalina macmini_OS_X Hardware
OS X of current or release version macmini_OS_X Hardware

MacOS 10.12 Sierra and MacOS 10.13 HighSierra can be updated to MacOS 10.14 Mojave.

MacOS instances are run in the dedicated EPAM-MAC region physically located in Minsk and Saint Petersburg. By default, in EPAM-MAC (Minsk) location hardware Macmini servers are run with OS X 10.15.x, while in EPAM-MAC (Saint Petersburg) with OS X 10.12.x. Virtual MacOS instances are billed at the level of EPAM-BY2 region, while hardware MacOS machines are billed at a fixed charge of $30 per month, calculated on the hourly basis (30/730.5 USD per hour). The cost of a hardware MacOS is calculated by multiplying the hourly price by the number of hours the machine was actually used.

Retrieving Available Images in CLI

You can retrieve the list of the images available for the specified project using or2-describe-images CLI command.

The command returns information about images. If you specify one or more image IDs, Orchestrator returns information for those images. If you do not specify image IDs, Orchestrator returns information for all relevant images according to your access rights.

The command response gives the the list of the available images, according to your permissions, their descriptions, group type, size and state.

Dedicated Instances

EPAM Cloud supports a solution based on dedicated instances concept, that allows to add hardware resources under Orchestrator control. This means that after a hardware server is registered in Cloud, its billing and events information becomes available via Orchestration.

Hardware server registration in Cloud is initiated by a user's request to DEV SRV team, responsible for hardware support in Cloud.

Dedicated instances related to hardware resources are assigned to the hardware region, EPAM-HW1, and this region name should be used in commands used to address the dedicated servers. Billing of hardware servers depends on their location.

After a hardware server is registered in Cloud, the user can retrieve the following server-related information:

  • Hardware resources list: to get the information on all the hardware servers registered for your project, run the or2din command with -r EPAM-HW1 region:

    or2din -p project -r EPAM-HW1

  • Hardware resource billing: to get the information on your hardware servers cost, run the or2report command with -r EPAM-HW1 region:

    or2report -p project -r EPAM-HW1 -y 2015 -m 06

  • Hardware resource audit: to get the information on the hardware-related events, run the or2audit command with -r EPAM-HW1 region and -g HARDWARE flag:

    or2audit -p project -r EPAM-HW1 -g HARDWARE

The information on dedicated instances is also available on Cloud Management Console, same as the information on any other instance in Cloud:


In EPAM Cloud, pricing depends on platforms and providers you use to host your virtual resources.

Billing in EPAM Regions

The described billing policy is applied since August 1, 2018. For the details of the previous policy, please see Annex C in the Account Management Guide.

The basic cost of Cloud resources hosted in EPAM regions is defined by the used CPU, RAM and hard disk space, as well as the license fee for Windows VMs. Additional chargeback can be applied for creating checkpoints and custom machine images.

Although the hourly price by which the virtual resources are billed is the same in each region, the final cost for identic VMs in OpenStack and ESX-based regions can vary. This is cosed by the difference in costs calculations. In ESX regions, the billing is calculated hourly, while in OpenStack ones, per-second billing is applied.

In both cases, the hourly/secondly price is derived from the monthly price for each element, with calculations based on average 730.5 hours per month.

The table below provides the virtualization types of different regions, and their billing approaches:

Location Service Region Virtualization type Billing Approach
Europe (Budapest, Hungary) EPAM-HU2 OpenStack Per-hour
CIS (Minsk, Belarus) EPAM-BY1 ESX Per-hour
CIS (Minsk, Belarus) EPAM-BY2 OpenStack Per-second
CIS (St. Petersburg, Russia) EPAM-RU2 ESX Per-hour
CIS (St. Petersburg, Russia) EPAM-RU3 OpenStack Per-second
USA (Edison, NJ) EPAM-US2 OpenStack Per-second
Europe (Kiyiv, Ukraine) EPAM-UA1 ESX Per-hour
Europe (Kiyiv, Ukraine) EPAM-UA2 OpenStack Per-second
CIS (Minsk, Belarus) EPAM-MAC ESX Per-hour
Asia (Hyderabad, India) EPAM-IN1 OpenStack Per-second

Please note that although billing in EPAM Cloud is unified, some services may be subject to a specific pricing policy. In such cases the respective information is given in the service desctiption.

For more details on EPAM Cloud billing model, please, see our Account Management Guide and the Billing and Quotas page.

Billing in External Clouds

EPAM Orchestrator provids access to external Cloud Providers (AWS, Azure, Google Cloud),without adding any extra fees to their costs. It means, that all the bills for external cloud usage are passed to the users "as is", and include only costs for the used infrastructures.

For more details on the biling and reporting specifics for each supported cloud provider, please see the Maestro User Guide