MSManu Shuklainecorpit.hashnode.dev·Aug 24 · 11 min readSageMaker MLflow got customer managed keys on 24 August 2026, in 16 Regions and on apps onlySageMaker MLflow got customer managed keys on 24 August 2026, in 16 Regions and on apps only Summary. AWS announced customer managed key encryption for SageMaker MLflow on 24 August 2026, using AWS KM00
UOUbani Obiajulum Emmanuelinemmanuelubani.hashnode.dev·Aug 22 · 17 min readI Built a Production MLOps Pipeline for Fraud Detection That Automatically Retrains When It Detects Data Drift — Full ImplementationA Fraud Detection Model That Nobody Was Watching It was the quarterly business review when the CFO asked a question nobody on the engineering team could answer. "Our fraud loss rate has been climbing 20
TMThamu Mnyulwainthamu.hashnode.dev·Jul 22 · 6 min readMLflow Autologging and Zero-Config TrackingThe fastest way to make experiment tracking real is not to build a perfect logging abstraction. It is to add one line before the training code and let MLflow capture the boring details automatically. 00
TMThamu Mnyulwainthamu.hashnode.dev·Jul 19 · 7 min readSuivi d'experiences reproductible avec MLflow et UVLa plupart des tutoriels MLflow commencent par pip install mlflow et se terminent par une capture de la Tracking UI. C'est utile, mais cela evite souvent la partie qui casse la reproductibilite en pre00
TMThamu Mnyulwainthamu.hashnode.dev·Jul 19 · 7 min readReproduzierbares Experiment-Tracking mit MLflow und UVDie meisten MLflow-Tutorials beginnen mit pip install mlflow und enden mit einem Screenshot der Tracking UI. Das ist hilfreich, aber es ueberspringt den Teil, der Reproduzierbarkeit meistens zuerst br00
TMThamu Mnyulwainthamu.hashnode.dev·Jul 19 · 7 min readReproducible Experiment Tracking with MLflow and UVMost MLflow tutorials open with pip install mlflow and end with a screenshot of the tracking UI. That is useful, but it misses the part that usually breaks reproducibility first: the environment. A lo00
TMThamu Mnyulwainthamu.hashnode.dev·Jul 14 · 12 min readProductionising Generative AI with MLflow 3.x: Tracing, Evaluation, and Prompt OptimisationGenerative AI systems fail differently from traditional software. In a normal HTTP service, a production incident often reduces to familiar questions: did the request time out, did the database return00
TMThamu Mnyulwainthamu.hashnode.dev·Jul 14 · 11 min readEvaluer la GenAI avec mlflow.genai.evaluate() : au-dela de l'accuracyLa premiere erreur dans l'evaluation des systemes GenAI consiste a traiter la sortie comme une etiquette de classification. Cela fonctionne pour des taches de machine learning deterministes. Cela ne f00
TMThamu Mnyulwainthamu.hashnode.dev·Jul 14 · 10 min readGenAI Evaluation with mlflow.genai.evaluate(): Beyond AccuracyThe first mistake teams make when they evaluate GenAI systems is treating the output like a classification label. That works for deterministic machine learning tasks. It does not work for a retrieval-00
TMThamu Mnyulwainthamu.hashnode.dev·Jul 14 · 10 min readGenAI-Evaluation mit mlflow.genai.evaluate(): Jenseits von AccuracyDer erste Fehler bei der Evaluation von GenAI-Systemen ist, die Antwort wie ein Klassifikationslabel zu behandeln. Das funktioniert bei deterministischen Machine-Learning-Aufgaben. Es funktioniert nic00