feat: expose EKS cluster primary security group ID#236
Merged
Conversation
Expose the EKS primary security group ID (auto-created by EKS) which is attached to all nodes and pod ENIs. This is needed for creating ingress rules that allow NLB traffic to reach pods when using IP target type.
sebastiancorrea81
approved these changes
Feb 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
eks_cluster_primary_security_group_idoutput to the EKS module wrappereks_cluster_security_group_idonly exposes the additional SG managed by Terraform, which is NOT attached to pod ENIsContext
When using NLBs with IP target type (Gateway API + ALB controller), traffic goes directly to pod IPs. The ENIs holding those IPs only have the primary cluster SG, not the additional one. Without this output, consumers cannot create ingress rules on the correct SG to allow NLB health checks and traffic to reach pods.
Test plan
module.eks.cluster_primary_security_group_idis exposed by the upstream terraform-aws-eks moduleimplementation-aws- NLB targets went from unhealthy to healthy after using this output for cluster SG ingress rules