Five worthy reads is a regular column on five noteworthy items we’ve discovered while researching trending and timeless topics. In this edition, we’ll learn about hyperscale data centers, including how they function, and the considerations and challenges organization face in deploying them.
With AWS’s announcement that macOS instances are available on Amazon EC2, iOS, macOS, and Safari developers now have the opportunity to move their build and test pipelines to the cloud and take advantage of all that the AWS ecosystem has to offer.
What is bandwidth? Bandwidth refers to the amount of data that can be sent or received by a particular device in a stipulated period. This is measured in Mbps (Megabits per second). Very often, people use bandwidth to refer to the speed of the internet connection. However, that is not the case. Talking about bandwidth vs. speed, the former helps understand the quantity of data transferred per second. At the same time, the latter focuses on the rate of data transfer from the source to the destination.
As in years past, re:Invent is where AWS announces many new features, services and enhancements. This year is no exception and here at Spot by NetApp we are proud of our product and engineering groups for delivering immediate and full support in relevant areas such as the new GP3 EBS volume and new EC2 instance types – D3, D3en, R5b and M5zn.
Our company is using Icinga for quite some time now to monitor our whole infrastructure and its customers infrastructure. We deploy many Icinga instances for different teams and customers (see this video for more information). To manage the configuration of these instances, we use the Icinga Director module. This gives us an easy way to deploy checks, services and hosts in Icinga. The teams do not have access to the configuration files of Icinga, so every change is done via the Director frontend.
In the context of businesses, the ultimate goal of innovation for technology companies is to drive a profit. This means that even though many software engineering problems can be solved with enough time and budget — just because a business can solve a problem doesn’t mean that they should. Sometimes, even once a team has figured out how to solve an engineering problem, it doesn’t make sense to deploy the solution — because it costs so much to operate.
Across the IT community, there is a buzz around the SaaSOps movement, and it has been consistently gaining momentum. As David Politis of BetterCloud describes it: “SaaSOps is a practice referring to how Software as a Service (SaaS) applications are managed and secured through centralized and automated operations (Ops), resulting in reduced friction, improved collaboration, and better employee experience”.
It was over a month ago that I promised we would tie together Splunk Security Content and the Splunk Attack Range to automatically test detections. Ultimately, using these projects together in a Continuous Integration / Continuous Delivery (CI/CD) workflow with CircleCI brings the rigors of software development to the SOC and truly treats 🛡detection as code. Well, I want to share how we have failed at achieving this goal.
With over 1 million customers and over 14 years of experience working with them, Amazon Web Services has some real insight into best practices and technologies for setting up and running secure, well governed cloud deployments. The recently launched AWS Control Tower puts this knowledge to use providing companies with a quick and simple way to securely set up complex, multi-account environments for rapid, yet fully controlled growth and innovation.
During my tenure at Puppet, I’ve learned that almost everything we do is focused on two things — eliminating soul-crushing work, and the never-ending desire to solve really hard customer problems. Couple those with the positive and energetic attitude of the Puppet team, and we’re bound to have a profound impact on our customers. Maybe I’ve had too much Kool-Aid?
