Requirements for an AWS-based cluster

While planning the deployment of an AWS-based Mirantis Container Cloud cluster with Mirantis Kubernetes Engine, consider the requirements described below.

For system requirements for a bootstrap node, see Requirements for a bootstrap node.


Some of the AWS features required for Container Cloud may not be included into your AWS account quota. Therefore, carefully consider the AWS fees applied to your account that may increase for the Container Cloud infrastructure.

If you use a firewall or proxy, make sure that the bootstrap, management, and regional clusters have access to the following IP ranges and domain names required for the Container Cloud content delivery network and alerting:

  • IP ranges:

  • Domain names:

    • and for packages

    • for binaries and Helm charts

    • and * for Docker images

    • for Telemetry (port 443 if proxy is enabled)

    • and for Salesforce alerts


  • Access to Salesforce is required from any Container Cloud cluster type.

  • If any additional Alertmanager notification receiver is enabled, for example, Slack, its endpoint must also be accessible from the cluster.


If you want to deploy a managed cluster that is based on Equinix Metal on top of an AWS-based management cluster, see Requirements for an Equinix Metal based cluster.


The requirements in this section apply to the latest supported Container Cloud release.

Requirements for an AWS-based Container Cloud cluster


Management or regional cluster

Managed cluster


# of nodes

3 (HA)

5 (6 with StackLight HA)

  • A management cluster requires 3 nodes for the manager nodes HA. Adding more than 3 nodes to a management or regional cluster is not supported.

  • A managed cluster requires 3 manager nodes for HA and 2 worker nodes for the Container Cloud workloads. If the multiserver mode is enabled for StackLight, 3 worker nodes are required for workloads.

# of vCPUs per node



RAM in GB per node



Storage in GB per node



Operating system

Ubuntu 20.04

Ubuntu 20.04

For a management and managed cluster, a base Ubuntu 20.04 image is required.




Mirantis Container Runtime (MCR) is deployed by Container Cloud as a Container Runtime Interface (CRI) instead of Docker Engine.

Instance type



To prevent issues with low RAM, Mirantis recommends the following types of instances for a managed cluster with 50-200 nodes:

  • c5.4xlarge - manager node

  • r5.4xlarge - nodes where the StackLight server components run

The /var/lib/docker Docker data is located on the same EBS volume drive as the operating system.


Do not stop the AWS instances dedicated to the Container Cloud clusters to prevent data failure and cluster disaster.

Bastion host instance type



The Bastion instance is created with a public Elastic IP address to allow SSH access to instances.

# of volumes

7 (total 110 GB)

5 (total 60 GB)

  • A management cluster requires 2 volumes for Container Cloud (total 50 GB) and 5 volumes for StackLight (total 60 GB)

  • A managed cluster requires 5 volumes for StackLight

# of Elastic load balancers to be used



  • Elastic LBs for a management cluster: 1 for Kubernetes, 4 for Container Cloud, 5 for StackLight

  • Elastic LBs for a managed cluster: 1 for Kubernetes and 5 for StackLight

# of Elastic IP addresses to be used