Hi Alex, I finally did not use the userid:group feature.
I noticed that all the instances that are started belong to the default group (that grants unlimited access from machines in the default group to machines in the default group) and to a group corresponding to their role. So what I did is that I denied access to the 80 port from the default group and from all the other groups that were not scalr.www However, now I have the following error when accessing my web servers: "Backend server not responding. One or more app instances unreachable." Any idea what I did wrong? Thanks, Claude On Nov 3, 1:53 pm, Alex Kovalyov <[EMAIL PROTECTED]> wrote: > It will not. It always requests the latest security groups from EC2. > > On 03.11.08 14:39, "Claude Vedovini" <[EMAIL PROTECTED]> wrote: > > > > > Hi Alex, > > > If I use another tool, like Elastic fox, to modify the security > > groups, will Scalr be in trouble? > > > Thx > > Claude > > > On Oct 31, 5:26 pm, Alex Kovalyov <[EMAIL PROTECTED]> wrote: > >> Granting access to userid:group is not yet implemented - will be soon. > > >> On 31.10.08 00:07, "Claude Vedovini" <[EMAIL PROTECTED]> wrote: > > >>> Hi all, > > >>> I am now looking at security and while reading the Amazon > >>> documentation about security groups it seems I should be able to > >>> easily isolate instances from each others (and the world) by granting > >>> access between groups (and not IPs) but when I look at the scalr.net > >>> interface about security groups, only granting access for IPs ranges > >>> seems possible. > > >>> Do I miss something? > >>> Thanks, > >>> Claude --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
