Ali Albaker
Cloud Architect
Healthcare

cloudprice-mcp — The FinOps MCP server

Open-source Model Context Protocol server that turns Claude, GitHub Copilot, Cursor, or any of 7 MCP-compatible AI clients into a multi-cloud cost analyst across AWS, Azure, GCP, and OCI. Compares compute, storage, object storage, managed Postgres, and egress pricing — and surfaces OCI's 10 TB free egress tier (~12× cheaper than hyperscalers at 50 TB/month). 14 tools including a v0.6 FinOps decision suite — migration assessment with payback math, RI / Savings Plan / CUD break-even, 3-year TCO with growth modeling, and egress arbitrage — that produce real recommendations in one tool call. One-line install auto-configures every detected AI client. Listed on the Official MCP Registry, Glama, and PyPI.

AI Tennis Analyzer — SaaS Platform

Full-stack SaaS application using AWS Bedrock and Rekognition for real-time video analysis of tennis technique. Cognito authentication, React frontend, serverless backend — production-grade architecture built as a personal passion project.

Enterprise Health System LZA Migration

Led end-to-end AWS Landing Zone Accelerator (LZA) migration for an enterprise health system — on-premises VMware workloads to fully compliant AWS cloud. Implemented HIPAA guardrails, blue/green deployments, and cost management from day one.

Enterprise Terraform Platform — Phased Healthcare Migration

Production Terraform monorepo codifying the AWS landing zone and per-application infrastructure for a phased healthcare migration — clinical and enterprise applications moved in sequenced waves, in a PHI-scoped environment under patient-safety-grade change control. 40+ deployable stacks built on a compact set of reusable first-party modules, deployed across multiple AWS accounts.

The engineering core is module consolidation: a single dynamic ec2_unified module serves both Linux and Windows workloads with AMI/volume presets, IMDSv2 enforced, EBS encryption, and compliance tagging on by default — alongside standardized Multi-AZ RDS SQL Server with AD-join and KMS, SSM-driven domain-join automation, and centralized tag governance.

Safety came from the state and provider design: per-wave, per-app remote state keys isolate blast radius to a single stack, and a Terraform check block asserts the authenticated account ID matches the intended target before any plan or apply — making a cross-account misfire structurally impossible rather than merely unlikely. Migration pattern was classified per application (replication-based lift vs. vendor-installed fresh build), with DMS, MGN, and RDS runbooks validated offline before execution, cross-region AWS Backup DR plans, and Trivy scanning in the supply chain.

The application portfolio spanned clinical, diagnostic, and facilities systems, each with its own vendor support constraints and migration pattern. Client identity, environment details, and application inventory withheld under engagement confidentiality.

Network Automation, Security & AI

A vendor-neutral reference architecture for governed network automation in regulated environments — Ansible, Rundeck, Git, and a source of truth, wired so that audit evidence is a byproduct of normal operation rather than a pre-assessment scramble. Includes a full control mapping to the HIPAA Security Rule, SOC 2 Trust Services Criteria, and HITRUST CSF, plus AWS and Azure Well-Architected alignment, an 8-layer defense-in-depth model, a phased maturity path, and runnable Ansible, Jinja2, and CI examples.

On-Premises to Azure — Healthcare Migration Reference

A migration reference architecture for moving a regulated healthcare estate from on-premises to Azure — compute, storage, databases, and disaster recovery — written as a service-by-service translation from AWS. Covers Azure Migrate vs. Site Recovery tool selection, dependency-derived wave sequencing, the storage decision that carries the most risk (imaging sized on IOPS, not capacity), the three SQL targets rather than the usual two, hub-spoke landing zone topology with Policy inheritance, and the platform differences that cost AWS practitioners time.

A reference architecture and playbook — target-state design and decision points, not a case study of a specific engagement.

Enterprise Cloud Migrations — AWS↔AWS & AWS→OCI

Led 85+ enterprise client migrations across AWS-to-AWS account moves and AWS-to-OCI cross-cloud transitions. Combined Terraform, PowerShell, and Bash with GitHub Actions pipelines to automate inventory, dependency mapping, and minimum-downtime cutovers — heavy emphasis on regulated and healthcare workloads.