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:
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
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) 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
-
- EPAM-BY2 is the region where personal projects can be created (for more details, see
the Account Management Guide)
-
- EPAM-BY2 supports both HDD and SSD storage. Storage type can be selected during the VM request by using the corresponding shape name (for example, MEDIUM.HDD - for HDD,
MEDIUM.SSD - for SSD). The standard shape notations (e.g. MEDIUM) are supported, in this case the default storage type for the region is used
-
- The Recycle Bin functionality is supported. This functionality allows restoring a terminated VM within 7 days after termination by sending a request
to support.epam.com
-
- Shapes up to 3XL are supported
-
- Custom image can be created only from instances with no additional volumes
EPAM-IN1, EPAM-US2
-
- 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
EPAM-UA2
EPAM-UA2 is currently run in the Beta mode, and has the following specifics:
-
- Shapes up to 3XL are supported
-
- Billing coefficient is 0 while in Beta.
-
- The region capacities are limited.
-
- Due to the limited capacities, while activating the region, the preference willbe given to the projects that are already activated in EPAM-UA1.
Network specifics in OpenStack-based regions
-
All instances in project have IPs from internal net (172.16.242.230/21)
-
All instances have an assigned floating IP from EPAM network (10.6.)
-
All instances have hostname like ECSX000XXXXX.epam.com, which can be resolved as an IP from EPAM network (for example, 10.6.129.34)
-
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.
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.
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).
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 |
- |
- |
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 (HDD/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.
Windows Images
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, and their availability in different types of regions and supported external cloud providers.
Windows Server 2012 Standard Edition |
W2012Std |
+ |
- |
+ |
- |
+ |
Windows Server 2012 R2 Standard Edition |
W2012R2Std |
+ |
+ |
+ |
+ |
+ |
Windows Server 2012 R2 Datacenter Edition |
W2012R2DC |
- |
- |
- |
+ |
+ |
Windows Server 2016 Standard |
W2016Std |
+ |
+ |
+ |
+ |
- |
Windows Server 2016 Datacenter Edition |
W20162DC |
- |
- |
- |
+ |
+ |
Windows Server Core 1709 |
WS1709Std |
- |
+ |
+ |
+ |
- |
Windows 10 Enterprise 32-bit |
Win10-32 |
+ |
+ |
- |
- |
- |
Windows 10 Enterprise 64-bit |
Win10-64 |
+/-* |
+/-* |
- |
- |
- |
*Win10 images are temporarily locked in OpenStack regions due to OpenStack performance issues.
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.
CentOS Linux 6 64-bit |
CentOS6_64-bit |
+ |
+ |
+ |
+ |
+ |
CentOS Linux 7 64-bit |
CentOS7_64-bit |
+ |
+ |
+ |
+ |
+ |
Oracle Linux 6 64-bit |
OracleLinux6_64-bit |
+ |
+ |
- |
- |
- |
Oracle Linux 7 64-bit |
OracleLinux7_64-bit |
+ |
+ |
- |
- |
- |
Debian GNU/Linux 8 64-bit |
Debian8_64-bit |
+ |
+ |
+ |
+ |
+ |
Debian GNU/Linux 9 64-bit |
Debian9_64-bit |
+ |
+ |
+ |
+ |
+ |
Ubuntu 14.04 64-bit LTS |
Ubuntu14.04_64-bit |
+ |
+ |
+ |
+ |
+ |
Ubuntu 16.04 64-bit LTS |
Ubuntu16.04_64-bit |
+ |
+ |
+ |
+ |
+ |
Ubuntu 18.04 64-bit LTS |
Ubuntu18.04_64-bit |
- |
+ |
+ |
+ |
+ |
CoreOS Container Linux 64-bit |
CoreOS_64-bit |
+ |
+ |
+ |
+ |
+ |
Please note: the general approach is given in the table. However, the set of provided images can alter in specific regions.
In external cloud regions, the last stable versions of CoreOS images are provided.
Please see the information about CoreOS images in AWS,
Google Cloud and
Microsoft Azure regions.
MacOS Images
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.
MacOS 10.10 Yosemite |
MacOS_10.10_Yosemite |
Virtual |
MacOS 10.11 EL Capitan |
MacOS_10.11_EL_Capitan |
Virtual |
MacOS 10.12 Sierra |
MacOS_10.12_Sierra |
Virtual |
MacOS 10.13 HighSierra |
MacOS_10.13_HighSierra |
Virtual |
OS X 10.12.x |
macmini_OS_X |
Hardware |
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.
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:
Pricing
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 HDD, 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:
Europe (Budapest, Hungary) |
EPAM-HU1 |
ESX |
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 |
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 Hybrid Cloud Guide