AWS offers the Amazon Elastic Kubernetes Service (EKS) in the below variants:

1. Classic EKS variant with self-managed worker nodes (https://docs.aws.amazon.com/eks/latest/userguide/worker.html). In this variant, the customer has to completely manage the EC2 instances for the Kubernetes data plane on which the Pods run.
2. EKS variant with managed node groups (https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html). Modified version of 1 at which AWS takes over large parts of the management of the EC2 instances for the Kubernetes Data Plane.
3. EKS on Fargate (https://docs.aws.amazon.com/eks/latest/userguide/fargate.html). As a customer, you don't have to manage the EC2 instances in the cluster yourself. You only specify the Pods here (e.g. with their memory requirements). AWS automatically allocates the underlying instances. As a customer, you have no direct access to these instances and you do not see them as such in your own AWS account.

Based on the reply on the other post 

https://support.pega.com/question/pega-amazon-elastic-kubernetes-service-eks-support

Based on the reply from Brett Allen from Pega, it is mentioned that Pega does not support AWS Fargate and the option to use managed node group is not tested but may work.

We are planning to use Option 2. Since the above post is over 3 years ago, could the team please help update if there are any changes to the above.