Introduction - AWS (4.2)

This installation guide describes how you perform a reference installation of Usage Engine Private Edition. It aims to provide you with a good starting point, not to provide you with a fully-fledged production-grade Kubernetes cluster.

When finished, you will have a Usage Engine Private Edition installation that is ready for you to start implementing your business logic, in the form of workflow configurations, and eventually creating your first EC Deployment.

The diagram below illustrates what the system will look like after you have followed this installation guide.

The diagram only shows the main components that this installation guide covers. For a full description of the Usage Engine Private Edition architecture, see
https://infozone.atlassian.net/wiki/x/IpJkBg.

Below, the purpose of the main components in the diagram are described:

Component	Purpose

Component	Purpose
external-dns	Makes Kubernetes resources (services, ingresses) discoverable via public DNS servers by automatically configuring the Route 53 DNS service. For additional information, please refer to: https://github.com/kubernetes-sigs/external-dns
aws-load-balancer-controller	Provisions application load balancer to satisfy ingress resources. Provisions network load balancer to satisfy service resources. For additional information, please refer to: https://github.com/kubernetes-sigs/aws-load-balancer-controller
ingress-alb	An ingress that gets created as part of installing Usage Engine Private Edition.
efs-csi-controller	This is optional and only required if your business logic implementation (workflow configuration) requires persistent file storage. Its purpose is to dynamically provision a persistent volume (pv) whenever a persistent volume claim (pvc) is created. The pv is provisioned based on the storage class (sc) that the pvc references. For additional information, please refer to:
mz-bundled-pvc	A pvc that gets created when installing Usage Engine Private Edition. It only gets created under the condition that persistence is enabled in the Usage Engine Private Edition helm chart. This is optional and only required if your business logic implementation (workflow configuration) requires persistent file storage.
platform desktop-online uepe-operator	These components are all part of the Usage Engine Private Edition helm chart. For detailed information about these components, see .
ingress-nginx-controller	This is an Ingress controller using NGINX as a reverse proxy and load balancer. This is optional and only required if you plan on creating EC Deployment(s) that use ingress. For addtional information, please refer to:
cert-manager	Automates management of TLS certificates. Although optional, it is recommended to apply TLS to Usage Engine Private Edition. For additional information, see