This topic contains the following sections:
Infrastructure as a Service, cloud service providing users with virtual computers and, sometimes, hardware and other resources. IaaS providers take care of physical resources, backup, security and other aspects creating an infrastructure where users can install their operating systems and application software.
See the Cloud Computing. IaaS / PaaS / SaaS Layers presentation for more information.
Visit the Cloud Orchestration Framework page for the details on IaaS capabilities used in the Cloud Orchestrator.
Infrastructure as Code, type of IT infrastructure provisioned and maintained through the use of code rather than manual process. IAC is sometimes referred to as programmable infrastructure. In IAC, provisioning and deployment processes are automated with the use of scripts. For example, IAC practices can be used to install and verify applications, create user accounts, set up databases, etc.
IAM, Identity and Access Management, is the AWS web service used to control users' access to the AWS resources. The IAM service is included in the features of the AWS account at no additional charge.
The user holding an AWS account can create IAM users within such AWS account. In such case, IAM users can access the AWS resources without using the credentials. The AWS login and password are not shared. Different IAM users can have different permissions to use the AWS resources. The AWS account is billed for the resources consumed by the IAM users.
Visit the Introduction to IAM page for details.
In EPAM Cloud, an existing AWS account can be used to access the AWS services via Orchestrator. IAM users can be created on the basis of such account. See the Maestro User Guide for details.
Image is a virtual appliance that stores all the information about the operating system of an instance, its configuration, metadata, permissions, and other settings that are applied to an instance when it is created. Available operating systems are Windows, Linux, and MacOS. The selected image influences the available shape options and thus determines the future performance and costs.
EPAM Orchestrator uses different types of images to run instances in private regions and public clouds. However, the existing aliasing approach unifies the process of creating the resources and ensures that resources with same parameters have similar configurations in different clouds.
Virtual machine - a software implementation of a physical computer. To request and run an instance, the following parameters should be specified:
- The project to which the instance is to be assigned
- The region in which the instance will be used
- The image (operating system configuration) to be used with the instance
- The shape (number of CPUs and RAM volume) of the instance to be created
See the Maestro CLI User Guide, Section 2, Working with Instances, for details on instance management.
Capacity of an instance defined by the number of vCPUs and the RAM size.
When a project is activated, the following shapes are available for it by default:
Other shapes can be requested by sending a Support Request.
See the Maestro CLI User Guide, Annex C, Instance Types and Their Shapes, for more details on the available instance shapes.
User-defined metadata which can be assigned to instances for description and auto configuration purposes.
See the Maestro CLI User Guide, Instance Properties for more details.
User acting as a contact point for an instance and receiving notifications on instance status changes. The instance owner cannot unsubscribe from the notifications related to the virtual machine they own.
Initially, the user requesting the instance is the owner of such instance. However, instance ownership can be transferred to a different user, if needed.
The instance owner is specified on the Management screen of the Cloud Management Console and in the response to the Describe Instances command sent via the Maestro CLI. See Maestro CLI User Guide, Section 2.10, Describe Existing Instances, for details.