Instance Types Supported for SBC SWe in AWS

• M4 instance for Passthrough and M4 does not support Transcoding because of weaker CPU
• C4 instance for Transcode and Crypto call scenarios
• Largest instance type supported is c4.4xlarge

All instances underlying Hypervisor is Xen and Networking is SRIOV.

• M4 instance for Passthrough and M4 does not support Transcoding because of weaker CPU
• C4 instance for Transcode and Crypto call scenarios
• Largest instance type supported is c4.8xlarge

All instances underlying Hypervisor is Xen and Networking is SRIOV.

• M5 and C5 instances are cheaper compared to M4 and C4 instances of previous generation
• M5 instance for Passthrough
• C5 instance for Transcode and Crypto call scenarios

Note: If you change the instance type from M4 to M5 or C4 to C5 you will need to contact Ribbon for appropriate licensing.

• G3 instances for Transcode only workloads/call scenarios
• Largest instance type supported is c5.9xlarge

Newer generation M5 and C5 instance underlying Hypervisor is KVM Nitrox and Networking is ENA.

"m5.xlarge",
"m5.2xlarge",
"c5.2xlarge",
"c5.4xlarge",
"c5.9xlarge",
"c5n.2xlarge",
"c5n.4xlarge",
"c5n.9xlarge",
"g3.4xlarge",
"p3.2xlarge",

• Ribbon recommends m5.xlarge or higher instance type if this instance type is available in your zone for passthrough.
• Use c5.2xlarge instance type or higher to handle Transcode or Crypto call scenarios

SBC and HFE:

• Ribbon recommends m5.xlarge or higher instance type if this instance type is available in your zone for passthrough.
• Use c5.2xlarge instance type or higher to handle Transcode or Crypto call scenarios.

HFE consideration:

• P3 and G3 instances are GPU-enabled, thus are not used by HFE. To reduce costs,  other mappings are available to G3 and P3.