Member since
05-24-2016
3
Posts
0
Kudos Received
0
Solutions
10-30-2016
04:41 AM
I use the network option "Use an existing subnet in an existing VPC" to launch my cluster in AWS. Cloudbreak automatically creates spot instances instead of the regular instances. I have not specified anywhere about spot instances. I checked my instance types created through "Manage Template" also. There is no reference to spot instances anywhere. Does anybody have any idea as to where this setting exists? I use my cloudbreak deployment with version: 1.6
... View more
Labels:
05-24-2016
04:52 PM
Hi Janos, Thanks for your reply. Reg. point 2, I understand ports 443 and 22 needs to be there in every security group but should they be opened globally i.e 0.0.0.0/0?
... View more
05-24-2016
02:39 PM
Hi I have couple of questions: 1) I'm unable to modify the security groups directly from the AWS console for security groups created by cloudbreak. Neither does cloudbreak provide any option to modify the security group after the cluster deployment. Am I missing something? 2) I created a security group in cloudbreak that opens all ports only within my company's exit IP. The cluster creation hangs with no information in the cbd logs. Is it mandatory to open up 22 and 443 globally?
... View more
Labels: