Hi Michele,
* I have been working on the same use case as you without using Scalr
vpc router, did you setup any proxy in public subnet so that instance in
private subnet can talk to Scalr server in public subnet? *
In my case, I set up a NAT gateway in public subnet so that instances
in private subnets can talk to outside(not sure if it's needed, but without
using it, my instances on Scalr UI will get stuck at "pending"), but the
servers on Scalr UI get stuck at "initializing" while on AWS side they are
all actually running.
Sorry to bother you with something you did a long time ago, I will
appreciate any comments you give to me.
BR
在 2015年2月16日星期一 UTC-8上午8:25:30，Michele Viviani写道：
>
> Hi,
> I do have a VPC with several Subnets (private and public). I'm running a
> PoC to understand the benefits and potentiality of Scalr.
> I created an EC2 in AWS and installed the open source version of the tool
> into a subnet
> Everything is fine. I was able to link my AWS VPC with credential, linked
> an Image, created a base role linked to that.
> I enforced the policy to be able to use that VPC only.
> I was able to create a farm, adding the role, selecting the right subnet,
> but the I got the error for the VPC Router.
>
> I was than modify the config.yml file according the the wiky page
> https://scalr-wiki.atlassian.net/wiki/display/docs/Using+VPC+-+Internal+Scalr+Deployment
> Restared the service.
> Unfortunately I still got the error.
>
> Can you please help me?
> Thanks
> Mike
>
>
--
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.
