Skip to content
This repository has been archived by the owner on Jun 5, 2020. It is now read-only.

Can't reference security groups from peered VPCs #510

Open
philomory opened this issue Jun 29, 2018 · 3 comments
Open

Can't reference security groups from peered VPCs #510

philomory opened this issue Jun 29, 2018 · 3 comments

Comments

@philomory
Copy link

When setting up ingress rules with ec2_securitygroup, the module can't handle ingress rules that refer to security groups in peered VPCs; this is because when it tries to do the mapping between security group names and security group ids, it always only looks in the current VPC for matches. That doesn't conform to AWS's own behavior though, AWS allows you to reference security groups from other peered VPCs in the same region, and has for more than two years.

@gregohardy
Copy link
Contributor

Raising a ticket for this.

@philomory
Copy link
Author

@gregohardy Is this a ticket I should be able to see? I checked tickets.puppetlabs.com and wasn't able to find it.

@daveseff
Copy link
Contributor

I added this recently in my own branch. I may be able to do a quick PR

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants