- From: Morgan Blackthorne <
>
- To: "
" <
>
- Subject: [chef] Nagios via Chef on EC2
- Date: Tue, 14 May 2013 23:07:42 -0700
I'm bootstrapping a Nagios server via Chef on EC2. I got it up and running at this point, but I need to fine-tune a few things to get a workable config. I'm using three different regions (us-west-2, where the Nagios host is, us-west-1, and us-east-1). The config that Chef built for the hosts uses all internal IPs for the config. While this could be fine for us-west-2, where the various security groups have access authorized to the Operations security group that has the Nagios host in it, but that obviously doesn't work for the other two regions.
Is there a way to tune how the config determines which interface is used?
--
~*~ 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")
- [chef] Nagios via Chef on EC2, Morgan Blackthorne, 05/14/2013
Archive powered by MHonArc 2.6.16.