<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Elijah Udom | Infrastructure &amp; Cloud Engineer (elijahu)</title><link>https://elijahu.me/portfolio/categories/cloud-engineering/</link><description>Infrastructure &amp; Cloud Engineering portfolio by Elijah Udom (elijahu) — AWS, Kubernetes, eBPF Security, AI/ML Infrastructure, and Platform Engineering projects.</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Wed, 05 Feb 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://elijahu.me/portfolio/categories/cloud-engineering/index.xml" rel="self" type="application/rss+xml"/><item><title>Building a Number Classification API on AWS Lambda: Serverless Architecture and CORS</title><link>https://elijahu.me/portfolio/projects/numberapi/</link><pubDate>Wed, 05 Feb 2025 00:00:00 +0000</pubDate><guid>https://elijahu.me/portfolio/projects/numberapi/</guid><description>&amp;ldquo;Serverless removes the infrastructure management problem and replaces it with a different set of problems. CORS is one of them.&amp;rdquo;
This is a breakdown of a number classification API built on AWS Lambda with API Gateway — the architecture decisions, the full Lambda function with input validation and error handling, the CORS preflight issue that catches most people, and the edge cases worth thinking about before they hit production.</description></item></channel></rss>