This topic contains the following sections:

MaaS

Monitoring-as-a-Service, a ready-to-use monitoring solution based on cloud monitoring engine. MaaS solutions are easy to integrate and immediately available and have low maintenance costs. The monitoring services are constantly accessible and well-compatible with other cloud products.

EPAM Cloud has two monitoring tools - Chef monitoring and Zabbix monitoring. Both are used to get information on different aspects of the system performance.

Chef monitoring is a default service and requires no special configuration.

Zabbix monitoring service allows using Zabbix statistics in the user's infrastructure. The Zabbix service has to be activated by the user.

See Services Guide, Section 3.3, Cloud Monitoring Service, and Cloud Monitoring Service page for details.

Machine Image

A virtual appliance, storing the information on operating system and any additional appliactions and settings that should be applied to an Instance on its creation.

Image is to be specified in the virtual machine request. The image selection influences the virtual machine charge and, in some cases, the available shape options. For example, virtual machines with Windows images can only have Medium shape or larger.

See Maestro CLI User Guide, Section 2.1, Determining Available Images, for details.

Maestro CLI

Maestro Command Line Interface used to perform basic Orchestrator commands via the remote command line by sending server API requests using REST API without the need to install 3rd party utilities. In Maestro CLI operations are performed by sending a command string with the required parameters. The system response will contain the confirmation of the performed operation, the requested information or an error message, if the command format was invalid.

The default configuration of Maestro CLI can be easily set up and requires minimum effort. Advanced users may customize their Maestro CLI to get the complete and unrestricted functionality.

See EPAM Cloud Orchestrator - Maestro CLI User Guide for details.

Maestro Stack

Tool allowing to automatically run a series of Maestro CLI commands.

Stacks are created as special files, called templates, which are uploaded to Orchestrator and then executed. Using stacks can significantly reduce time for resource management and increase the project efficiency.

Maestro Stacks can either be created manually and then validated and uploaded to the Orchestrator or configured with the Stack Builder tool on the Cloud Dashboard The created stacks are stored in the Orchestrator and run, when needed.

See Cloud Formation Services Guide for details.

MFA

Multi-Factor Authentication, an authentication method in which the user's identity is verified by several independent credentials of different categories. Typically, the credentials are something the user knows (for example, the password), something the user has in their possession (a security code or token) and, in certain cases, something the user is (biometric identification, for example, fingerprints). Multi-factor authentication requires at least two of such independent credentials for user verification.

In EPAM Cloud, MFA is used as an additional security measure for IAM users working in AWS. IAM users accessing AWS have to perform two-step authentication, first providing their login and password and then, when prompted, entering the MFA code received on their smartphone.

For more details on MFA usage in AWS visit the AWS Multi-Factor Authentication page.

See Hybrid Cloud Guide, Section 8, Security, for information on setting up multi-factor authentication in AWS.

Migration to Cloud

The process of transferring projects to a cloud, comprising activation, configuration, automation and support.

  • Activation. Accumulating basic information of existing process flow and utilized technologies, contact points, for further understanding of project needs and its scale shape. This also includes introduction of Cloud Solution and comes down to configuring Virtual Hosting.
  • Configuration and preparation for performance testing and following enrichment and automation of existing environment.
  • Automation. Vertical and horizontal scaling of project, reliability improvement, setting up automation for development process, sustaining high availability.
  • Support. Supervising of set up project environment, high level support and monitoring.

See Comfortable Migration to the Cloud white paper for details.