diff --git a/modules/eks/cluster/CHANGELOG.md b/modules/eks/cluster/CHANGELOG.md
index 03371cb02..085783949 100644
--- a/modules/eks/cluster/CHANGELOG.md
+++ b/modules/eks/cluster/CHANGELOG.md
@@ -1,3 +1,9 @@
+## Release 1.455.1
+
+Components PR [#1057](https://github.com/cloudposse/terraform-aws-components/pull/1057)
+
+Fixed "Invalid count argument" argument when creating new cluster
+
 ## Release 1.452.0
 
 Components PR [#1046](https://github.com/cloudposse/terraform-aws-components/pull/1046)
diff --git a/modules/eks/cluster/main.tf b/modules/eks/cluster/main.tf
index 80cbdc86c..c9677bb9b 100644
--- a/modules/eks/cluster/main.tf
+++ b/modules/eks/cluster/main.tf
@@ -55,7 +55,7 @@ locals {
   # If Karpenter IAM role is enabled, give it access to the cluster to allow the nodes launched by Karpenter to join the EKS cluster
   karpenter_role_arn = one(aws_iam_role.karpenter[*].arn)
 
-  linux_worker_role_arns = compact(concat(
+  linux_worker_role_arns = local.enabled ? concat(
     var.map_additional_worker_roles,
     # As of Karpenter v0.35.0, there is no entry in the official Karpenter documentation
     # stating how to configure Karpenter node roles via EKS Access Entries.
@@ -64,8 +64,8 @@ locals {
     # does not work if they are Windows nodes, but at the moment, this component
     # probably has other deficiencies that would prevent it from working with Windows nodes,
     # so we will stick with just saying Windows is not supported until we have some need for it.
-    [local.karpenter_role_arn],
-  ))
+    local.karpenter_iam_role_enabled ? [local.karpenter_role_arn] : [],
+  ) : []
 
   # For backwards compatibility, we need to add the unmanaged worker role ARNs, but
   # historically we did not care whether they were LINUX or WINDOWS.