EPAM CloudApp Engine

EPAM CloudApp Engine is a cloud run-time environment for applications as containers on scalable resources with minimal configuration management overhead. The platform provides development, management, security, and integration capabilities, also referred to as Shared Infrastructure Services. It is delivered as a self-service over the EPAM Cloud.

Solution Highlights

EPAM CloudApp Engine is a hybrid PaaS based on an open source version of OpenShift, also called OKD4, and other additional services, which is aimed for developers who want to run containerized applications. From the customer's point of view, the main feature of EPAM CloudApp Engine is the multi-cluster capability and the support for Public Clouds such as AWS, Azure, and GCP.

EPAM CloudApp Engine Highlights

  • Hybrid PaaS Concept — It is a cloud-agnostic PaaS solution, the approach that is changed from "a single on-prem cluster in many regions" to "many small clusters in the required regions or locations deployed over different IaaS platforms".
  • Extended Service Offering — An extension for the Service offering. Provides integration with the managed services of public clouds, bootstrappers for quick starting of a multi-language application (such as Java or Dot Net), and operator-based self-managed services.
  • Self-Service Capabilities — CloudApp Engine offers its customers the maximum self-management capabilities and automation in processing the ESP tickets.
  • Portable Application Management — Provides portability of applications between the existing clusters, and the ability to build the hybrid multi-cloud applications.
  • Enterprise Support — There are SLAs defined for the platform with the advanced monitoring and logging services.

Services Offering

EPAM CloudApp Engine is an internal EPAM Platform-as-a-Service solution that is targeted to accelerate delivery of the development outcome on your project by providing your team with a modern and technologically advanced toolkit that will help to carry out major infrastructure and development operations tasks on your project.

At present, EPAM CloudApp Engine users have access to the following features:

1. PaaS V3 Core Services

  • EPAM PaaS V3 Container Engine hosted in the EPAM Cloud on-prem
  • Web console and CLI
  • Security compliant by default (SIEM, Vault, Qualys, SentinelOne) with multiple authentication options
  • Container engine CPU and memory within your namespaces quotas and limits
  • Persistent Storage self-services within your namespaces quotas and limits
  • SDN Networking service capabilities (Namespaces Network isolation) and Service Discovery for applications

2. EPAM CloudApp Engine Core Services

  • EPAM CloudApp Engine Container Engine hosted in the EPAM Cloud on AWS
  • Web console and CLI
  • Security compliant by default (SIEM, Vault, Qualys, SentinelOne) with multiple authentication options
  • Container engine CPU and memory within your namespaces quotas and limits
  • Persistent Storage self-services within your namespaces quotas and limits
  • SDN Networking service capabilities (Namespaces Network isolation) and Service Discovery for applications

3. EPAM CloudApp Engine Managed Services

  • Routers and services: DNS-es generation, predefined common certificates, and custom annotations
  • Monitoring core resources
  • Logging store with auth and quotas in days and size
  • Internal docker registry repository for your CI/CD pipelines
  • Config store: number of secrets and configmaps within your quotas and limits
  • Selenium test automation with Moon

4. Cloud Native and Community Services

  • Open-source Services Catalog
  • Public Cloud Managed Services
  • CI/CD tools
  • IDE workspaces

5. EPAM CloudApp Engine Monitoring

  • Infrastructure monitoring
  • Alerting engine

6. Customer Services

  • Onboarding assistance
  • Architecture consulting
  • 24/7 infrastructure support
  • End-user support
  • EPAM CloudApp Engine Billing service
  • Cost optimization tools

Pricing Policy

With EPAM CloudApp Engine, you pay only for what you use! No additional fees are applied. It means that you pay only for the requested cluster resources — CPU, Memory, and Storage — and the resources you consume on each container and namespace and depending on how stable the region was chosen for launching containers in accordance with Workload placement strategy.

Currently we offer two pricing tiers:

  • 1. Free Trial — Personal namespace for EPAMers - $0
  • 2. Professional — Offered for EPAM projects -Pay as you Go

Getting Started for EPAM Projects

To start working with EPAM CloudApp Engine please perform the following steps:

  • 1. Get an EPAM CloudApp Engine Project Namespace via respective support request.
  • 2. When you are notified about your namespace creation, log into EPAM ClodApp Engine with your EPAM account credentials.
  • 3. Choose what to pick next on User Guides.

Along with this, we offer the second option to getting started with EPAM CloudApp Engine — Personal Namespace. The Personal namespaces are intended only for EPAM employees for learning purposes. They are offered for free as a self-service option, with certain restrictions. To start Free Trial follow the Getting Started with Personal Spaces guide.

References

You can find more information about EPAM CloudApp Engine via the following links: