<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cloudfront on Micah Henning</title>
    <link>https://www.micah.soy/tags/cloudfront/</link>
    <description>Recent content in Cloudfront on Micah Henning</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 30 Mar 2024 11:05:00 -0500</lastBuildDate>
    <atom:link href="https://www.micah.soy/tags/cloudfront/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Lock Down Lambda Function Access with CloudFront (undocumented solution)</title>
      <link>https://www.micah.soy/posts/lock-down-lambda-function-access-with-cloudfront/</link>
      <pubDate>Sat, 30 Mar 2024 11:05:00 -0500</pubDate>
      <guid>https://www.micah.soy/posts/lock-down-lambda-function-access-with-cloudfront/</guid>
      <description>Background Link to heading AWS introduced Function URLs for Lambda functions to enable public invocation access over the World Wide Web. Function URLs support IPv4 and IPv6, Cross Origin Resource Sharing (CORS), and IAM for access control. The format of these URLs is https://&amp;lt;url-id&amp;gt;.lambda-url.&amp;lt;region&amp;gt;.on.aws.&#xA;You may want to use a custom domain or share an existing domain with a unique path pattern. You may also want to protect function invocation by implementing caching, Origin Shield, or Web Application Firewall (WAF).</description>
    </item>
  </channel>
</rss>
