AH

Cloud &
platform engineer

I build and operate cloud platforms, focusing on infrastructure automation, application delivery, observability, security, and incident response.

Ahmed Hoda
Ahmed Hoda Chicago, IL

Cloud Engineer at Cars Commerce

June 2025 — Present

01 AWS & Kubernetes

The infrastructure

Multi-tenant fleet ownership.
Terraform to production operations.

50+EKS clusters
90+AWS accounts
3AWS Organizations

EKS Auto Mode & self-hosted Karpenter

01 / Automation

Fleet upgrades,
made repeatable

Built an EKS control-plane upgrade pipeline covering preflight checks, blocking disruption-budget remediation, add-on upgrades, node convergence, and Slack reporting.

Engineering decisions

Captured a node-version baseline to verify convergence, added an idempotent verify-only rerun, and handled three-hour OIDC session limits so long-running upgrades survive credential expiry.

02 / Infrastructure as code

A consistent path
through env0

Migrated the EKS fleet from direct Terraform state to env0-managed workflows, with per-cluster configuration and organization-level OIDC access.

Migration scope

Generated tfvars for the Auto Mode fleet, established the env0 identity provider, and migrated the Datadog Terraform workspace from its S3 backend. Tenant workloads retain dedicated AWS account boundaries.

03 / Deployment guardrails

AI-assisted
infrastructure review

Built a Python tool that triggers env0 plans, retrieves pending Terraform changes, and uses Claude on AWS Bedrock for risk assessments before approval.

Handling real deployments

Supports multi-cluster targeting, sub-environment detection, dry runs, apply timeouts, and per-deployment error isolation. Separate review prompts across 6+ infrastructure repositories cover IAM trust policies and GitOps deployment risk.

Access & identity

Central Terraform for IAM and Identity Center, cross-account KMS and Secrets Manager policies, and organization-wide CloudFormation StackSets.

Cost engineering

Analyzed 300+ EBS volumes, built a multi-region unused-volume scanner, and evaluated Auto Mode against self-managed Karpenter in an architecture decision record.

Terraform / OpenTofu / env0 / EKS / Karpenter / IAM / Identity Center / KMS / EC2 / EBS / RDS / SQS / SNS / Route53

02 Platform systems

Four areas of ownership

How applications ship, workloads run,
and failures get understood.

Kubernetes platform
Delivery

Helm & Argo CD

Fleet-wide application delivery across 6 business units.

  • Central env0 module registry with per-cluster override layering for workloads that cannot use fleet defaults.
  • Selected Renovate for GitOps dependency tracking, including Argo CD manifests and Karpenter resource versions.
Unblocking a security AMI rollout

A single-replica External Secrets webhook had a disruption budget that allowed no evictions. I used an Argo CD ignoreDifferences guardrail to prevent self-heal from reversing the temporary change.

Executed across the self-managed fleet at roughly 7 minutes per cluster, with zero failed evictions.

Helm · Argo CD · Renovate · External Secrets

Developer infrastructure

GitHub runners

Self-hosted runner infrastructure across multiple GitHub organizations.

  • Built and maintain the runner image pipeline with canary deployment and identity gating.
  • Operate runner scale sets that provide shared deployment capacity for engineering teams.
Responding to blocked deployments

Led SEV-1 incident response for an Actions Runner Controller bug that blocked team deployments, then authored the postmortem.

GitHub Actions · Runner Scale Sets · AMI pipelines

Observability

Datadog

Monitoring as code, fleet-wide agent standards, and difficult failure analysis.

  • Own 18 marketplace monitors and synthetics, log indexing, archiving, and AWS integrations.
  • Standardized agent resources across 5 platform teams and deployed OpenCost with Prometheus for Kubernetes cost attribution.
The healthy agent with missing data

A version upgrade silently stopped PostgreSQL cluster checks while the cluster agent remained healthy. Comparing working and broken startup logs exposed a removed configuration-copy step.

Fixed the canonical configuration mount and verified both database instances dispatching again in production.

Why steady-state memory was misleading

Historical dashboards correctly showed roughly 6 GiB usage, but cold-start resource discovery peaked near 10.2 GiB. Limits based on steady state caused startup OOMs on large clusters.

Sized limits to the startup burst, resolving crash loops on multiple clusters exceeding 200 nodes.

Datadog Operator · Prometheus · OpenCost

Workload security

CrowdStrike

Falcon lifecycle management and security workload reliability across the fleet.

  • Manage node-sensor pinning and operator upgrades, including CrowdStrike integration in server images.
  • Investigate scheduling and admission-controller constraints before platform-wide rollouts.
Finding the failure beneath the crash loop

A Falcon admission controller recorded 1,115 restarts over eight days. One undersized node accounted for 77% of major page faults, with storage reads saturating and kubelet probes timing out.

I confirmed the same signature on four additional clusters and traced it to a NodePool with no instance-size floor. Increasing pod memory had not addressed the cause.

Directed remediation at node supply and page-cache pressure rather than treating it as a security-agent defect.

Falcon Sensor · Falcon Operator · Kubernetes

Independent project

Answers, grounded
in your documents.

Explore repository (opens in a new tab)

A retrieval-augmented document Q&A system combining semantic search, open-weight models, and a dual-agent workflow.

Document Q&A / Architecture

Select a stage to explore

01 / Ingest

PDFs are loaded, split into overlapping text chunks, and embedded for storage in Chroma. This prepares the document collection for semantic retrieval.

LangChain · Sentence Transformers · Chroma

03 Get in touch