Skip to content
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

VPC Placement Strategy is not complete #614

Closed
moofish32 opened this issue Aug 21, 2018 · 2 comments
Closed

VPC Placement Strategy is not complete #614

moofish32 opened this issue Aug 21, 2018 · 2 comments

Comments

@moofish32
Copy link
Contributor

The concept of a placement strategy is a nice abstraction. In the current form there are some gaps:

  1. Isolated subnets are ignored (that's my miss)
  2. Public subnets may come in pairs (e.g. Ingress only public subnet and Egress only public subnets, this separation commonly occurs so a NACL can be used on egress to protect against layer 3/4 data exfiltrations)
  3. Many private subnets can also occur in large team VPCs where network isolation in layers is desired

The use of tags to select subnets might be something to consider. In order to quickly enable teams the support of simply allowing users to specify subnetIds would unblock current users.

@rix0rrr
Copy link
Contributor

rix0rrr commented Aug 21, 2018

I'm just working on that in here: #610

Can you elaborate some on additional things you would like to see in there?

@rix0rrr
Copy link
Contributor

rix0rrr commented Aug 21, 2018

(Please do it in the PR)

@rix0rrr rix0rrr closed this as completed Aug 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants