You can use this as a reference or modify according to your infrastructure standards, see Pre-installation (4.0) page for the AWS service list required for MZ installation in AWS.

Working With the Infrastructure Template

• Get the latest infrastructure templates from Release Information.
  
  Download the template file and unzip it to a new folder.

  Code Block
  $ cd <your work folder> $ tar xzvf mz10-aws.tgz

For EKS Cluster

Set up the VPC and EKS Cluster

The default value for the cluster name is mz-eks and region is eu-west-1

1. Go to the eksctl folder in the unzipped contents.
   Update the following fields in the mz-eks.yaml file:

   See https://github.com/weaveworks/eksctl for information about more parameters that can be used in the eksctl template

   Code Block
   Metadata name (cluster name, default to mz-eks) aws region (default to eu-west-1) Worker Nodes instanceType (change the instant type to match your application load) minSize, maxSize and desiredSize (if you wish to have more nodes running)

2. Execute the following commands to start the creation of the EKS cluster

   Code Block
   $ eksctl create cluster -f mz-eks.yaml --kubeconfig=./kubeconfig $ export KUBECONFIG=`pwd`/kubeconfig You should be able to run any kubectl commands from now on

Create Resources Required for  with EKS

1. Go to the terraform folderand copy the terraform.tfvars.example to terraform.tfvars.

   Code Block
   $ cp terraform.tfvars.example terraform.tfvars

2. Retrieve the following values from AWS Console and fill in the parameters in terraform.tfvars.

   terraform.tfvars	Where to get the values
   aws_account_id	From AWS Console Go to My Account page and you will see the Account Id under Account Settings
   aws_region	Follow as per the value configured in mz-eks.yaml Default is eu-west-1
   cluster_name	Follow as per the value configured in mz-eks.yaml Default is mz-eks
   db_password	Use a secure password for the platform database. Minimum 10 characters.
   domain domain_zone_id	From AWS Console On the Route 53 page, find your existing Hosted Zone and copy the Hosted Zone ID and Domain Name.
   vpc_id	From AWS Console On the VPC Service page, find the vpc name eksctl-mz-eks-cluster/VPC and copy the VPC ID.

   Code Block

   # ____ _____ _____ _____ _ _ _____ ____ _____ # / ___|| ____|_ _| |_ _| | | | ____/ ___|| ____|_ # \___ \| _| | | | | | |_| | _| \___ \| _| (_) # ___) | |___ | | | | | _ | |___ ___) | |___ _ # |____/|_____| |_| |_| |_| |_|_____|____/|_____(_) # The below values must be set explicitly in order for the setup to work correctly. vpc_id = "vpc-xxxxxxxxxxxxxxxxx" aws_region = "eu-west-1" aws_account_id = "" # cluster_name.domain will be the final domain name cluster_name = "mz-eks" domain = "example.com" # Route 53 Hosted Zone ID # This should be the Zone ID of the Domain above. Ie. that domain must already exist in Route 53. # We'll insert the nameservers of the new domain name "cluster-name.domain" as a NS record in domain's hosted zone. domain_zone_id = "" # Password to the database. db_password = ""

3. Run the following commands:

   Code Block
   $ terraform init $ terraform plan $ terraform apply

4. Save the output from terraform for the next step.

Installing AWS Helpers

1. Run the following commands by replacing the placeholders with values from the terraform output.

   Placeholder	Value from terraform output
   <region>	Follow as per the value configured in cluster.yaml Default is eu-west-1
   <eks_domain_zone_name>	eks_domain_zone_name
   <eks_domain_zone_id>	eks_domain_zone_id
   <efs id>	efs_id
   <cluster_name>	Follow as per the value configured in cluster.yaml Default is mz-eks

2. See https://github.com/kubernetes-sigs/aws-efs-csi-driver for information on how to install Amazon EFS CSI Driver as follows:

   Code Block
   $ helm repo add aws-efs-csi-driver https://kubernetes-sigs.github.io/aws-efs-csi-driver/ $ helm repo update $ helm upgrade --install aws-efs-csi-driver --namespace <namespace> aws-efs-csi-driver/aws-efs-csi-driver

3. If you need to dynamically provision persistent volume claim (PVC) through Amazon EFS access points, see https://github.com/kubernetes-sigs/aws-efs-csi-driver/tree/master/examples/kubernetes/dynamic_provisioning for information on how to install the storage class.

   Below is an example of a storage class yaml setup:

   Code Block
   kind: StorageClass apiVersion: storage.k8s.io/v1 metadata: name: aws-efs provisioner: efs.csi.aws.com parameters: provisioningMode: efs-ap fileSystemId: <efs id> directoryPerms: "700"

4. See https://github.com/bitnami/charts/tree/master/bitnami/external-dns for information on how to install External DNS as follows:

   Code Block
   $ helm repo add bitnami https://charts.bitnami.com/bitnami $ helm repo update $ helm upgrade --install external-dns bitnami/external-dns \ -n <namespace> \ --set provider=aws \ --set aws.zoneType=public \ --set txtOwnerId=<eks_domain_zone_id> \ --set "domainFilters[0]=<eks_domain_zone_name>" \ --set policy=sync

5. See https://github.com/aws/eks-charts/tree/master/stable/aws-load-balancer-controller for information on how to install AWS Load Balancer Controller as follows:

$ helm repo add eks https://aws.github.io/eks-charts
$ helm repo update
$ helm install aws-load-balancer-controller eks/aws-load-balancer-controller \
-n <namespace> \
--set clusterName=<cluster_name>

6. Create a custom values yaml and populate it with the following information, which will be used in NGINX ingress controller installation:

   ingress-nginx-values.yaml

   Code Block
   controller: scope: enabled: true admissionWebhooks: enabled: false metrics: enabled: false serviceMonitor: enabled: false ingressClassResource: name: nginx enabled: true default: false controllerValue: "k8s.io/ingress-nginx"

$ helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
$ helm repo update
$ helm install <release name> ingress-nginx/ingress-nginx --version <NGINX helm chart version> -f ingress-nginx-values.yaml -n <namespace>

oc adm policy add-scc-to-user nonroot -z <service account name> -n <namespace>

$ helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
$ helm repo update
$ helm install <release name> ingress-nginx/ingress-nginx --version <NGINX helm chart version> -f ingress-nginx-values.yaml -n <namespace>