Problems with SecurityMonkey Scheduler in a Private VPC

[markofu]

As we discussed recently, I experienced issues running SecurityMonkey in a Private VPC without a public ip address.

As you requested, this is just a tracking issue to see if you could reproduce.

Thanks again dude :)

[oba11]

for me works fine.
You probably need an elastic IP.
Create a cname for the elastic IP.
in env-config/config-deploy.py change the FQDN and SECURITY_POST_LOGIN_VIEW to the created cname.
Should be fine.

[markofu]

Thx but my request is to do with not having a public ip, an EIP is a public Internet routable IP address.

[oba11]

I think its still possible without an EIP, as long as the dns could resolve to your selected IP somehow.
And public IP is not that bad if you have the restrict the security group.

[scriptsrc]

Hey Mark,

I deployed into a private VPC on Monday without having a public IP, nor an EIP.
I actually have it behind an ELB and delegate SSL and resolve DNS to that ELB.