153 reputation
6
bio website
location
age
visits member for 3 years, 9 months
seen 7 hours ago

17h
awarded  Curious
Nov
17
comment using CloudFormation with an existing S3 bucket
He might be coming from a different direction, but the fact that when you delete a stack, if the deletion policy for a S3 bucket is "retain" and then you go provision the same stack again, you'll have this error. Very annoying to say the least. At least with volumes you can snapshot and restore, there's absolutely nothing you can do with S3.
Nov
9
accepted Chef over Puppet on Azure?
Nov
9
comment Chef over Puppet on Azure?
@FelixFrank can you please write an answer based on that comment? That really i think is the answer.
Nov
4
asked MariaDB Multimaster replication and AWS Auto Scaling Group
Oct
27
comment Chef over Puppet on Azure?
"recommended/approved solution by the vendor" yes. I'm not interested in being "adventurous". If they recommend something, I follow. Unless there's something seriously wrong. DSC is well, as the name says "desired state" tho. If Azure officially endorse (which I actually haven't seen anywhere yet, despite all the buz) Chef, maybe using DSC will make it more "declarative"?
Oct
27
asked Chef over Puppet on Azure?
Sep
30
asked Puppet manifest versioning
Jun
24
comment AWS ELB health check potentially remove all instances
@EEAA i meant from the web server. The webserver test it's connection to the dB server. If the web server can't see the dB server, it goes off line
Jun
24
comment AWS ELB health check potentially remove all instances
@EEAA that's what I'm doing and what i mean
Jun
24
asked AWS ELB health check potentially remove all instances
May
13
asked Recommended instance size for AD controller on AWS
May
11
comment mongodb on aws 2 region replication
@Osterjour afaik, arbiter just counts towards your majority?
May
9
accepted mongodb on aws 2 region replication
May
8
asked mongodb on aws 2 region replication
Apr
28
comment AWS route 53 database hostname best practice
Thanks for the input. They are indeed in different DBs
Apr
28
accepted AWS route 53 database hostname best practice
Apr
28
comment AWS route 53 database hostname best practice
Apology, please see edit.
Apr
28
revised AWS route 53 database hostname best practice
Clarify why it's to do with Route 53.
Apr
28
asked AWS route 53 database hostname best practice