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.
This topic contains the following sections:
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.
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.
/cloud_map.png)
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.
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:
/VM_configuration.png)
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 1000 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.
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.
Below is the list of available shape sizes.
Please, note that the maximum RAM size available throughout self-service for EPAM service regions is 15GB. If you need more RAM for your instance, please, use AWS-type regions (see Hybrid Cloud guide for details)
| EPAM Cloud Shape | CPU | RAM, GB | AWS Instance Type | Microsoft Azure Instance Size | Google Cloud Instance Type |
| MICRO | 1 | 0.5 | t2.nano, t1.micro* | A0 | MICRO |
| MINI | 1 | 1 | t2.micro | - | MINI |
| SMALL | 1 | 2 | t2.small, m1.small* | A1 | SMALL |
| MEDIUM | 2 | 4 | t2.medium, c3.large* | A2 | MEDIUM |
| LARGE | 2 | 8 | t2.large, m1.large* | A3 | LARGE |
| XL | 4 | 7.5 | c4.xlarge, c3.xlarge* | - | - |
| 2XL | 4 | 16 | m4.xlarge, m3.xlarge* | - | - |
| 3XL | 8 | 15 | c4.2xlarge, c3.2xlarge* | - | - |
| 4XL | - | - | - | - | - |
| 5XL | 8 | 32 | m4.2xlarge, m3.2xlarge* | - | - |
| 6XL | - | - | - | - | - |
| 7XL | 8 | 61 | r4.2xlarge, m2.4xlarge* | - | - |
| 8XL | 16 | 122 | r4.4xlarge | - | - |
*Instance types used for PV-based custom instances (the default virtualization type for AWS is HVM).
Instance types for which mapping is not available can be requested directly via the native cloud provider tools.
SSD Storage Support
The EPAM-BY2 region supports selection of the storage type (HDD or SSD) during virtual machine creation. For that purpose, the region offers two sets of VM shapes determining whether the VM will have HDD or SSD storage. The shape name will include the .SSD or .HDD indicator appended to its name to show that the VM started with that shape will have the storage of SSD or HDD type.
/ssd_shapes.png)
As soon as your project is activated in the EPAM-BY2 region, both standard and SSD shapes will be available for it. If you request additional shapes for your project, both standard and SSD shapes of the same size will be activated.
The usual shape notations (e.g. MEDIUM, LARGE, etc.) are also supported. When an instance is requested with such shape name, the default storage for the region is used (HDD or SSD). The response to the or2run command will indicate the default storage type.
Currently, SSD storage is set as default for the EPAM-BY2 region.
All Windows systems are available in Enterprise edition and use Active Directory log-in type.
Below is given the list of Public Machine Images with Windows OS.
| Title | Activation time | Auto-Configuration |
| Windows 7 32-bit Enterprise | 25 min | epconfig, epchef, Chef-Client |
| Windows 7 64-bit Enterprise | 25 min | epconfig, epchef, Chef-Client |
| Windows 8 32-bit Enterprise | 25 min | epconfig, epchef, Chef-Client |
| Windows 8 64-bit Enterprise | 25 min | epconfig, epchef, Chef-Client |
| Windows Server 2008 R2 Standard Edition 32-bit | 25 min | epconfig, epchef, Chef-Client |
| Windows Server 2008 R2 Standard Edition 64-bit | 25 min | epconfig, epchef, Chef-Client |
| Windows Server 2012 R2 Standard Edition | 25 min | epconfig, epchef, Chef-Client |
| Windows Server 2012 Standard Edition | 25 min | epconfig, epchef, Chef-Client |
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.
| Title | Activation time | Auto-Configuration |
| Linux CentOS 5.9 64-bit | 10 min | epconfig, epchef, Chef-Client |
| Linux CentOS 6.4 32-bit | 10 min | epconfig, epchef, Chef-Client |
| Linux CentOS 6.4 64-bit | 10 min | epconfig, epchef, Chef-Client |
| Oracle Linux 6 64-bit | 10 min | epconfig, epchef, Chef-Client |
| Ubuntu 10.04 32-bit | 10 min | epconfig, epchef, Chef-Client |
| Ubuntu 10.04 64-bit | 10 min | epconfig, epchef, Chef-Client |
| Ubuntu 12.04 64-bit | 10 min | epconfig, epchef, Chef-Client |
| Ubuntu 14.04 64-bit | 10 min | epconfig, epchef, Chef-Client |
| Ubuntu 16.04 64-bit | 10 min | epconfig, epchef, Chef-Client |
EPAM Cloud supports three virtual MacOS images and one hardware MacOS image. Virtual MacOS systems are accessible with EPAM user credentials (without @epam.com), 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.
| Title | Activation time | Auto-Configuration |
| MacOS_10.10_Yosemite (virtual) | 30 min | N/A |
| MacOS_10.11_EL_Capitan (virtual) | 30 min | N/A |
| MacOS_10.12_Sierra (virtual) | 30 min | N/A |
| macmini_os_X (hardware) | 10 min | N/A |
Hardware MacOS machines are created with MacOS_10.12_Sierra operating system.
MacOS instances are run in the dedicated EPAM-MAC region physically located in Minsk. Virtual MacOS instances are billed at the level of EPAM-BY1 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. For the specifics of EPAM-MAC region and the virtual machines hosted in it see Orchestrator ver. 2.1.63, What's New.
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.
/or2dim_screenshot.png)
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:
or2din -p project -r EPAM-HW1
or2report -p project -r EPAM-HW1 -y 2015 -m 06
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:
/hw_on_ui.png)
In EPAM Cloud, pricing depends on platforms and providers you use to host your virtual resources.
Billing in EPAM Regions
The basic cost of Cloud resources hosted in EPAM regions is defined by the used CPU, RAM and HDD, as well a by the Soft and Labour needed to support the service and one-time instance launch fee.
The other important thing that influences the cost is the virtualization region itself. Each Virtualization region has its own coefficient by which the basic VM cost is multiplied to get the final cost of the VM. This means, that two VMs with same characteristics can have different costs in different regions. The table below provides the coefficients of different regions
| Location | Service Region | Coefficient |
| Europe (Budapest, Hungary) | EPAM-HU1 | 1 |
| CIS (Minsk, Belarus) | EPAM-BY1 | 1 |
| CIS (Minsk, Belarus) | EPAM-BY2 | 0.8 |
| CIS (St. Petersburg, Russia) | EPAM-RU2 | 1 |
| USA (Edison, NJ) | EPAM-US2 | 0.6 |
| Europe (Kiyiv, Ukraine) | EPAM-UA1 | 1 |
| CIS (Minsk, Belarus) | EPAM-MSQ3 | 0.8 |
| CIS (Minsk, Belarus) | EPAM-MAC | 1 |
| CIS (Minsk, Belarus) | EPAM-DKR | -* |
| Asia (Hyderabad, India) | EPAM-IN1 | 1 |
*VMs in the EPAM-DKR region are billed for electricity consumption only at the rate of $33 per month.
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 Hybrid Cloud Guide