There are lots of excellent reasons to move applications into the public cloud. But those benefits cannot come at the expense (pun intended) of performance. Your SLAs, whether explicitly stated and written into contracts or implicitly promised through your commitment to quality, are part of your brand. Falling short is costly. Even if you don’t have to pay penalty fees, your reputation and customer loyalty can take a hit.
Compromising a pod in a Kubernetes cluster can have disastrous consequences on resources in an AWS Elastic Kubernetes Service (EKS) account if access to the Instance Metadata service is not explicitly blocked. The Instance Metadata service is an AWS API listening on a link-local IP address. Only accessible from EC2 instances, it enables the retrieval of metadata that is used to configure or manage an instance.
We are excited to partner with AWS in launching AWS Bottlerocket, a container optimized operating system. Bottlerocket gives DevOps teams speed, efficiency and security in containerized environments.
In surveys about why organizations adopt Kubernetes, a desire to reduce overall IT costs is an oft-cited reason for adopting containers and Kubernetes. Yet after the fact, when organizations talk about surprises during Kubernetes adoption, many cite increased costs. So does Kubernetes reduce costs or not? Like so many things in life, it depends. Here are some of the reasons Kubernetes projects come in over-budget and how to avoid them.
Sysdig is pleased to support AWS today in their GA launch of Bottlerocket, a special-purpose operating system designed for hosting Linux containers. Orchestrated container environments run potentially hundreds of compute nodes. Operating general-purpose Linux on container hosts introduces complexity for IT teams who must patch and update packages across their clusters. Worse, features and packages that are not necessary for running containers, introduce unnecessary security exposure.
Hybrid IT environments enable Enterprises to optimize factors such as performance, cost, agility, and security, but they also introduce complexity. Containers are a great way to reduce some of this complexity by standardizing how applications are developed and deployed.
This is part two of our journey towards monitoring Azure resources with SCOM, using the Azure Management pack. In Part 1: Installation, we finished installing the Management Pack and managed to connect one of our subscriptions where the resources we want to monitor are. Now, let’s move on to configuring the monitoring for actual resources or services.
Metrics help you understand how your business and applications are performing. Longer metric retention enables quarter-over-quarter or year-over-year analysis and reporting, forecasting seasonal trends, retention for compliance, and much more. We recently announced the general availability (GA) of extended metric retention for custom and Prometheus metrics in Cloud Monitoring, increasing retention from 6 weeks to 24 months. Extended retention for custom and Prometheus metrics is enabled by default.
Many large organizations deploy Cloud Foundry atop the public cloud to deliver superior business outcomes. The app platform has proven to be a terrific way to adopt public cloud in an efficient, expedient, and secure fashion. There’s another benefit to deploying atop the public cloud—easy access to innovative, first-party services.
In the midst of the COVID-19 pandemic, many businesses have faced uncertainty regarding the future. While some companies had to close down temporarily, others were able to move toward a remote workforce. By mid-April of 2020, the number of employed adults saying they began working remotely peaked at 62%. While this number will inevitably go down once the pandemic passes, it certainly seems like remote work has become more commonplace.
