Planning

The following should be taken into consideration when planning for a API Management - Local Edition cluster:

  • How many logical zones make up your API Management - Local Edition cluster?
  • How many Traffic Manager, Cache, NoSQL, and Log service components should each zone have?
  • A minimal API Management - Local Edition cluster with one zone and one instance of each component requires 4 CPUs and 16 GB memory.

    For example: T2 X-Large

    For information, see https://aws.amazon.com/ec2/instance-types/.

  • To support high availability (HA) and Resiliency, additional resources (CPU, Memory, and so on) may be necessary.

Since clusters can be set up in many different ways, and can be shared by many applications, it is the Administrator's responsibility to have the cluster set up and be ready for deployment.

For the Kubernetes worker nodes, use the k8s_node_size recommended in the following table:

Deployment k8s_node_size
Normal >= m3.large
No OAuth < m3.large

For the Kubernetes master node, use the k8s_master_size recommended in the following table:

Number of nodes in the cluster k8s_master_size
< 5 m3.medium
6 - 10 m3.large
> 10 m3.xlarge