As the number of IoT devices scale, the challenges of provisioning and keeping them up to date in the field increases. Domotz, who manufacture an all-in-one, network monitoring and management device for enterprise IoT networks, found themselves with this challenge that was further compounded by their rapid software release cadence. One of the most crucial and difficult aspects for Domotz to solve was the delivery of automatic updates to the tens of thousands of devices deployed.

As a team that does pure serverless, we place a lot of emphasis on fast deployments. Lately, though, as our codebase has gotten larger, and the number of interactions between the microservices has increased, we have come up against the classic problem of excessively long test execution times in our serverless continuous integration.

More than 40 million people use GitHub as a collaboration tool for building software around the world. For most companies — including distributed teams like Elastic — GitHub has become a critical content source for building software, holding much of the information and knowledge upon which the organizations are built, across items like issues, pull requests, and more.

Today, we’re excited to announce you can now integrate LaunchDarkly with Sleuth, allowing you to track feature flags as a source of change in your DevOps stack. The Integration LaunchDarkly gives developers fine-grained control over which users see which features, and with our native LaunchDarkly integration you can now track the status and impact of feature flags relative to other source changes in your projects, such as code, issues, etc.

IAM is the de-facto method of authorization in AWS. Most Kubernetes “Quick Start” guides for AWS do not adequately cover how to manage IAM access in your pods. This blog series will first go over the security issues specific to AWS IAM on Kubernetes, then compare solutions, and then end with a detailed walkthrough for setting up your cluster with one of those solutions.

The coronavirus (COVID-19) pandemic has forced many organizations to take unprecedented steps towards remote working. As a fully distributed team, we’ve faced the common challenges of remote work. Based on our experience from our very beginning in 2018, all but a few of these organizations new to remote working will face hurdles to overcome and may try to revert to colocation as soon as possible. Remote working is hard, even when it’s carefully planned and executed.