You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There seem to be no way to provision multiple public subnets. This functionality is useful for many use cases, having security (firewall) subnets being one of them. The public subnet code technically iterates over public subnet(s) but it's iterating keys and public is protected key and cannot be used more than once.
The text was updated successfully, but these errors were encountered:
Hi! thanks for opening this issue! you are correct that we lock down the module to only define 1 set of public subnets using protected keys. ATM we do not have any intention of allowing additional public subnet definitions.
Hi! Thanks for coming back so quickly. Yes I have looked at it and in the central firewall architecture that would work. I had a feeling implementing multiple public subnets right now would be a rather ordeal and quite a refactor to the module itself. I have worked around this in my wrapper module, no problem. Just wanted to signal a use case that might be somewhat of a niche. Again, thank you for considering it.
Hello,
There seem to be no way to provision multiple public subnets. This functionality is useful for many use cases, having security (firewall) subnets being one of them. The public subnet code technically iterates over public subnet(s) but it's iterating keys and
public
is protected key and cannot be used more than once.The text was updated successfully, but these errors were encountered: