The bees need a security group to run under. The one specified was not found. #186
Comments
|
@Hueyza the tool expects a security group name instead of ID, try using the name instead (it automatically finds the ID later). I or someone may write a patch which helps with this by identifying if an ID was provided, and if so using that. |
FliesLikeABrick
pushed a commit
to FliesLikeABrick/beeswithmachineguns
that referenced
this issue
Nov 28, 2017
…with possible user experience issues. BWMG requires an id for subnets, but a name for security groups. This commit adds a fallback for security group lookup to use the provided name as an id. This could be optimized by checking if the name provided starts with sg- then using it as an ID, but hardcoding this arbitrary string check was avoided
cosmin
added a commit
that referenced
this issue
Nov 29, 2017
Improvement for #186 in beeswithmachineguns, accept sg ID and name
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Getting The bees need a security group to run under. The one specified was not found. when using a sg-id that exists in my AWS account. I've tried two different SG ids that exists and that I currently use in my VPC but still tells me it can't find the one. Anyone else run into this?
The text was updated successfully, but these errors were encountered: