The preparations described below are required to install  on Amazon Web Services using Helm charts and Docker images. Read through the steps below and follow each step before installing. This pre-installation is normally not needed to be done again, once you have done it.

...

If you do not have any existing setup or starting with fresh account in AWS, Please refer the Setup (3.2) and modify accordingly to match with your production environment.

Initialization

1. Use the aws configure command to setup your AWS credentials.

   Code Block
   $ aws configure aws_access_key_id = <access key id> aws_secret_access_key = <secret access key> output = json region = <region where you have your EKS cluster>

   
   

2. Update kubeconfig context to access your eks cluster.

   Code Block
   $ aws eks update-kubeconfig --name <name_of_your_cluster> To set the default cluster, used as the example in this installation: $ aws eks update-kubeconfig --name mz-eks

   
   

   Note
   title Note!
   This step can be omitted if you do not have an existing eks cluster or if you will be using the Openshift Cluster. If you do not have an eks cluster installed, you can create one in the Setup (3.2).

   
   

3. verify that your are in right cluster and can list the nodes and other resources

   Code Block
   $ kubectl get node $ kubectl get all

   
   

   Note
   title Note!
   This step can be omitted if you do not have an existing eks cluster or if you will be using the Openshift Cluster. If you do not have an eks cluster installed, you can create one in the Setup (3.2).

   
   

4. To verify that the Helm CLI is initialized, run the following command:
   

   Code Block
   $ helm version -c

   Output example:

   Code Block
   $ helm version -c version.BuildInfo{Version:“v3.2.1”, GitCommit:“fe51cd1e31e6a202cba7dead9552a6d418ded79a”, GitTreeState:“clean”, GoVersion:“go1.13.10"}

   
   

...