APPUiO Managed Kubernetes with EKS

APPUiO Managed Rancher with Amazon Elastic Kubernetes Service (EKS) is our product to provide services for the managed Kubernetes offering of Amazon AWS.

Use Cases

Full Production Readiness

Managed cloud services are engineered for production. Leveraging these services is the recommended path into production.

Step in to the Cloud

Managed cloud services are perfect to start using the cloud. If the cloud is already used, managed cloud services are the perfect way to use Kubernetes.


Using Kubernetes from Hyperscaler clouds allows for full scalability. With Hyperscaler-managed Kubernetes, you can get rid of infrastructure "pets" that need special attention. See The History of Pets vs Cattle and How to Use the Analogy Properly for a good read.


Hyperscaler clouds not only offer Kubernetes, but a large amount of other services. By using the Kubernetes offering of a Hyperscaler cloud, all the other available services are just waiting to be used.

Costs saving

Usually big clouds are not necessarily cheaper out of the box. By using the possibilities the cloud offers with integrated Cluster autoscaling or other optimization tricks like "Spot" instances a huge cost saving can be achieved.

Shared Rancher Management Server

VSHN operates a shared Rancher Management Server and provides access to it for users of the APPUiO Managed Rancher product.

The VSHN provided Rancher Management Server includes:

  • Access to the Kubernetes cluster with a VSHN Account

  • Graphical overview of the Kubernetes cluster

  • Access control to the clusters

  • GUI to deploy applications

Instead of using the shared Rancher Management Server a dedicated instance can be provided at additional cost. Please contact us for more information.

VSHN Supported Features and Configuration

Supported by default

These features and configurations are available out-of-the box and installed and configured by default.

Feature / Configuration Description

Cluster Maintenance

Kubernetes control-plane and node updates are applied continuously when they’re available. See also Version and Upgrade Policy.

Persistent Storage with CSI

Storage is provided by the native cloud storage offering using officially support CSI integrations.

Cluster Backup

A full backup of the etcd database is made every 4 hours. This includes a dump of all objects in JSON format, this way single objects can be restored on request. The backup data is encrypted before it is stored in an object storage backend, usually on the same cloud as the cluster is running. K8up is used as the backup operator, using Restic as backup backend.

Persistent storage volumes are not automatically backed up. The user of persistent volumes is obliged to take care of this. For that purpose, K8up is available on the cluster to help with that task. We’re also happy to help, just let us know.

Setup with Terraform

Cluster provisioning is done with Terraform, which includes all needed cloud resources for the Kubernetes cluster to work.

Cluster limits

We’re following the recommendations of upstream Kubernetes. See Limits for more details.

Supported on request

These features or configuration adjustments must be specifically requested and some restrictions apply. Activation and configuration of these features imply additional engineering costs and can cause additional recurring engineering costs for operating them.

Feature / Configuration Description


Crossplane is an open source Kubernetes add-on that enables platform teams to assemble infrastructure from multiple vendors, and expose higher level self-service APIs for application teams to consume, without having to write any code. We can help with the deployment and configuration of Crossplane on the cluster to make it ready to work with the cloud the cluster is provisioned in.

Cluster Autoscaling

Cluster autoscaling configuration is fully supported, depending on the possibilities of the cloud service.


These features or configuration adjustments are not supported by VSHN, but can still be activated, changed or used, although are neither monitored, backed up nor maintained. No guarantees are given, use them at your own risk.

Still interested in one (or more) of these unsupported options? Get in contact with and we figure out together what we can offer.
Feature / Configuration Description

Cluster Provisioning with Rancher

Provisioning of Kubernetes clusters via the Rancher Management Server is only supported with a dedicated Rancher Management Server.

OPA Gatekeeper

The Open Policy Agent Gatekeeper is not supported by VSHN.


Istio is not supported by VSHN.

CIS Kubernetes Benchmark

CIS scans aren’t support by VSHN.

Longhorn Storage

Longhorn storage isn’t support by VSHN.


Pipelines aren’t supported by VSHN. We recommend using GitLab for that.


Rancher logging is currently not in use by VSHN, we’re using a Project Syn component for log-shipping with Fluent Bit as this allows for more flexible configuration.

Version and Upgrade Policy

Supported are only the Kubernetes versions of AWS which are compatible with the Rancher version used by VSHN.

The official upstream documentation applies:

Installations must be upgraded to the next release within three months after a new release is available.


The price model is described here: Price Model.

Pricing information of EKS can be found under Amazon EKS pricing. Additionally to the EKS control plane compute resources will incur costs.

Minimum Requirements

Item Description

EKS control plane

1 control plane

See Amazon EKS clusters for a description.

EKS nodes

At least 3 nodes

Refer to Amazon EKS nodes for options.


Please refer to Amazon EKS service quotas to see the current limits and quotas for the EKS product.

The maximum number of Pods per Node is dictated by the number of available IP addresses, see eni-max-pods.txt for a calculation (Source: Stackoverflow).