If you missed the first 2 tips, go back and read 5 Tips to Avoid Deadlocks in Amazon RDS (Part 1), and then come back for the last 3 tips on deadlock avoidance. Once again, I want to re-emphasize that RDS is not actually capable of creating deadlocks — it merely reports them from the underlying database engine.

One difficult task for the AWS account administrator is to keep track of used and unused resources. That’s why we’re adding more actions to help track down unused resources. Today, we’re happy to announce a new action: Delete Unused Elastic IP Addresses.

Today we are announcing the release of StackStorm v2.9.2 and StackStorm v2.10.1. Those two patch releases fix a security issue which has been reported to us this week by one of our users (Alexandre Juma – thanks!).

This tutorial walks through using Rancher to deploy Elasticsearch into a Kubernetes cluster. At the end of this article, you will have a fully functional 2-node Elasticsearch cluster, complete with sample data and examples of successful queries.

Over the last couple of weeks, we’ve prioritized some sustaining product goals to polish the codebase and update some big ticket dependencies. Among those updates were: React, Redux, and Webpack - the biggies. The first two were pretty painless and inspired the confidence to approach updating Webpack from v2 to v4 like maybe no big deal! Though confidence level was on high, I felt a slight chill and a twinge of doubt by the prospect of making changes to our build configs.

Last week, I wrote A Beginner’s Guide to Deadlocks in Amazon RDS. This week, I’d like to lay out my 10 years of experience about how to avoid deadlocks altogether. Often times, this will be out of the hands of operations people, but you can still move for dev changes based on issues in production. The more knowledgeable you are about deadlocks in general, the more they will lean on you as a resource with wisdom, not a totalitarian barking rules.

KubeCon + CloudNativeCon North America 2018 was an incredible event. We had many exciting announcements – LogDNA’s new partnership with IBM Cloud, our recent round of funding, as well as great conversations, product demos, fun giveaways, and even surprise gifts for loyal customers, our booth was jam packed.

Jenkins is an extremely popular, open-source, continuous integration tool used for running tests, building code, and subsequently pushing to staging and then production. In a previous post, I outlined instructions for collecting, analyzing and visualizing Jenkins system logs.