Description

What problem are you trying to solve?

Context: 1 account with 2 VPCs; each VPC has a security group named the same.

When specifying security group terms using the name, reconciling the node class will include both security groups. If the node is only being attached to 1 subnet it means 1 of the security groups is invalid since it doesn't belong to the same network as the subnet. This results in the following error when trying to create the node.

InvalidParameter: Security group <SECURITY_GROUP_ID> and subnet <SUBNET_ID> belong to different networks.

A simple solution would be to allow optionally specifying a VPC name or ID (much like the Terraform AWS provider allows for the aws_security_group data source). This would provide sufficient information to target the appropriate security group.

How important is this feature to you?

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment