One of EPAM Orchestration aims was to unify working with Hybrid Clouds. We paid much attention to improving AWS integration with EPAM Orchestration, so that the user feels minimum difference when working with two cloud providers.

AWS Roadmap

As EPAM Cloud gets more integrated with Amazon, our users tend to create their infrastructure in AWS more and more often. This causes the growing need to use AWS services that are not available via Maestro CLI.

To solve this problem and to provide our users with the ability to access existing AWS features, we added a couple of new CLI commands and scenarios. We also created a roadmap that will help you to make the correct decision and find the necessary information resources.

1/2 To activate your project in EPAM Cloud or AWS for a project, please submit an activation request at EPAM Service Desk and provide the details.
3 To perform standard instance manipulations in AWS, you can use Maestro CLI commands with AWS regions specified as --region parameter value. For more details, please, see Maestro CLI Reference Guide , sections 2: Getting Started and 3: Working with Instances.
4 The details on setting up the S3 tool on AWS instances, please, see in the Hybrid Cloud Guide.
5 To get a temporary access to AWS management console, run the or2-aws-management-console command and follow the link provided in the command response. For more details, please, see Hybrid Cloud Guide.
6-9 To find more information on the mentioned EPAM Cloud capabilities, please, see our Cloud Management Console and Billing guides.
10 EPAM Cloud web-site is available on
11 The details on EPAM Cloud integration with AWS and Azure are given in other section on this page
12 For more information on AWS Partnership program, please, see the Amazon Partner Network page.

AWS Regions Activation

To activate AWS regions for your project in EPAM Cloud, simply leave a Project or Region Activaion Request.

The request is free of charge and will be fulfilled during three working days. Please remember that it should be approved by the Project Manager/Project Coordinator.

When the project is activated in AWS, all the project members get a corresponding email notification, and the access to all AWS regions via EPAM Orchestration.

AWS Images and Aliasing

The image format is typically bound to the virtualizer this image is aimed to be run with. Therefore, the images that can be used by one software, are inapplicable for another.

That's why EPAM Orchestration uses different types of images to run instances in EPAM Cloud and in AWS. However, all the images available for AWS are functional "twins" of EPAM Cloud public images. This means that the VMs run from a pair of "twin" images in different clouds will have the same Operating System.

To provide better usability, Maestro CLI supports referencing images with a set of aliases, with one alias referencing both "twin" images. Maestro CLI detects which image is exactly to be used basing on the region specification in the command where the alias is referenced:

More details on AWS aliasis is given in AWS Utilization Guide, attached to this page.

AWS Instance Types

In EPAM Orchestrator, Shape is a combination of CPU and RAM that your virtual machine will have. In AWS, the same parameters are referred to as Instance Type.

When creating a new AWS instance, specify the EPAM shape name, and Orchestrator will automatically map it to the corresponding AWS instance type according to the table below. The instance type parameters may vary according to selected AWS region.

In AWS, instance type is also determined by the AMI virtualization type which can be paravirtual (PV) or hardware virtual machine (HVM). HVM images have a fully virtualized hardware set and boot through the master boot record of the root block device of the image. This way, the OS runs directly on the VM. In addition, HVMs use the hardware extensions of the host system (CPU, network and storage) which can have a positive effect on their performance.

PV AMIs boot through a special boot loader and cannot use the hardware extensions.

Windows AMIs support HMV virtualization, while Linux images support both types. When a VM is created, the system checks whether HMV virtualization is supported index the selected region and, if so, creates the VM of the instance type corresponding to HVM. Otherwise, a PV-compatible instance type is used.

For more information on AWS virtualization types and their comparison, please see Linux AMI Virtualization Types page.

EPAM Shape Virt. Type #vCPU Memory AWS Instance Type Mapping
Micro HVM 1 512MB t1.micro*
PV 1 512MB t2.nano
Mini HVM 1 1GB t1.micro
Small PV 1 1.7GB m1.small
HVM 1 2GB t2.small
Medium HVM 1 3.75GB m1.medium
HVM 2 4GB t2.medium
HVM/PV 2 3.75GB c3.large
Large HVM/PV 2 7.5GB m3.large
HVM/PV 2 8GB t2.large
XL HVM/PV 4 7.5GB c3.xlarge
HVM 4 7.5GB c4.xlarge
2XL HVM/PV 4 15GB m3.xlarge
HVM 4 16GB m4.xlarge
3XL HVM/PV 8 15GB c3.2xlarge
HVM 8 15GB c4.2xlarge
4XL - - - -
5XL HVM/PV 8 30GB m3.2xlarge
HVM 8 32GB m4.2xlarge
6XL - - - -
7XL HVM 8 61GB r3.2xlarge

*t1.micro instance type is not recommended for usage, due to security reasons. The VMs based on this instance type cannot be exposed to internet and are not checked by Nessus Security Scanner.


