Billing & Quotas

EPAM Cloud Service provides you with a flexible system of resources and costs planning, monitoring and management.

Resource Utilization Quotas

In order to prevent unexpected expenses each EPAM project is assigned a certain Cloud Resources Utilization Quota - an allowance, that can be used to run instances, create storages and manage the aforementioned resources, in accordance with actual prices. General allowance is composed of Computing and Storage quotas. Computing quotas encompass operations on instances, while Storage quotas address volumes.

Resource Utilization Quotas are set via the Manage Cloud Wizard available to Project Managers, Project Coordinators, Account Managers and Delivery Managers.

a. Quotas are set for regions in which the project is activated or for region types. In this field, select the project, where you want to update quotas.

b. The quotas are applied by specific regions, by region types, or to the whole Cloud infrastructure. The type of the quota depends on the region or set of regions to which it is applied. The following options are possible:

  • ALL - the specified quota will be applied cumulatively to all regions in which the project is activated, unless a narrower quota is set
  • ALL_EPAM - the specified quota will be applied cumulatively to all EPAM regions in which the project is activated, unless a narrower quota is set
  • ALL_AWS - the specified quota will be applied cumulatively to all EPAM regions in which the project is activated, unless a narrower quota is set
  • ALL_AZURE - the specified quota will be applied cumulatively to all Azure regions in which the project is activated, unless a narrower quota is set
  • ALL_GOOGLE - the specified quota will be applied cumulatively to all Google Cloud regions in which the project is activated, unless a narrower quota is set
  • EACH - the specified quota will be applied to each region in which the project is activated, unless a narrower quota is set
  • EACH_EPAM - the specified quota will be applied to each EPAM region (named as EPAM-XXX), unless a narrower quota is set
  • EACH_AWS - the specified quota will be applied to each AWS region (named as AWS-XXX), unless a narrower quota is set
  • EACH_AZURE - the specified quota will be applied to each Azure region (named as Azure-XXX), unless a narrower quota is set
  • EACH_GOOGLE - the specified quota will be applied to each Google region (named as GCP-XXX), unless a narrower quota is set
  • Region by name - set up quota for a specific region

c. The quota amount specifies the monthly expense limit according to the selected quota type.

All-type quotas control the total aggregated amount used for all affected regions and trigger the quota action as soon as the aggregated amount reaches the specified level. Each-type quotas control the amount used in each affected region separately and trigger the quota action as soon as the amount in the particular region reaches the specified level. In all cases, the most restrictive quota applies.

By switching between region options, you can specify a multi-level quota system. In case several region rules are applicable to a region (for example. "EACH_EPAM" and "EPAM-BY1"), the one with smaller quota limit is applied.

d. After selecting the quota amount, choose the action to be taken when the quota is depleted in the particular region. The following quota actions are available:

  • Stop VMs when 100% quota depleted - Once a quota has been depleted, all resources in the region are stopped automatically. They are not terminated, you will be able to access them next month or as soon as your quota is refilled.
  • Request approval for new VMs after quota is 100% depleted - Once the set quota has been depleted, project members will be able to request creating new resources in the region where quota has been depleted, but the action will not be performed until the Project Manager or Delivery Manager approves it. The Project Manager or Delivery Manager receives an email notification where they can approve or reject a new VM creation
  • Deny requesting new VMs when 100% quota depleted - Restricts running new VMs
  • Disable quota - Allows resource actions despite the quota depletion

Please note that for AWS, Azure and Google Cloud regions, quotas are mandatory. For all projects activated in AWS, Azure or Google Cloud, a default ALL_AWS, ALL_AZURE or ALL_GOOGLE quota of $300 is set. To change the quota, use the Manage Cloud Wizard as described in the Managing Quotas section. All quota settings are subject to approval by the Director of Global IT Operations. When the quota has been approved, you will see the applicable quota amount in the Manage Cloud Wizard as well as in the response to the or2report command in Maestro CLI.

e. In Notification plan section, select the quota utilization rate, at which you would like to get the notification with quota usage update information.

For more information on Resource Utilization Quotas see the Account Management Guide.

Billing Model for EPAM Cloud

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.

EPAM Cloud Orchestrator utilizes a specifically designed flexible billing model for private regions. The approach is based on the pay-as-you-go principle, and includes the following basic rules:

  • The resources are billed on per-second basis in OpenStack regions, and hourly for ESX ones. The price for a second or an hour is derived from the pre-established monthly price, and is based on the assumption that there are 730.5 hours per month in average.
  • The prices in all private regions are the same.
  • The billing for active (running) and passive (stopped) VMs differs, as the stopped VMs consume less resources.

