Hi Jay, Your users can not change the Security Groups associated with a server that has already been launched. They can edit rules in an existing Security Group, but can not change the Security Group assignment without terminating and re-launching.
Reference Documentation: https://scalr-wiki.atlassian.net/wiki/display/docs/Security+Groups%2C+Security+Rules+and+Running+Instances https://scalr-wiki.atlassian.net/wiki/display/docs/Editing+a+Running+Farm Let us know if you have any questions from here. Many thanks, Wm. Marc O'Brien Scalr Technical Support On Wednesday, April 20, 2016 at 10:34:33 AM UTC-6, Jay Farschman wrote: > > As I roll out my latest version of the Scalr CE to my AWS end-users, the > most common problem I'm having with them is around security groups. They > don't think about what ports need to be open, because the "Security" tab > doesn't seem that important when they are building a Farm Role. Then after > they spin up the VM/instance, they try to add "Security Groups" to the Farm > Role, but this does not add them to the running instance. > > Should this work? > > I am forced to tell user: > > > 1. If you haven't invested much time in the instance, build it again > 2. If you've invest too much time, contact me in chat and I'll add the > rules for you. > > I have 150+ users and they all want to work quickly. Thanks. > -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
