Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

Version 1 Next »

Customers that use Amazon Connect will be hosting the AWS-Managed Opensearch domain on their AWS.

This document would show the sizing recommendations based on number of active agents on their Amazon Connect instance.

Please note though, that the number of active agents is not the only factor for Opensearch domain CPU/Memory load. Dashboard complexity

<1000 Agents (Standard Deployment)

This the default sizing typically used for new customers.

  • Standard

    • Master Nodes: None

    • Data Nodes

      • 1 Data Node

      • Size: m6g.large

  • If customer requires HA/Multi-AZ for their deployment

    • This configuration would be able to handle loss of an AZ

    • Master Nodes

      • 2 Master Nodes

      • Size: c6g.large

    • Data Nodes

      • 2 Data Nodes

      • Size: m6g.large

1000-2000 Agents

  • Standard

    • Master Nodes: None

    • Data Nodes

      • 1 Data Node

      • Size: m6g.xlarge

  • If customer requires HA/Multi-AZ for their deployment

    • This configuration would be able to handle loss of an AZ

    • Master Nodes

      • 2 Master Nodes

      • Size: c6g.large

    • Data Nodes

      • 2 Data Nodes

      • Size: m6g.xlarge

1000-2000 Agents

  • Standard

    • Master Nodes: None

    • Data Nodes

      • 1 Data Node

      • Size: m6g.xlarge

  • No labels