Today, we’re starting Relay by Puppet, a new initiative to build the future of cloud-based DevOps automation. This post captures our musings about the evolving world of cloud-native infrastructure and how Relay addresses this evolution.
Security is top of mind for many organizations—and for good reason. Recovering from a data breach is extremely costly. In fact, the average data breach costs more than $8.6 million in the US. One of the best ways to defend against cyberthreats is by adopting and implementing security automation.
S3 buckets without encryption can leave sensitive data exposed and at risk. As a best practice and to meet a number of industry and governmental regulations, it’s important to ensure that S3 server side bucket encryption has been properly applied at all times. To do this, many security teams rely on their Cloud Posture Security Management (CSPM) platform and/or AWS GuardDuty to monitor their AWS resources and provide alerts when an S3 bucket is found unencrypted.
Over the past few months, we set out to drastically reduce the amount of time Code Manager takes to deploy code and sand down some rough edges to make it more stable and robust. In order to understand what we were able to achieve, we need a quick primer on how code is deployed to a Puppet Server in the first place. There are three parts to a Code Manager code deployment: We’ve improved each of these three parts of the Code Manager code deployment.
