This will be a write-up on how to get a self-healing and self-curating SSL-enabled Hot/Warm ELK stack using ECS and lambda

We’ve been using pure beanstalk at my current gig for six months and here are my thoughts.

In the last few months I’ve been working to move my latest employer to AWS from Heroku and discovered a very nasty bug.

I recently found out that you can have at most 500 application versions across beanstalk. I wrote a small script to purge it of old ones

After building the arcade cabinet I saw the PiGrrl Pocket and unfortunately for my pocket: I made one as well.

It’s been quite a while since my last post, but I promise I have somewhat of a decent reason. I wrote a book on AWS design patterns!

I finally broke down and bought a 3d printer.

I released a new Puppet module to the forge out of another work necessity. Mirth is used pretty heavily for HL7 ETL, and has a ton of other uses.

So. We have an application that it’s constantly pushed to Yum when it’s modified. We have a puppet manifest (with tests) that can deploy this application and keep it up to date, and we even have r10k handling the deployment of those puppet modules so that we don’t have to worry about dependencies, and we can even stage them! What we don’t have is a way of getting changes to that puppet module to the puppet master without remoting in and running r10k. That’s easy to fix with jenkins!

Now that we have a package, we need a way of installing it amirite? We’re going to write a puppet module for this package complete with rspec tests