Operations | Monitoring | ITSM | DevOps | Cloud

Puppet

Puppet supports DoD continuous compliance and configuration management

Puppet Enterprise now offers Compliance Enforcement Modules aligned to DISA STIGs Benchmarks. The Defense Information Systems Agency (DISA) Security Technical Implementation Guides (STIGs) were built to safeguard our most critical security systems and data against a dynamic threat environment, yet monitoring and enforcing widely deployed infrastructure at the U.S. Department of Defense (DoD) scale is a formidable task.

How to rein in cloud chaos with Puppet

Cloud automation can do a lot for your organization, making it possible to automate resource creation, management, and housekeeping tasks. If you’ve thought that cloud automation is out of reach, or you’re curious to learn what it can do, we’re excited to announce a brand new webinar that can help! Discover cloud automation in action and walk away with code that you can get up and running within an hour.

Updating A Forge Module In Puppet Enterprise Using Code Manager

Puppet Support Explain how to change the version of a Forge module deployed in your Puppet Enterprise Environment Please note it is not considered best practice to declare `:latest` rather than a specific version tag in your PuppetFile as this could lead to untested module combinations being deployed to your environment. Commands Used: puppet-code deploy production --wait -l debug puppet module list --environment=production

Get your time back by getting rid of unused modules with Dropsonde

You’ve probably been using Puppet Forge modules to manage bits in your infrastructure for years. If you’re like most of us, you’ve gradually added more modules and maybe you’ve lost track of exactly what some of them do and on what nodes they’re declared. You may even suspect that you have modules installed that you haven’t actually used in years…. only you’re not quite certain which modules those might be. I am certainly guilty of this!

How Puppet is making platform engineering more secure

As platform engineering continues to rise in popularity, there is a new side effect to watch out for: the people using the internal developer platforms aren't the people who built it. They’re not necessarily familiar with the codebase, they may not know what's powering it behind the scenes – and the platform might even have to contend with malicious users. So how is Puppet evolving to contend with this new challenge?

Here's how to drive velocity and business success with self-service

“Give customers the power to help themselves. Self-service options allow for faster problem resolution while reducing strain on your support teams.” – our friends at ServiceNow Self-service is a crucial component to any DevOps strategy. Many IT organizations still depend on manual and ticket-driven workflows with strong reliance on dedicated teams to make simple and frequent change requests. Unfortunately, these traditional models don’t scale.

New Puppet Enterprise LTS release increases security and compliance

We’re pleased to introduce updates to Puppet Enterprise that give infrastructure operations teams the insights they need to manage and protect infrastructure and complex workflows in a simple yet powerful way. With Puppet Enterprise 2021.7, teams gain automatic access control and a host of system insights related to runs and events.

How to Change the Puppetdb Port in Puppet Enterprise

Occasionally in Puppet Enterprise, you may need to change the port PuppetDB consumes, for instance, if another service requires port 8081. While we in Puppet Support recommend that you change the port for the other service. If you can’t do that, Follow this Video and the attached Knowledge base article for a guide on changing the port.