---
schema_version: "1"
id: 99ed224282b6bb07954651d11dc424db01e20230a4e81d294b49c1adc0a362e4
title: Supported Configurations for Anypoint Platform PCE
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/private-cloud/3.2/supported-cluster-config.md
canonical_url: https://docs.mulesoft.com/private-cloud/3.2/supported-cluster-config
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 319b894befe842c7cf9fcab35962505a02fac7331cb0f5b55c91f22dde516ea6
description: MuleSoft Documentation Site
release: "3.2"
latest: false
---
---
product: Anypoint Platform Private Cloud Edition
version: 3.2
---

# Supported Configurations for Anypoint Platform PCE

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

To ensure platform performance, stability, and high availability, Anypoint Platform Private Cloud
Edition (Anypoint Platform PCE) supports two network configurations: 4-node and 7-node. To ensure
high availability and performance, each node must run on its own server in both configurations. If
you are using a virtual machine to host the nodes, you must ensure that each VM node is running on a
separate physical server.

Both the 4-node and 7-node configurations have two separate components:

- Anypoint Platform Core

- Monitoring Center Add-On (optional)

## 4-Node Configuration

The 4-node configuration is the smallest configuration that Anypoint Platform PCE supports. This is
the minimum number of nodes that can enable high-availability and failover. In this configuration,
each node hosts the platform applications and services. You must configure a load balancer to use
round-robin distribution of traffic among each of the four nodes.

![4-node Configuration](/mulesoft/current/en-us/private-cloud/3.2/_images/configuration-4-node.png)

Three of the nodes host an instance of the database and object store. Hosting the database and
object store enables persistence but requires larger minimum disk and memory requirements. Although
three of the nodes contain a database, only one database is used as the primary. Applications on
each node write to this database only. The other two database instances are hot standby instances of
the primary database that take over as the primary database in case of failure.

## 7-Node Configuration

In the 7-node configuration, four nodes are dedicated to hosting platform applications and services.
The other three nodes host the database and object store instances. Although each node contains a
database, only one of the database nodes is used as the primary. Applications on each node write to
this database only. The other two database instances are hot standby instances of the primary
database that take over as the primary database in case of failure.

![7-node Configuration](/mulesoft/current/en-us/private-cloud/3.2/_images/configuration-7-node.png)

You must configure a load balancer to use round-robin distribution of traffic among all of the nodes
in your cluster.

## Supported Platform Components and Configuration

> [!WARNING] The following recommendations and limits are based on the following resources:
>
> - A 4-node environment consisting of 4 nodes of 8 cores and 32GB RAM, or
>
> - A 7-node environment consisting of 7 nodes of 8 cores and 32GB RAM.

### Mule Runtime Engine and Mule Applications

The following table shows the recommended and maximum number of Mule instances and Mule applications
that Anypoint Platform PCE supports:

<table><colgroup><col> <col> <col></colgroup><thead><tr><th></th><th>4-node Configuration</th><th>7-node Configuration</th></tr></thead><tbody><tr><td><p>Maximum number of Mule instances per environment</p></td><td><p>500</p></td><td><p>500</p></td></tr><tr><td><p>Maximum number of Mule instances across all environments</p></td><td><p>1500</p></td><td><p>3000</p></td></tr><tr><td><p>Maximum number of Mule instances per server group</p></td><td><p>20</p></td><td><p>20</p></td></tr><tr><td><p>Maximum Mule instances per cluster</p></td><td><p>8</p></td><td><p>8</p></td></tr><tr><td><p>Mule applications under management per environment (recommended)</p></td><td><p>Under 200</p></td><td><p>Around 200</p></td></tr><tr><td><p>Mule applications under management per environment (maximum)</p></td><td><p>500</p></td><td><p>500</p></td></tr><tr><td><p>Mule instances under management (maximum)</p></td><td><p>500 single Mule runtime engine, or 250 Mule runtime clusters, consisting of 2 Mule runtime engines per cluster</p></td><td><p>1000 single Mule runtime engines, or 500 Mule runtime clusters, consisting of 2 Mule runtime engines per cluster</p></td></tr><tr><td><p>Mule applications per Mule runtime engine (recommended)</p></td><td><p>Fewer than 25</p></td><td><p>Fewer than 25</p></td></tr><tr><td><p>Mule applications per Mule runtime engine (maximum)</p></td><td><p>100</p></td><td><p>150</p></td></tr></tbody></table>

### APIs and API Manager

<table><colgroup><col> <col> <col></colgroup><tbody><tr><td></td><td><p>4-node Configuration</p></td><td><p>7-node Configuration</p></td></tr><tr><td><p>Maximum instances per API group</p></td><td><p>100</p></td><td><p>100</p></td></tr><tr><td><p>Client applications (per user)</p></td><td><p>5000</p></td><td><p>5000</p></td></tr><tr><td><p>Client applications (per root organization)</p></td><td><p>10000</p></td><td><p>10000</p></td></tr><tr><td><p>Maximum API instances manager per root organization</p></td><td><p>6000</p></td><td><p>12000</p></td></tr><tr><td><p>Applied policies</p></td><td><p>12000</p></td><td><p>24000</p></td></tr><tr><td><p>Created contracts</p></td><td><p>12000</p></td><td><p>24000</p></td></tr></tbody></table>

For both 4-node and 7-node configurations, the following apply:

- Maximum instances per API group

- Applications

- A single API implementation with one policy counts as 0.5 APIs.

- A single clustered proxy with up to 5 policies counts as 1.

- All Mule instances are polling every 60 seconds.

### Access Management

