How EMP Works

EMP consolidates your EKS worker nodes on a pool of EC2 metal, replacing some or all existing workers with Elastic VMs (EVMs) running on AWS metal.

New EVM workers will be created based on Kubernetes scheduling requests, but they will be placed on existing pool of metal, till the metal nodes start running out of capacity.

So the workers may not be fully utilized, but underlying metal will be. 
And this is what you will pay for. 

Scale & Rebalance with Live Migration

EMP monitors EVM resource utilization and dynamically scales AWS metal instances only when existing pool or metal is running out of utilized capacity.

EMP also auto rebalances EVMs across the bare metal pool, live migrating EVMs under the hood. So when existing metal nodes 
start to utilize all of their capacity, EMP will rebalance EVMs to other metal nodes.

Diagram: EMP's live migation demonstrates how Bare Metal pods are scaled and rebalanced

EMP vs Existing Tools

OutcomesEMPKarpenterCloudHealthCloudabilityCloudZeroKubecost
Improve resource efficiency using over-provisioningIcon of a checkmark
Rebalance and consolidate without pod disruptionIcon of a checkmark
Eliminate changes to pod requests and limitsIcon of a checkmark
Optimize usage via bin packingIcon of a checkmarkIcon of a checkmark
Cost visibilityIcon of a checkmarkIcon of a checkmarkIcon of a checkmarkIcon of a checkmarkIcon of a checkmark
Resource taggingIcon of a checkmarkIcon of a checkmarkIcon of a checkmark
Cost allocationIcon of a checkmarkIcon of a checkmarkIcon of a checkmarkIcon of a checkmark

Achieve over 70% utilization with EMP

Comparison graphs showing EKS vs EKS with EMP. EKS graph shows 49% allocated, 34% utilized, and 17% unallocated vs the EKS with EMP graph which shows 12% allocated, 70% utilized, and 18% unallocated.
Scroll to Top