Our journey migrating our production care management platform from ANS to Cloudflare Load Balancer—eliminating manual certificate management, resolving security concerns, and achieving a seamless cutover.

This case study demonstrates how we implemented HTTP/2 on production Apache servers with zero downtime using a blue-green deployment strategy.

This guide demonstrates how to set up secure TLS 1.3 communication using Ed25519 elliptic curve certificates and a private Certificate Authority (CA). It covers encrypted client-server communication with modern, efficient cryptographic standards — ideal for internal systems, microservices, and zero-trust network architectures.

Learn how to set up MySQL user accounts with role-based access profiles, secure configurations, and consistent privilege management across environments.

A secure and standardised approach to accessing MySQL in non-production environments using SSH tunneling, with a focus on least privilege and improved access controls.

This article outlines the implementation and usage of custom Apache 503 error pages on production Tomcat web application instances

Network troubleshooting and configuration are crucial skills for Linux system administrators. This guide covers essential network commands for AlmaLinux/RHEL systems.

On Friday 6th September 2024 at 21:31, we received an alert from LogicMonitor indicating one of our production web app servers (Tomcat#3) was down, with the message: "The host Tomcat#3 (i-xxxxxxx) is down". However, shortly after receiving the alert, we attempted to SSH into the VM and confirmed that the server was fully operational. But what did it go wrong?

In this guide, I'll demonstrate a blue-green deployment strategy in Kubernetes using Deployments and Services. The goal is to achieve zero downtime by running two sets of pods: the current version (v1.0, blue) and the new version (v2.0, green). I'll also explain how to roll back from green to blue if necessary.

On 15th August 2024, an incident occurred where the CPUBusyPercent alert did not trigger for one of our Production MySQL Database VMs (DB01), despite the CPU being at 100% for seven minutes. This was unexpected since the threshold settings in LogicMonitor were supposed to trigger alerts under such conditions.