Hi, it's requirements from scalr to have VPC router role in case if you run your instances inside VPC.
This role is made for the instances which have not assigned EIP on it, so this instance will allow them to communicate scalr (because your scalr server could be inside VPC => reach. from instance even without EIP assigned or inside another VPC or even outside(no VPC, another cloud, separated server)) So, as far as I'm understand they did this role because in that case you don't need to worry about location of scalr server Середа, 11 вересня 2013 р. 11:23:35 UTC+2 користувач Monick написав: > > Plus, I tried Scalr.net 30-day free trial before, and I didn't need a > router role overthere. Why in open source versione is it required? > > Il giorno mercoledì 11 settembre 2013 11:21:28 UTC+2, Monick ha scritto: >> >> Hi all, >> I'm trying to create a farm with my custom role, but I can't save it, >> with "VPC Router role required for farm that running inside VPC" message. >> I have all my subnets already configured in EC2 (and IGW and also VPG, >> VPNs... it's a complex corporate infrastructure) so, if I correctly >> understand, I don't really need a VPC Router, because my subnets have their >> routing tables. But Scalr ignores that and requires a Router... how can I >> avoid it? >> > -- 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/groups/opt_out.