AWS instances run in Cloud, have a specified IAM role, which supports the following manipulations:

  • Volume management
  • Tags management
  • Elastic IP management
  • S3 Management.

All these operations are performed via Amazon CLI that is to be set up on an AWS instance, run with Orchestrator. To set up the AWS CLI on a VM, perform the following steps:

  • Login to the VM via SSH
  • Run the following commands in the VM's console:

    apt-get update
    apt-get install python-pip
    pip install awscli
  • Check the AWS CLI work with Amazon S3:

    aws s3 ls s3:

    This command displays the folders in the S3 root. The output can be similar to this one:

    2014-11-21 16:17:05 storage-eu-west
    2014-11-21 16:10:02 storage-us-east

    To see the content of the subfolders, use the command:

    aws s3 l3://storage-eu-west


The users who work with AWS-based infrastructures can face the following limitations:

  • By default, the users who work with AWS via EPAM Orchestration, do not have the access to AWS Management Console. To get the temporary access, run he or2-aws-management-console command and follow the returned link to login to the Amazon Web Management Console directly.
  • All the operations on AWS infrastructure are performed via Maestro CLI and Create Wizard on Orchestration Management Console. In case the supported facilities are not enough, please use AWS Cloud Formation stacks that can invoke any operation supported by AWS.
  • All AWS-based VMs are accessible from EPAM locations, but are not available through other public IPs. The access check is based on public IPs, approved for locations.
    In case you need to expose an AWS VM to Internet, please, submit the Access for customers : Expose Amazon AWS server to Internet request on Service Portal. This will initiate the standard security check procedure, and if no issues are detected, the VM will be exposed to Internet.


The pricing for AWS machines run in Cloud differs from that of EO machines. EPAM Orchestration retrieves the chargeback for AWS usage via linked accounts, and does not imply any additional fee. You can find the actual prices and AWS billing models on the Amazon EC2 Pricing page on AWS website.

To estimate the price of the AWS-based infrastructure you plan to create, you can use the AWS Simple Monthly Calculator.

Please note that storage billing principles in AWS and EPAM Cloud differ. In AWS, each VM shape has its pre-defined storage volume which is fully paid irrespectively of the actual storage usage.

In EPAM Cloud, only the used storage is billed, except for OpenStack-based regions where the entire storage volume is billed irrespective of its actual usage. Each Linux VM has a default 40 GB storage and Windows has 100, and at the VM start, only the storage taken by the system is considered used.

We recommend using the online calculators to estimate the costs of your virtual infrastructure, although, taking into account that the actual resource consumption may be somewhat different. The costs are influences by multiple factors, such as traffic volume, occasional deviations from the planned usage routine, etc. In addition, Windows VMs in AWS tend to be more expensive than Linux, as their resource consumption is higher.

For example, the historical data shows that the actual monthly cost of existing VMs of similar shapes in EPAM-BY1 and AWS-USEAST regions is as follows:

VM# Region OS Shape/Type Cost (31 days, 744 hours)
1 AWS-USEAST Windows m3.large $193.176
2 EPAM-BY1 Windows Large $83.491
3 EPAM-BY1 Windows Large $77.548
4 AWS-USEAST Linux m3.large $98.952
5 EPAM-BY1 Linux Large $71.49
6 EPAM-BY1 Linux Large $73.754

You can use this data as additional reference, but please remember, that the final prices always depend on actual usage pattern, and cannot be predicted with pinpoint accuracy.

AWS Integration Training

In order to simplify your acquaintance with AWS, we developed a training and a presentation on the basic concepts of EPAM Cloud integration with Amazon. This covers the following topics:

  • What is Cloud Computing?
  • AWS Usage Roadmap
  • AWS and EPAM Cloud Management Consoles
  • Resources unification
  • Running a VM in AWS

The presentation can be downloaded from this page.

AWS Enterprise Support

EPAM Systems has purchased the AWS Enterprise Support package entitling EPAM users to a variety of AWS-related support services.

EPAM Orchestrator allows making a request directly to the AWS Support. This is implemented as a dedicated option in the Requests for Support wizard.

AWS-related requests are sent to AWS Support directly from EPAM Orchestrator. This way, your support requests are processed faster and more efficiently.

If you have an AWS-related issue, use the Requests for Support wizard on the Cloud Management Console and select AWS Enterprise Support.

When you select AWS enterprise support, the next wizard step allows specifying your project, region, subject and severity of the request. You can also add free-text comments to describe your issue in more detail.

After submitting the request, you will receive an email confirmation containing the link to your ticket in the AWS support system. When the issue is resolved, you are also notified about it by email.


Below is a list of documents related to this section. You can find the full list of our documents in the Documentation Storage.

Please select a required document:

AWS Basics Presentation

The presentation helps you to get acquainted with the basic concepts of EPAM Cloud integration with AWS