Given that current AMI images for EKS nodes already run ssm-agent internally, it would suffice to add to the node's role the AmazonSSMManagedInstanceCore managed policy in order for the agent to check in to SSM and allow connecting to the instance without the need to add the SSMAgentAddOn (which runs a daemonset).
Proposed Solution
Create a node role and add the AmazonSSMManagedInstanceCore policy.
Acknowledgements
[x] I may be able to implement this feature request
Describe the feature
Given that current AMI images for EKS nodes already run ssm-agent internally, it would suffice to add to the node's role the
AmazonSSMManagedInstanceCore
managed policy in order for the agent to check in to SSM and allow connecting to the instance without the need to add the SSMAgentAddOn (which runs a daemonset).Proposed Solution
Create a node role and add the
AmazonSSMManagedInstanceCore
policy.Acknowledgements
CDK version used
2.60.0
EKS Blueprints Version
1.5.4
Node.js Version
v16.19.0