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
Thanks for the super useful construct! Saved me lots of time :)
While playing with it, I came across the error: Specify a single subnet in [SINGLE_INSTANCE] deployment mode..
It's probably not that uncommon to have multiple isolated subnets across availability zones, but still deploy only a single instance broker (perhaps to manage cost in development environments). Having to manually construct a subnet selection to contain exactly one subnet is a little awkward. Other official constructs seem to allow a larger subnet selection and (presumably) just choose the first one - at least I've never hit an error like this before. Anyways, would be great if this construct could handle this case more gracefully somehow.
It's actually a little more complicated in my case, since I have to switch between the single and cluster constructs depending on some configuration. Not a huge deal but wanted to mention in case somebody else would find this useful. Thanks again!
The text was updated successfully, but these errors were encountered:
Hi, @jayalfredprufrock thanks for your feedback. We are happy to hear that our work is helping others :) We will discuss the possible options and get back to you next week.
Thanks for the super useful construct! Saved me lots of time :)
While playing with it, I came across the error:
Specify a single subnet in [SINGLE_INSTANCE] deployment mode.
.It's probably not that uncommon to have multiple isolated subnets across availability zones, but still deploy only a single instance broker (perhaps to manage cost in development environments). Having to manually construct a subnet selection to contain exactly one subnet is a little awkward. Other official constructs seem to allow a larger subnet selection and (presumably) just choose the first one - at least I've never hit an error like this before. Anyways, would be great if this construct could handle this case more gracefully somehow.
Here is what I need to do now:
It's actually a little more complicated in my case, since I have to switch between the single and cluster constructs depending on some configuration. Not a huge deal but wanted to mention in case somebody else would find this useful. Thanks again!
The text was updated successfully, but these errors were encountered: