<p>I think the instance class is going to vary based on the kind of workloads you run. You might start out with X but next thing you know your running a bunch of random stuff. You can always run a cluster of different instance classes and then have the scheduler schedule your workloads to the right instance. </p>

<p>M5 and t3 are Nitro based instances. They have a big list of benefits <a href="https://aws.amazon.com/ec2/nitro/" rel="nofollow noreferrer">https://aws.amazon.com/ec2/nitro/</a> . My favorite being that I can log into those instances using my AWS account with no SSH keys. </p>

<p>My personal workloads are more memory-hungry. Since you can't throttle memory like cpu you should factor that in when sizing your instances. I think fewer denser instances are probably more favorable than lots of small instances. </p>

<p>I'm not sure what your use case is for running nginx rever proxies but you may want to look into kubernetes ingress. </p>

CC BY-SA 4.0
2020-05-26T12:12:02.330Z
2020-05-26T12:12:02.330Z
Levi
<p>Hi We are deploying a fairly standard multiple purpose (data replication workers and some nginx web proxies) in an EKS cluster, and wondering what EC2 instance class people recommend for this workload. Probably would look at a base of 3 x (M5|T3|..).large instances with the ability to scale it up. I wonder if others have experience with comparing the compute types.</p>

<amazon-web-services><kubernetes>
Best AWS EC2 instance class for general Kubernetes cluster
silverdagger
# Best AWS EC2 instance class for general Kubernetes cluster

(Asked by: username_0 on 2020-05-26)

Hi We are deploying a fairly standard multiple purpose (data replication workers and some nginx web proxies) in an EKS cluster, and wondering what EC2 instance class people recommend for this workload. Probably would look at a base of 3 x (M5|T3|..).large instances with the ability to scale it up. I wonder if others have experience with comparing the compute types.

**Tags:** amazon-web-services, kubernetes


---

## 1 answers

### Answer by username_1 on 2020-05-26. Score: 2 | Accepted answer

I think the instance class is going to vary based on the kind of workloads you run. You might start out with X but next thing you know your running a bunch of random stuff. You can always run a cluster of different instance classes and then have the scheduler schedule your workloads to the right instance.

M5 and t3 are Nitro based instances. They have a big list of benefits <https://aws.amazon.com/ec2/nitro/> . My favorite being that I can log into those instances using my AWS account with no SSH keys.

My personal workloads are more memory-hungry. Since you can't throttle memory like cpu you should factor that in when sizing your instances. I think fewer denser instances are probably more favorable than lots of small instances.

I'm not sure what your use case is for running nginx rever proxies but you may want to look into kubernetes ingress.


---

