-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SecurityGroup: add support for adding Ingress Rules that reference Security Groups from a Peered VPC #7111
Comments
This needs an additional implementation of |
Can write like this
|
Not sure how @singlewind 's solution solves the problem. Tried using |
Sorry, I misunderstood the problem. |
Allows users to add ingress/egress security group rules containing a security group id using the Peer interface. Implements #7111 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Allows users to add ingress/egress security group rules containing a security group id using the Peer interface. Implements aws#7111 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Any updates on this? Connecting vpc-peered security groups is something we are looking to do too :) |
maybe it can be closed, because there are an implementation of Peer SG with another account ? |
This was solved by #18248, reopen if you're still having an issue. Thanks |
|
Use Case
we have multiple sub accounts that are connected with vpc peering.
we need to manage security-groups that reference security-groups from a peered account like it is possible in cloudformation with
SourceSecurityGroupOwnerId and
SourceSecurityGroupId in the AWS::EC2::SecurityGroup
from what i have seen so far this is not possible with the addIngressRule method of the ec2 securitygroup
Proposed Solution
Other
This is a 🚀 Feature Request
The text was updated successfully, but these errors were encountered: