How to Reduce Your Amazon EKS Costs by Half in 15 Minutes

Overprovisioning is the top reason why teams see their cloud bills constantly growing. But choosing the best instances from the hundreds of options AWS offers is a tough call.

How to Reduce Your Amazon EKS Costs by Half in 15 Minutes

How are you supposed to know which ones will deliver the performance you need?

Fortunately, you can find solutions on the market that can do that for you.

If you’re curious about how it all works, follow my journey and see how I slashed the costs of running my containers in EKS by half using CAST AI, in 15 minutes.


I started by provisioning an e-commerce app (here) on an EKS cluster with six m5 nodes (2 vCPU, 8 GiB) on AWS EKS. I then deployed an AI engine to analyze my application and suggest some optimizations. Finally, I activated the engine and watched the system self-optimize.

The initial cluster cost was $414 per month. Within 15 minutes, in a fully automated way, the cluster cost went to $207 (a 50% reduction), by reducing six nodes to three nodes. Then, 5 minutes later, the cluster cost went down to $138 per month, using spot instances (a 66% reduction).

EKS savings with CAST AI


Get your free CAST AI Savings Report to check how much you could potentially save. It’s the best starting point for any journey into cloud cost optimization.

Step 1: Deploying my app and running the Savings Report

 I deployed my app in 6 nodes on EKS. Here’s what it looked like before – all the nodes were empty:

Deployed app in 6 nodes

The cluster was created via eksctl:

eksctl create cluster --name boutique-blog-lg -N 6 --instance-types m5.large --managed --region us-east-2

And after deployment – the green rectangles are the pods:

pods after deployment

I’m using kube-ops-view, a useful open-source project to visualize the pods.

Notice that with Kubernetes, the application’s pods (aka containers) are spread evenly across all the nodes by default. Kubernetes is a fair orchestration engine. The CPUs range between 40 and 50%.

Note: all EKS autoscalings have been disabled on purpose, as CAST AI will substitute EKS Cluster Autoscaling.

Now it’s time to connect my EKS cluster to CAST AI. I created a free account on and selected the Connect your cluster option.

Click on ‘Connect cluster’:

Connect cluster to CAST AI

CAST AI agent

I copied and ran the script successfully on my terminal (I use Lens, another free tool for this).

[email protected] ~ % curl -H "Authorization: Token  "" | kubectl apply -f -
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 2585 0 2585 0 0 2391 0 --:--:-- 0:00:01 --:--:-- 2391
namespace/castai-agent created
serviceaccount/castai-agent created created created
secret/castai-agent created
deployment.apps/castai-agent created

 The CAST AI agent went over my EKS cluster in read-only mode and generated this Savings Report:

CAST AI savings report

If I switch my six m5.large to what CAST AI recommends – three c5a.large – I could slash my bill by almost 60%. Sounds like a plan!

With Spot Instances, I can get even higher savings (66.5%).

CAST AI savings report with spot instances

Step 2: Activating the cost optimization

To get started with cost optimization, I need to add my AWS access key ID and Secret access key to the platform.

 Getting the access keys was easy. All it took was running this script:

Enable CAST AI cost optimization

Step 3: Enabling policies

I turn on all the policies available in CAST AI:CAST AI automation policies

  • CPU Policy: I tell the engine to never go above my budget. I set it up to 200 CPUs.
  • Node autoscaler: CAST AI will make a smart selection of nodes whenever I have unscheduled pods, starting with Spot Instances (if the unscheduled pods are Spot Instance-friendly) or On-Demand.
  • Node Deletion + Evictor: Evictor is a background process that continuously shrinks the cluster to the minimum number of nodes by bin-packing pods. Once a node becomes empty, it’s deleted automatically.

Evictor is a CAST AI tool that constantly looks for inefficiencies in a setup and helps to maximize savings as fast as possible. Run this command to activate Evictor:

So, I installed Evictor and set it to work. Evictor is running!

CAST AI Evictor feature

