Instance types and capacities for an AWS deployment

Last Updated : Aug 04, 2025 |
Prolog information
Metadata
Keywords:

Instance types

The following table lists the minimum resources required for each CMS deployment size.
When selecting an instance type for a CMS deployment, ensure that it meets or exceeds the minimum resource requirements. These resources are necessary to support the capacities described in the table following the instance types.
Important:
  • The resource requirements do not match the instance types offered by Amazon. Deploy CMS on an AWS instance type that meets or exceeds the minimum resource requirements.
  • Avoid downsizing the resource allocation, as it can impact CMS performance. CMS is a read and write-intensive application. Avaya recommends using the EBS-optimized storage from Amazon.
Server type
Small
Medium
Large
AWS Instance Type
m4.large
m5.large
m4.2xlarge
m5.2xlarge
m4.4xlarge
m5.4xlarge
AWS vCPU
2
8
16
AWS RAM (GB)
8
16
64
Hard Disk Drive (GB)
800
1200
1800
NICs
3
4
4
  • The m4.large and m5.large instance types offer moderate network performance. For high network performance, use m4.2xlarge or m5.2xlarge. Consistent network performance is essential to maintain fast refresh rates for reporting.
  • The m4.2xlarge, m5.2xlarge, m4.4xlarge, and m5.4xlarge instance types provide more CPU and memory than required for small configurations. When selecting an instance type, evaluate the trade-offs between network performance and instance cost.

Capacities

The AWS instance types listed above support the capacities shown in the following table:
Use this table to determine the appropriate configuration for your deployment.
  • Select the configuration size that provides your required capacities.
  • If any capacity requires a larger configuration, use the larger configuration option.
    • For example, if you need 100000 agent skill pairs but your peak busy-hour call volume is 200000, select the medium configuration.
Parameter
Small
Medium
Large
Peak busy-hour call volume
30000
200000
400000
Concurrent CMS Supervisor sessions1
50
200
2999
Concurrent agents
500
5000
10000
Third-party software
3
3
3
Agent skill pairs
100000
200000
800000 2
Reports per CMS Supervisor session
3
5
10 3
Report elements 4
5
5
12
Percentage of supervisors that can run reports with a three-second refresh rate
10%
50%
100%
Active agent traces
250
1000
5000
Internal Call History (ICH) records - per 20 minutes
4000
4000
4000
External Call History (ECH) records - per 20 minutes
10000
60000
300000
  1. This value is the total number of active CMS Supervisor PC Client and Web Client sessions.
  2. For actual capacity details, see Avaya Call Management System Overview and Specification.
  3. For actual capacity details, see Avaya Call Management System Overview and Specification.
  4. For a definition of Report elements, see Avaya Call Management System Overview and Specification.