Gbrits's questions

I've got IIS exposed to the internet. On the same server I've got a NodeJS-app running (port 8080). I need to expose the node app over SSL to the internet.

Is it possible to just switch from Https -> http when doing the reverse proxy call from IIS -> Node?

This would make my life easier because I don't need to support https directly on Node. Hence, I'd only need to install a SSL-cert on the IIS-server.

So in short my plan is:

ssl (443) -> IIS -> - (https -> http) -> NodeJS (8080)

Is this possible?

How do StatsD and CollectD relate?

• Is StatsD and alternative to CollectD
• Is StatsD used to aggregate metrics coming from CollectD (and possibly other tools)
• something else entirely. If so what?

Trying to get my facts straight here.

Is Sensu (pretty new kid on the block) meant to be a replacement for both the following?:

• Nagios (monitoring & alerting)
• collectD (feeding info to Nagios in this setup)

I've read up on config management/provisioning tools like Ansible and SaltStack. These sound pretty good to me and I intend to use one of the two heavily (Not yet decided which altough I'm leaning towards Ansible). Ideally I want to use on of the two to control all aspects of configuration and command-execution in the system. I.e: from initial bootstrapping, ad-hoc commands, but also when a system-wide exception happens.

To this end it seems that I could use Nagios event handlers (when correctly setup) to in turn execute configured ansible playbooks (or the saltstack equivalant) to try to bring the system back in a correct state.

Is this setup often used? Any reasons this would not be a good idea?

I'm asking because it seems logical/convenient to me to have all config under 1 tool (ansible or saltstack), but information on using a combination of Nagios (or similar) and Ansible (or similar) as described seems to be really sparse/non-existent.

Couldn't find this exact same question so here it goes:

I'm trying to setup a CNAME record to an elastic ip linked to a ec2-instance, but this fails. When deassociating the elastic-ip from the instance and linking it to the public dns of the instance it works as expected.

Isn't it allowed to point a CNAME to a ip-address (instead of a dns-name ) ?

btw: i'm not using an A-record, because I already us this to redirect the naked domain (e.g: example.com) to www.example.com using the free service: http://wwwizer.com/

EDIT: more explicitly: I'd like both www.allehotelsinparijs.nl to point to 79.125.111.73 which is an amazon elastic-ip (although I think that doesn't matter for this discussion) . Moreover I want allehotelsinparijs.nl redirect to www.allehotelsinparijs.nl

Any other way to to this? Since from an answer below it seems that indeed a cname can't link to an ip-address

I created a software raid 5 disk using: mdadm -C /dev/md2 -l5 -n4 /dev/sd[i-l]

at the same time I'm using dstat to see io-activity: dstat -c -d -D total,sda1,md2,sdi,sdj,sdk,sdl -l -m -n

and notice that disks sd[i-k] are all read from and sdl is written to. Now, I do understand that raid5 has to be configured, but it takes a really long time and all disks are clean & formatted (using xfs) so I figure there might be some kind of shortcut to skip (unnecessary? ) checking.. Is it?

The creation is part of a time-critical nightly batch-process (run on amazon ec2) so it's not a one-time thing.

Thanks, Geert-Jan