<p>Our EKS cluster is terraform managed and was specified with EC2 Launch Template as terraform resource. Our aws_eks_node_group includes Launch template section as shown below.</p>
<pre><code>resource &quot;aws_eks_node_group&quot; eks_node_group&quot; {
.........................
..........................
  launch_template {
    id      = aws_launch_template.eksnode_template.id
    version = aws_launch_template.eksnode_template.default_version
    name    = aws_launch_template.eksnode_template.name
  }
}
</code></pre>
<p>However, after a while, EKS self-deployed the new Launch Template and linked it to the relevant auto-scaling group.</p>
<ol>
<li>Why this has happened at the first place and how to avoid it in the future?</li>
<li>How can we link the customer managed Launch Template to EKS Autoscaling Group via terraform again? I tried changing the name or version of the launch template, but it is still using one created by EKS (self-managed)</li>
</ol>

<ol>
<li></li>
</ol>
<blockquote>
<p>The Amazon EKS API creates this launch template either by <strong>copying</strong> one you provide or by creating one automatically with default values in your account.</p>
</blockquote>
<ol start="2">
<li></li>
</ol>
<blockquote>
<p>We don't recommend that you modify auto-generated launch templates.</p>
</blockquote>
<p>(<a href="https://docs.aws.amazon.com/eks/latest/userguide/launch-templates.html" rel="nofollow noreferrer">source</a>)</p>
