AWS-based cluster

AWS-based cluster

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


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:

  • IP ranges:

  • Domain names:

    • and for packages

    • for binaries and Helm charts

    • for Docker images

    • for Telemetry (port 443 if proxy is enabled)

    • 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.

Requirements for an AWS-based Container Cloud cluster


Bootstrap cluster 0

Management 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 nodes for the manager nodes HA and 2 nodes for the Container Cloud workloads. If the multiserver mode is enabled for StackLight, 3 nodes are required for the Container Cloud workloads.

# of vCPUs per node




RAM in GB per node




Storage in GB per node

5 (available)



Operating system

Ubuntu 16.04 or 18.04

Ubuntu 18.04

Ubuntu 18.04

For a management and managed cluster, a base Ubuntu 18.04 image with the default SSH ubuntu user name is required.

Docker version

Current version available for Ubuntu 18.04



For a management and managed cluster, Mirantis Container Runtime 19.03.14 is deployed by Container Cloud as a CRI.

Instance type




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

  • c5d.4xlarge - manager node

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

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





The bootstrap cluster is necessary only to deploy the management cluster. When the bootstrap is complete, this cluster can be deleted and its resources can be reused for the managed cluster workloads.