<table><colgroup><col> <col> <col></colgroup><thead><tr><th></th><th>4-node Configuration</th><th>7-node Configuration</th></tr></thead><tbody><tr><td><p>Maximum number of supported business groups</p></td><td><p>75</p></td><td><p>N/A</p></td></tr><tr><td><p>Maximum number of users</p></td><td><p>10000</p></td><td><p>N/A</p></td></tr></tbody></table>

See the Access Management documentation for more information on
[identity management and supported providers](https://docs.mulesoft.com/access-management/external-identity).

### Exchange

<table><colgroup><col> <col> <col></colgroup><thead><tr><th></th><th>4-node Configuration</th><th>7-node Configuration</th></tr></thead><tbody><tr><td><p>Maximum Exchange assets</p></td><td><p>60,000</p></td><td><p>60,000</p></td></tr><tr><td><p>Maximum file size when publishing asset through UI</p></td><td><p>5 MB</p></td><td><p>5 MB</p></td></tr><tr><td><p>Maximum uncompressed file size</p></td><td><p>50 MB</p></td><td><p>50 MB</p></td></tr><tr><td><p>Maximum file size when publishing asset through Maven</p></td><td><p>200 MB</p></td><td><p>200</p></td></tr><tr><td><p>Maximum number of dependencies for a single asset</p></td><td><p>100</p></td><td><p>100</p></td></tr><tr><td><p>Maximum icon size</p></td><td><p>2 MB</p></td><td><p>2 MB</p></td></tr><tr><td><p>Maximum number of resources (attachments) per asset portal</p></td><td><p>100</p></td><td><p>100</p></td></tr><tr><td><p>Maximum resource size for attachments to the asset portal</p></td><td><p>2 MB</p></td><td><p>2 MB</p></td></tr><tr><td><p>Maximum indexable asset content for RAML or asset portal</p></td><td><p>1 MB</p></td><td><p>1 MB</p></td></tr><tr><td><p>Maximum number of categories per organization</p></td><td><p>500</p></td><td><p>500</p></td></tr><tr><td><p>Maximum number of custom configurations per organization</p></td><td><p>500</p></td><td><p>500</p></td></tr><tr><td><p>Maximum number of pages in a portal</p></td><td><p>50</p></td><td><p>50</p></td></tr><tr><td><p>Maximum length of page name</p></td><td><p>128 characters</p></td><td><p>128 characters</p></td></tr><tr><td><p>Maximum review title length</p></td><td><p>30 characters</p></td><td><p>30 characters</p></td></tr><tr><td><p>Maximum review text length</p></td><td><p>2048 characters</p></td><td><p>2048 characters</p></td></tr></tbody></table>

The 1 MB maximum indexable asset content for RAML or asset portal means that if your portal has more
than 1MB in text, only the first 1MB will be indexed, and if your portal has more than 1 MB in RAML
specifications, only the first 1 MB will be indexed.

### API Designer and API Mocking Service

The following apply to both 4-node and 7-node configurations.

<table><colgroup><col> <col></colgroup><tbody><tr><td><p>Maximum number of projects</p></td><td><p>Limited by version control system</p></td></tr><tr><td><p>Maximum number of concurrent users</p></td><td><p>16</p></td></tr><tr><td><p>Maximum number of mocking service instances</p></td><td><p>One per API version</p></td></tr><tr><td><p>Maximum number of mocking service users</p></td><td><p>16</p></td></tr></tbody></table>

### Anypoint Monitoring

Anypoint Monitoring is an optional, add-on component. See
[Anypoint Monitoring on Anypoint Platform PCE](https://docs.mulesoft.com/private-cloud/3.2/anypoint-monitoring). The following limitations apply
when using Anypoint Monitoring with Anypoint Platform PCE.

#### Enhanced API Analytics Monitoring Limits

- API Summary Metrics

  - Retention: 1 year

- API IP Address Metrics

  - Number of IP addresses per API per minute: limited to 20 unique IP addresses.

  - Retention: 1 hour

- API Endpoint Metrics

  - Number of endpoints per API per minute: limited to 100 unique endpoints

  - Retention: 1 hour

#### Application Monitoring Limits

- Number of endpoints per application per minute: 5 unique endpoints

- Number of client IP addresses per application per minute: 5 unique endpoints

#### Custom Metrics

- Up to 10000 alerts

- System performs

#### Advanced Alert Limits

- Up to 20 alerts

#### Performance Limits

- Number of Mule instances: 3000

- Number of applications: 12000

- Number of application replicas: up to 12000. An application can run on multiple Mule instances in
  a server group or cluster.

- Number of APIs: up to 120000

- Number of custom metrics: 50

#### Examples of Supported Parameters

- 6000 applications, each with 1 extra replica corresponds to 12000 application replicas

- 2000 applications, each with 6 extra replicas corresponds to 12000 application replicas

- 12000 applications, with no replicas corresponds to 12000 application replicas

#### Hardware Requirements

- 3 Nodes

- CPU: 32 cores

- Memory: 128 GB

- Disk requirements:

  - 4TB InfluxDB volume for each AMV node

  - 500 GB Logstash volume per AMV node

  - 500 GB insight-cassandra-meld volume per AMV node

  - IOPS: 1500 IPS per volume (1 voolume each for Influx, logstash, and insight-cassandra-meld)

  - Network: 10 GB/second

#### License Requirements

- The Influx Enterprise license (included in the Anypoint Monitoring subscription) is required to
  enable monitoring.

### Anypoint Visualizer

Anypoint Platform PCE does not the support the following Anypoint Visualizer features:

- List of applications

  If an application does not use Anypoint Monitoring, Anypoint Visualizer cannot track it on
  Anypoint Platform PCE.

- Policy visualization

## See Also

- [Anypoint Monitoring](https://docs.mulesoft.com/private-cloud/3.2/anypoint-monitoring)

- [Anypoint Visualizer](https://docs.mulesoft.com/visualizer/)