fix: Add missing ec2:DescribeSecurityGroups IPv4 VPC CNI IRSA permissions#646
Merged
bryantbiggs merged 1 commit intoMay 28, 2026
Conversation
ec2:DescribeSecurityGroups IPv4 VPC CNI IRSA permissions
bryantbiggs
approved these changes
May 28, 2026
10161bc
into
terraform-aws-modules:master
22 of 23 checks passed
antonbabenko
pushed a commit
that referenced
this pull request
May 28, 2026
## [6.6.1](v6.6.0...v6.6.1) (2026-05-28) ### Bug Fixes * Add missing `ec2:DescribeSecurityGroups` IPv4 VPC CNI IRSA permissions ([#646](#646)) ([10161bc](10161bc))
Member
|
This PR is included in version 6.6.1 🎉 |
This was referenced Jun 1, 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
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.
Add missing ec2:DescribeSecurityGroups permissions
Description
Add missing ec2:DescribeSecurityGroups to iam-role-for-service-account VPC CNI policy
Motivation and Context
Closes #645
VPC CNI add-on upgrades fail because of missing IAM permissions
Breaking Changes
How Has This Been Tested?
examples/*to demonstrate and validate my change(s)examples/*projectspre-commit run -aon my pull request