diff --git a/website/config.yaml b/website/config.yaml
index 62b0da37d6e4..05fd37b3b084 100644
--- a/website/config.yaml
+++ b/website/config.yaml
@@ -67,6 +67,7 @@ params:
         icon: fab fa-slack
         desc: 'Chat with us on Slack in the #aws-provider channel'
   latest_release_version: v0.31.1
+  latest_k8s_version: 1.28
   versions:
     - v0.31
     - v0.30
diff --git a/website/content/en/preview/faq.md b/website/content/en/preview/faq.md
index f951643f7027..66ea2c7d50fd 100644
--- a/website/content/en/preview/faq.md
+++ b/website/content/en/preview/faq.md
@@ -176,10 +176,10 @@ Yes, see the [KubeletConfiguration Section in the NodePool docs]({{<ref "./conce
 The difference between the Core and Full variants is that Core is a minimal OS with less components and no graphic user interface (GUI) or desktop experience.
 `Windows2019` and `Windows2022` AMI families use the Windows Server Core option for simplicity, but if required, you can specify a custom AMI to run Windows Server Full.
 
-You can specify the [Amazon EKS optimized AMI](https://docs.aws.amazon.com/eks/latest/userguide/eks-optimized-windows-ami.html) with Windows Server 2022 Full for Kubernetes 1.28 by configuring an `amiSelector` that references the AMI name.
-```
+You can specify the [Amazon EKS optimized AMI](https://docs.aws.amazon.com/eks/latest/userguide/eks-optimized-windows-ami.html) with Windows Server 2022 Full for Kubernetes {{< param "latest_k8s_version" >}} by configuring an `amiSelector` that references the AMI name.
+```yaml
 amiSelectorTerms:
-    - name: Windows_Server-2022-English-Full-EKS_Optimized-1.28*
+    - name: Windows_Server-2022-English-Full-EKS_Optimized-{{< param "latest_k8s_version" >}}*
 ```
 
 ## Deprovisioning
diff --git a/website/content/en/preview/getting-started/getting-started-with-karpenter/_index.md b/website/content/en/preview/getting-started/getting-started-with-karpenter/_index.md
index 924e9a74577d..abde781ae826 100644
--- a/website/content/en/preview/getting-started/getting-started-with-karpenter/_index.md
+++ b/website/content/en/preview/getting-started/getting-started-with-karpenter/_index.md
@@ -41,10 +41,11 @@ authenticate properly by running `aws sts get-caller-identity`.
 
 ### 2. Set environment variables
 
-After setting up the tools, set the Karpenter version number:
+After setting up the tools, set the Karpenter and Kubernetes version:
 
 ```bash
 export KARPENTER_VERSION={{< param "latest_release_version" >}}
+export K8S_VERSION={{< param "latest_k8s_version" >}}
 ```
 
 Then set the following environment variable:
diff --git a/website/content/en/preview/getting-started/getting-started-with-karpenter/scripts/step02-create-cluster.sh b/website/content/en/preview/getting-started/getting-started-with-karpenter/scripts/step02-create-cluster.sh
index 675aca0bebf1..32619fa12871 100755
--- a/website/content/en/preview/getting-started/getting-started-with-karpenter/scripts/step02-create-cluster.sh
+++ b/website/content/en/preview/getting-started/getting-started-with-karpenter/scripts/step02-create-cluster.sh
@@ -12,7 +12,7 @@ kind: ClusterConfig
 metadata:
   name: ${CLUSTER_NAME}
   region: ${AWS_DEFAULT_REGION}
-  version: "1.28"
+  version: "${K8S_VERSION}"
   tags:
     karpenter.sh/discovery: ${CLUSTER_NAME}