Fix AWS EKS cluster creating docs

All comments regarding CNI is outdated, resulting cluster would have
version of CNI 1.5 which is bigger than 1.2 required.

site/content/en/docs/Installation/_index.md

@@ -24,7 +24,7 @@ In this quickstart, we will create a Kubernetes cluster, and populate it with th
 ## Usage Requirements
 
 - Kubernetes cluster version 1.11
-    - [Minikube](https://github.com/kubernetes/minikube), [Kind](https://github.com/kubernetes-sigs/kind), [Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine/), 
+    - [Minikube](https://github.com/kubernetes/minikube), [Kind](https://github.com/kubernetes-sigs/kind), [Google Kubernetes Engine](https://cloud.google.com/kubernetes-engine/),
       [Azure Kubernetes Service](https://azure.microsoft.com/en-us/services/kubernetes-service/) and [Amazon EKS](https://aws.amazon.com/eks/) have been tested
     - If you are creating and managing your own Kubernetes cluster, the
     [MutatingAdmissionWebhook](https://kubernetes.io/docs/admin/admission-controllers/#mutatingadmissionwebhook-beta-in-19), and
@@ -241,21 +241,25 @@ minikube start --kubernetes-version v1.12.10 --vm-driver virtualbox
 
 Create your EKS instance using the [Getting Started Guide](https://docs.aws.amazon.com/eks/latest/userguide/getting-started.html).
 
-### Ensure VPC CNI 1.2 is Running
-
-EKS does not use the normal Kubernetes networking since it is [incompatible with Amazon VPC networking](https://www.contino.io/insights/kubernetes-is-hard-why-eks-makes-it-easier-for-network-and-security-architects). 
-
-In a console, run this command to get your current cni version
-
-```bash
-kubectl describe daemonset aws-node --namespace kube-system | grep Image | cut -d "/" -f 2
+Possible steps are the following:
+1. Create new IAM role for cluster management.
+1. Run `aws configure` to authorize your `awscli` with proper `AWS Access Key ID` and `AWS Secret Access Key`.
+1. Create an example cluster:
 ```
-Output should be `amazon-k8s-cni:1.2.0` or newer. To upgrade to version 1.2, run the following command.
-
-```bash
-kubectl apply -f https://raw.githubusercontent.com/aws/amazon-vpc-cni-k8s/master/config/v1.2/aws-k8s-cni.yaml
+eksctl create cluster \
+--name prod \
+--version 1.12 \
+--nodegroup-name standard-workers \
+--node-type t2.medium \
+--nodes 3 \
+--nodes-min 3 \
+--nodes-max 4 \
+--node-ami auto
 ```
 
+
+> Note: EKS does not use the normal Kubernetes networking since it is [incompatible with Amazon VPC networking](https://www.contino.io/insights/kubernetes-is-hard-why-eks-makes-it-easier-for-network-and-security-architects).
+
 ### Follow Normal Instructions to Install
 
 Continue to [Installing Agones](#installing-agones).
@@ -272,7 +276,7 @@ You can use either [Azure Cloud Shell](https://docs.microsoft.com/azure/cloud-sh
 
 If you are using Azure CLI from your local shell, you need to login to your Azure account by executing the `az login` command and following the login procedure.
 
-Here are the steps you need to follow to create a new AKS cluster (additional instructions and clarifications are listed [here](https://docs.microsoft.com/azure/aks/kubernetes-walkthrough)): 
+Here are the steps you need to follow to create a new AKS cluster (additional instructions and clarifications are listed [here](https://docs.microsoft.com/azure/aks/kubernetes-walkthrough)):
 
 ```bash
 # Declare necessary variables, modify them according to your needs