This is what Evictor in action looks like:

  1. One node (in red below) is identified as a candidate for eviction.
  2. Evictor automatically moves the pods to other nodes “bin-packing.”
  3. Once the node becomes empty, it’s deleted from the cluster.
  4. Go back to step 1.
Nodes status

One node is deleted:

Reducing number of nodes

Here are the Evictor logs:

time="2021-06-14T16:08:27Z" level=debug msg="will try to evict node \"\""
time="2021-06-14T16:08:27Z" level=debug msg="annotating (marking) node \"\" with \"\""
time="2021-06-14T16:08:27Z" level=debug msg="tainting node \"\" for eviction"
time="2021-06-14T16:08:27Z" level=debug msg="started evicting pods from a node"
time="2021-06-14T16:08:27Z" level=info msg="evicting 9 pods from node \"\""
I0614 16:08:28.831083 1 request.go:655] Throttling request took 1.120968056s, request: GET:
time="2021-06-14T16:08:44Z" level=debug msg="finished node eviction"

And now the second and third nodes were evicted – 3 nodes remain:

Active nodes after optimization

After about 10 minutes, Evictor deleted 3 nodes and left 3 nodes running. Note that CPUs are now at a much healthier 80% rate.

The cost of this cluster is now $207.36 per month – half the initial cost of $414 per month.

I managed to achieve 80% of the projected savings. This is what I saw in my CAST AI dashboard: 

CAST AI dashboard

Advanced savings

Step 4 (optional): Moving my app to new optimized nodes

Steps 1, 2, and 3 are fully automated. CAST AI gradually shrinks the cluster by eliminating waste and overprovisioning. It does so by bin-packing pods and emptying nodes one by one. From that moment, the cluster is optimized and Evictor will continuously look for further optimization opportunities over time.

Step 4 is an advanced optional step where CAST AI actively replaces the current nodes with more optimized nodes, such as Spot Instances. The concept is fairly simple: CAST AI cordons the cluster, drains nodes, and replaces them with more optimized nodes.

The nodes are cordoned:

Cordoned nodes

The first two nodes are drained, and the AI engine selects the most appropriate instances type for these nodes. This is what I saw in my CAST AI dashboard:

CAST AI setup progress

As you can see, my cluster now has only two nodes and costs $138 per month. It’s hard to imagine that I started out with a monthly EKS bill of $414.72!


Moving from a non-optimized setup to a fully-optimized one was a breeze. CAST AI analyzed my setup, found opportunities for savings, and swiftly optimized my cluster in 15 minutes. I cut my EKS bill by half in 15 minutes, from $414 to $207.

Then, I activated advanced savings by asking CAST AI to replace nodes with more optimized nodes and achieved further savings, ending up with a $138 bill.

EKS savings with CAST AI

Run the free CAST AI Savings Report to check how much you could potentially save. It’s the best starting point for any journey into cloud cost optimization.

  • Blog
  • How to Reduce Your Amazon EKS Costs by Half in 15 Minutes

Leave a reply

Inline Feedbacks
View all comments
2021-07-19 12:54 PM

interesting case study, efficient autoscaling

2021-07-20 12:04 PM

Evictor looks promising

2021-07-21 11:15 PM

so Evictor basically removes excessive nodes?

Vidmantas CAST AI
2021-07-23 10:45 AM
Reply to  eks

Yes, that is correct.

2021-07-22 2:30 PM

nice to see a real-life example

Vidmantas J.
2021-07-27 12:54 PM
Reply to  cool

Hi, you may also like to check out our case studies with real clients. You can find this here:

2021-08-11 7:42 AM

This kubeops view is major discovery for me, visualizing the clusters and pods, loved that!

David Kurk
2021-08-11 8:38 AM

Even though the first stage looks like just simply shrinking the pods in to fever clusters, the autoscaling and spot instance replacement looks promising, I’ll give it a shot with my team later on this week

2021-08-12 9:59 AM

I liked how the evictor is such a simple feature, but so needed that we sometimes dont think about how much it could save..

2021-08-12 10:09 AM

Running this script in my cluster doesn’t seem a very great idea, can I have a look at it before running it?

Recent posts