Operations | Monitoring | ITSM | DevOps | Cloud

In the last few years, many organizations I worked with have significantly increased their cloud footprint. I’ve also seen a large percentage of newly launched companies go with cloud services almost exclusively, limiting their on-premises infrastructure to what cannot be done in the cloud — things like WiFi access points in offices or point of sale (POS) hardware for physical stores.

Thomas Stringer has a couple of great blog posts on how to understand your Azure monitoring costs and also on how to reduce your costs, see Azure Monitor Log Analytics too Expensive? Part 2 – Save Some Money | Thomas Stringer (trstringer.com). In the past I’ve blogged on How to calculate the Azure Monitor and Log Analytics costs associated with AVD (not an easy task!).

Moving large amounts of data to the cloud can be arduous and time-consuming. A cloud migration would take years if engineers manually moved data from assessment through mobilization and migration phases. An effective cloud migration also requires adequate data encryption, fast data transfer speeds, and constant monitoring. Migrating workloads to AWS requires you to monitor costs in real-time as well to avoid overspending.

Spot worker nodes on EKS (Elastic Kubernetes Service) are a great way to save costs by allowing customers to take advantage of unused capacity. With Sumo Logic, we have experimented with and adopted spot worker nodes for some of our EKS clusters to see if we can pass along the same benefits. We decided to share some of the learnings, challenges, and caveats with using spot instances along with the monitoring setup.

Ever wonder how best to plan for a successful cloud migration? I sat down with David Colebatch, CEO / Chief Migration Hacker at Tidal Migrations to better understand what it takes to approach a cloud migration with confidence. David will help to demystify cloud migration planning and further change our perceptions of the cloud.

Toward the end of each year, tens of thousands make the journey to Las Vegas to participate in AWS re:Invent. AWS re:Invent has been the seminal conference for cloud-focused engineers since 2012, offering a space where the global cloud computing community can share and learn the latest insights and solutions.

Since the 90s, when you run a company in the Healthcare industry in the US market, you must comply with the Health Insurance Portability and Accountability Act (HIPAA) Security Rule. Some of the security rules are directly linked to how you operate your organization, the others how you manage your application data for your customers. This article will walk you through what to consider on AWS to be HIPAA compliant in 2022.

When an alert fires from your applications, your team needs to know as soon as possible to mitigate any user-facing issues. Customers with complex operating environments rely on incident management or related services to organize and coordinate their responses to issues. They need the flexibility to route alert notifications to platforms or services in the formats that they can accept.