Fair warning up front: this is not a Terraform, AWS, or Elasticsearch tutorial. You’ll need to know a bit or read the docs to apply the examples.
When I wanted to add the AWS version of ELK (Elasticsearch, Logstash, Kibana) which is Elasticsearch, Cloudwatch and Kibana, I hit a road block that Terraform did not support provisioning the actual streaming of logs from Cloudwatch to Elasticsearch naively. Googling lead me approximately nowhere, and I had to devise a solution from scratch.
A while back, I opened (as in ‘made available’) BitSyncHub, a tool to automatically synchronize Bitbucket repositories to Github. At the time I saw no real reason to open source it - it was a quick hack to solve my own problems, and I felt that anyone else could just reproduce it if they wanted to.
Since then, a whole lot of open source projects, including a few big names, has started using the service, and when I had to reply to a recent support request from one of these projects that I did not have time to look into their issue due to daytime work, I realized that some projects are now depending on the service staying up and working.
I was honored to be given the oppurtunity to speak at the first instance of Stockholm Automation Nights last week, and hope to be able to attend many more. I think it was a good mix of talks - my talk was more to the DIY side of automation, Andrey talked about Jenkins delivery flows, and Håkan Rönngren had more of a process and way-of-working focus in his talk on test automation.
I was blown away by the amount of response - mostly positive - on my Python is important post. However, a lot of the replies, both positive and… slightly less positive, really highlighted an issue I have with how a lot developers seem to approach programming languages: the search for the Perfect Language to Love and Protect. Why are so many developers so very emotional when it comes to their favourite programming language?