diff --git a/docs/operations/images.md b/docs/operations/images.md
index 28611e0938..305bdc8390 100644
--- a/docs/operations/images.md
+++ b/docs/operations/images.md
@@ -8,7 +8,7 @@ For AWS, you should set the `image` field in one of the following formats:
 * `ami-abcdef` - specifies an image by id directly (image id is precise, but ids vary by region)
 * `<owner>/<name>` specifies an image by its owner's account ID  and name properties
 * `<alias>/<name>` specifies an image by its [owner's alias](#owner-aliases) and name properties
-* `ssm:<ssm_parameter>` specifies an image through an SSM parameter (kOps 1.26+)
+* `ssm:<ssm_parameter>` specifies an image through an SSM parameter (kOps 1.25.3+)
 
 ```yaml
 image: ami-00579fbb15b954340
diff --git a/docs/tutorial/working-with-instancegroups.md b/docs/tutorial/working-with-instancegroups.md
index 792e5de065..48a8550613 100644
--- a/docs/tutorial/working-with-instancegroups.md
+++ b/docs/tutorial/working-with-instancegroups.md
@@ -194,7 +194,7 @@ using preemptible/spot instances you might be waiting for a long time.
 
 ## Fetching images via AWS SSM (AWS Only)
 
-{{ kops_feature_table(kops_added_default='1.26') }}
+{{ kops_feature_table(kops_added_default='1.25.3') }}
 
 If you are using AWS, you can dynamically fetch instance group images from an AWS SSM Parameter. kOps will automatically fetch SSM Parameter and lookup the AMI ID on every `kops update cluster` run. This is useful if you often update your images and don't want to update your instance group configuration every time. Your SSM Parameter must start with `ssm:` and contain the full path of the SSM Parameter.