Skip to main content
Version: v5.1

Requirements Overview

Requirements prior to installation#

Before beginning the installation, ensure that your current system has the full set of required system resources described on this page.

These requirements are broken down into the following categories:

Essential system resources#

A Digital Twin Platform environment will generally require the following system resources:

  • Core Networking
    • Subnets, routing tables, internet access, etc.
    • Load balancing, WAF, etc. for ingress into Kubernetes
  • Kubernetes v1.34+
    • Network Policy Implementation
    • Custom Metrics Collection Implementation
    • Block storage CSI Provider
    • Shared file system CSI Provider
  • Postgres v14
  • MongoDB v6
  • Redis v7
  • Neo4J v4.4
  • Kafka v3.7
  • ActiveMQ v5.18
  • SMTP
  • DNS

Suggested requirements for Amazon Web Services#

For a detailed list of requirements, refer to the AWS requirements page.

Suggested requirements for Oracle Cloud Infrastructure#

For a detailed list of requirements, refer to the page Oracle requirements page.

Other suggested requirements#

It is also recommended to have the following:

  • Ingress, Naming, and Certificates: use ingress-nginx, external-dns, and cert-manager to auto-create your cloud-native load balancer, proxy incoming traffic to the Kubernetes cluster, assign DNS names, and issue certificates from Let’s Encrypt or another ACME-based certificate provider.
  • External Secrets: store all generated secrets in AWS Secrets Manager and pull them into Kubernetes using the External Secrets Operator. This is especially helpful for managing the secrets used by external services referenced by the Digital Twin Platform Helm Chart.
  • Service Mesh: for mTLS connections between services inside Kubernetes. The Platform does not provide native TLS between its own services or to other Kubernetes installations (such as neo4j); a service mesh is expected to encrypt that traffic (for example, Istio, Linkerd, or AWS App Mesh Controller).
  • Cluster Autoscaling: services are configured to scale horizontally as needed, so a cluster autoscaler should be in place (for example, cluster-autoscaler or AWS Karpenter).