Installing and configuring multi-node systems are common enterprise tasks that can require a tremendous amount of time and resources. As technology continues to evolve, so will the need to effectively deploy and manage these systems.

This is a bit of an odd post as product marketing is usually not in the position of recommending against the use of certain product features. But a question about Chef’s “why-run” mode came up during a webinar last week, and we’ve heard several other stories of customers still using this feature in Chef.

If you read Julian Dunn’s recent blog post and the follow up InSpec 2.0 Cloud Resources Mini-Tutorial you know that Chef recently launched InSpec 2.0.

With Habitat, it’s easy to package and export your applications to any environment, and Cloud Foundry is no exception. Our friends over at Stark & Wayne set up a quick demo to just how easy it can be! Set up Habitat First, clone the example Node repo here.

With ChefConf18 coming up in May, we’ve been digging into the archives to share some of attendee’s favorite sessions from past events. This week, we’re going back to 2015 where Chef CTO and co-founder Adam Jacob shares his thoughts and insights on the relationship and similarity between DevOps practices and Kung Fu.

Starting today, all AWS customers have the ability to perform compliance as code using InSpec through AWS EC2 Systems Manager (SSM). InSpec, an open-source testing framework from Chef, provides teams the ability to define and assess system state and status across the entire application lifecycle.

In an era of rapidly developing threats and continually evolving compliance frameworks, we need to be able to react quickly. The most successful organizations pursue continuous automation in three stages: detect, correct, and automate.

Chef’s Test Kitchen project allows for fast functional testing of infrastructure code.

What are Habitat tokens? With a recent revision of the Habitat builder site, some brand new functionality has now become available for Habitat users.