<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Lambda@Edge on AWS by Ivan - Cloud Engineering &amp; DevOps</title>
    <link>https://awsbyivan.com/tags/lambda@edge/</link>
    <description>Recent content in Lambda@Edge on AWS by Ivan - Cloud Engineering &amp; DevOps</description>
    <image>
      <title>AWS by Ivan - Cloud Engineering &amp; DevOps</title>
      <url>https://awsbyivan.com/images/og-image.png</url>
      <link>https://awsbyivan.com/images/og-image.png</link>
    </image>
    <generator>Hugo -- 0.152.2</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 15 Oct 2026 10:00:00 +0000</lastBuildDate>
    <atom:link href="https://awsbyivan.com/tags/lambda@edge/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Case of the Random 503: A CloudFront and Lambda@Edge Mystery</title>
      <link>https://awsbyivan.com/blog/cloudfront-lambda-edge-503/</link>
      <pubDate>Thu, 15 Oct 2026 10:00:00 +0000</pubDate>
      <guid>https://awsbyivan.com/blog/cloudfront-lambda-edge-503/</guid>
      <description>An intermittent CloudFront 503 traced to a Lambda@Edge origin-response function timing out on cross-region DynamoDB and S3 calls. Here&amp;#39;s how CloudFront architecture explains the mystery.</description>
    </item>
  </channel>
</rss>
