<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Lambda on Micah Henning</title>
    <link>https://www.micah.soy/tags/lambda/</link>
    <description>Recent content in Lambda on Micah Henning</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 10 Aug 2024 13:27:00 +0000</lastBuildDate>
    <atom:link href="https://www.micah.soy/tags/lambda/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Resolving `No such file or directory` Error After Building Lambda Docker Image with Packer</title>
      <link>https://www.micah.soy/posts/packer-lambda-docker-image-command-not-found/</link>
      <pubDate>Sat, 10 Aug 2024 13:27:00 +0000</pubDate>
      <guid>https://www.micah.soy/posts/packer-lambda-docker-image-command-not-found/</guid>
      <description>Hashicorp Packer builds containers, virtual machines, and machine images with virtually any kind of provisioner. In particular, it can create docker images without a Dockerfile and then push them to a repository like ECR. I recently had a project where I used Packer to create a docker image using a bash script provisioner, pushed to AWS Elastic Container Registry (ECR) for use in AWS Lambda. However, the container failed to execute due to a runtime error:</description>
    </item>
    <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>
