Not sure if theres an easy solution to this. You can consider a NAT box or ssh tunnel setup in one region , and every chef clients from that region used this proxy to access the chef server (which is hosted in another location). This proxy server in turn needs to be whitelisted in chef server security group. You need to have one proxy server in every zone though.
On Wed, Aug 8, 2012 at 12:48 PM, Morgan Blackthorne < " target="_blank"> > wrote:Just wondering how others approach this situation. Elastic IPs aren't viable as we'll have nodes in autoscaling groups, etc.One approach mentioned in #chef was to launch the EC2 nodes inside VPC, and then link the regions via VPC. We'd end up paying for that, but it's an option. Any others? I'm not sure I want to (on short notice) add VPC into the mix while I'm on a deadline, though.Does Chef support the concept of slave servers, where I could have a server host in each region with an ElasticIP that pulls from the master host?
--~*~ StormeRider ~*~
"Every world needs its heroes [...] They inspire us to be better than we are. And they protect from the darkness that's just around the corner."(from Smallville Season 6x1: "Zod")
On why I hate the phrase "that's so lame"... http://bit.ly/Ps3uSS
Archive powered by MHonArc 2.6.16.