For the sake of easier comprehension, the billing model is presented on the following diagram and detailed below:

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 description.

You can find the detailed information on pricing by each element by calling the "or2price -r region" Maestro CLI command.

AWS Billing

The pricing for AWS machines run in Cloud differs from that of EO machines. Orchestration retrieves AWS billing information due to linked accounts principle and does not imply any additional fee.

You can find the actual AWS prices and 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 is similar to those for EPAM Cloud OpenStack regions: each VM shape has its pre-defined storage volume which is fully paid irrespectively of the actual storage usage.

For more details on AWS usage and billing, please see the Hybrid Cloud page.

Azure Billing

EPAM Orchestrator retrieves the billing information directly from Azure and provides it to the users "as is". Please take into account the following specifics of Azure billing:

In Azure, only the used storage is billed. 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 and is charged.

Azure prices for the resources that have already been charged can change. If the change takes place after EPAM Orchestrator closes the month, the difference is taken into account during the next month billing generation.

To estimate the price of the infrastructure to be hosted in Azure, use the calculator on the Azure Pricing page.

Billing in Google Cloud Platform

Billing in Google Cloud differs from billing in EPAM Cloud in certain ways. Please note the specifics of Google Cloud billing below.

In Google Cloud, the provisioned storage is billed, regardless of the actual usage.

Google Cloud billing supports no cost distribution by region, therefore, all project costs will be billed to one of the regions specified as default. Billing for individual resources is not supported, however, the costs are broken down by resource type.

To find the price of Google Cloud-based infrastructure, use the Google Cloud Platform Pricing Calculator.

Billing by Tags in Public Clouds


To sort your costs and optimize the reports you get, you can set cost allocation tags to AWS items.

The resources can be grouped by environment type, purpose, belonging to a specific team, etc. By AWS design and best practices, one resource can have several tags and belong to several groups (up to 50). This allows effective multi-dimensional costs filtering within accounts.

Currently, the default cost allocation tags library for AWS includes these five tag keys:

  • user:tag (the tag initially included in the library)

  • project

  • application

  • environment

  • aws:cloudformation:stack-id (the tag, automatically added by the CloudFormation service)

An AWS cost allocation tag consists of two parts – a key and a value that you define on the tag creation. The diagram below illustrates the concept of tags in AWS.

Both tagged and untagged resources will be included in the monthly reports, but you can use tags to aggregate the reporting data by logical, functional, or any other criteria.

Azure Cloud

These words are reserved by Azure and cannot be used as a tag prefix or a tag key – microsoft, azure, windows:

Google Cloud

Billing by tags is not supported for Google Cloud Platform.

Hardware Instances Pricing

EPAM Orchestrator allows to register, monitor and manage hardware instances of two types - Hardware Macmini and Dedicated instances (hardware servers). This section provides the basic information on the hardware billing principles.

The detailed information on hardware billing is given in the respective section of the Account Management Guide. Please note: the described billing policy is applied since August 1, 2018. For the details of the previous policy, please see Annex C of the same guide.

Hardware Macmini Pricing

Hardware Macmini instances are provided within the EPAM-MAC region only. The only possible configuration is:

  • Shape: LARGE (2CPU, 8Gb RAM)
  • System disk: 300Gb (not extendable)

The price for Macmini instances is $30/Month, calculated hourly as $30/730.5 per hour.

Dedicated Instacnes Pricing

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.

Dedicated instances related to hardware resources are assigned to the hardware region, EPAM-HW1, and this name is to be specified when one needs to review or manage these resources.

Each assignment has a serverUsage parameter identifying which part of the server capacity the project uses. Typically, the value here is 100%. However, there are servers used by several projects simultaneously. In this case, the projects can have different values for the parameter, but the total for the server should be 100. The monthly chargeback for shared servers is divided between the projects according to their serverUsage rate.

The cost of a dedicated instance depends on the DC type (owned by EPAM or rented), and the the hardware ownership (belongs to EPAM or bought by project/customer). In general, the price of a dedicated instance is affected by the following services usage:

Hosting: Server equipment hosting cost.

Electricity: Cost of the electricity, used to supply the server and the cooling system.

Hardware amortization: Hardware amortization cost for the reporting period (month).

Technical support service: Technical support service for the reporting period (month) provided by the equipment vendor.

The prices in own and rented DCs can vary, as each hosting provider has its own billing approaches. With rented DCs, the chargeback billed to the project can change due to the updates in the terms of contract with the provider, or the significant changes in the rate of the accounting currency to the USD.

If the dedicated instances are hosted in a public provider, the billing is calculated by the respective provider and the service costs are transmitted to the project through the EPAM Billing System.