fix: clarify custom AMI usage with eksctl (coder#848)

bpmct · web-flow · commit bd79e3738682 · 2022-02-14T13:40:04.000-06:00
diff --git a/setup/kubernetes/aws.md b/setup/kubernetes/aws.md
@@ -180,14 +180,18 @@ as a workspace deployment option, you'll need to
    managedNodeGroups:
      - name: coder-node-group
        amiFamily: Ubuntu2004
-       ami: <your Ubuntu 20.04 AMI ID>
+       # Custom AMIs can be used instead of amiFamily
+       # ami: <your Ubuntu 20.04 AMI ID>
        instanceType: <instance-type>
        minSize: 1
        mazSize: 2
        desiredCapacity: 1
-       overrideBootstrapCommand: |
-      #!/bin/bash -xe
-      sudo /etc/eks/bootstrap.sh --apiserver-endpoint '' --b64-cluster-ca 'LS0tLS1...LS0tCg==' '<cluster-name>'
+       # Uncomment "overrideBootstrapCommand" if you are using a custom AMI
+       # and replace YOUR_CLUSTER_CA with "certificate-authority-data" from
+       # your kubeconfig
+       # overrideBootstrapCommand: |
+       #  #!/bin/bash -xe
+       #  sudo /etc/eks/bootstrap.sh --apiserver-endpoint '' --b64-cluster-ca 'YOUR_CLUSTER_CA' '<cluster-name>'
    ```
 
 > [See here for a list of EKS-compatible Ubuntu AMIs](https://cloud-images.ubuntu.com/docs/aws/eks/)
