Usage Engine Private Edition can be deployed on any Kubernetes engine compliant with the upstream version stated in the release notes. This includes OpenShift distributions as well as the hosted Kubernetes services available from all hyper-scalers – Amazon EKS, Google GKE and Azure AKS.
Test and Development Environment
A local environment can easily be setup in lightweight desktop Kubernetes environment like Docker Desktop, Rancher Desktop, Minikube or similar. Standard container runtimes like containerd and dockerd are supported. At least 2 CPUs and 4Gb of memory is recommended for a basic deployment with a few simple workflows.
Deployment in AWS
AWS is currently the most common and well tested environment for public cloud deployments. DigitalRoute provides customizable infrastructure as code (IaC) templates in Terraform format to make it possible to get an environment up and running quickly.
The following services are mandatory in an AWS deployment:
Amazon RDS for PostgreSQL
Amazon Elastic File System
Amazon Route 53
Amazon Elastic Kubernetes Service
AWS Key Management Service
Elastic Load Balancing
Note that Usage Engine require Kubernetes and thus is not possible to deploy in Amazon ECS or directly on EC2s without Kubernetes.
Deployment in other cloud environments
Usage Engine can be deployed in any cloud environment that provides an upstream compatibly Kubernetes cluster. It has been verified in hyperscaler environments like Google Cloud Platform, Microsoft Azure as well as in private cloud using Kubernetes distributions like OpenShift, Rancher and VMware Tanzu.
Usage Engine is delivered as an environment agnostic Helm chart, ready to be deployed in any Kubernetes cluster. To take full benefit from the application and environment, some services need to be configured to provide:
Shared file system - Corresponding to EFS in AWS
DNS - Corresponding to Route53 in AWS
Layer 7 and layer 4 load balancer – Corresponding to ALB and CLB in AWS
Postgres or Oracle compatible database – Corresponding to RDS in AWS
Certificate management for TLS traffic – Corresponding to KMS in AWS