{
  "id": 15408337,
  "title": "Hands-On with the New Amazon CloudFront Support for AWS Lambda Web Functions",
  "url": "https://urgent.news/2026/10/18/hands-on-with-the-new-amazon-cloudfront-support-for-aws-lambda-web",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-18T12:41:41.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/aws-builders/hands-on-with-the-new-amazon-cloudfront-support-for-aws-lambda-web-functions-7i9"
  },
  "original_language": "en",
  "account": "On October 12, 2026, Amazon Web Services announced that Lambda Web Functions can now serve as origins for Amazon CloudFront. This feature allows applications running on Lambda Web Functions to be delivered through CloudFront's global edge network without any code changes. By placing CloudFront in front of a Lambda Web Function, applications can take advantage of caching, custom domains with managed TLS certificates, and enhanced security through AWS WAF. AWS also introduced CloudFront Origin Access Control (OAC) to restrict access to the Lambda Web Function, ensuring that only requests routed through CloudFront reach the origin.\n\nTo test this integration, the author created a Lambda Web Function in the ap-southeast-1 region using the Node.js 24.x runtime and the default Hello World template. The Lambda Web Function was configured with IAM authentication (IamAuth) for CloudFront OAC integration, requiring authenticated requests to be invoked. A CloudFront distribution was then created, with the Lambda Web Function endpoint designated as its origin. The private Lambda function access to CloudFront was enabled through Allow private Lambda function access to CloudFront, and a resource-based policy was added to the Lambda Web Function to grant CloudFront service principal permission to invoke the endpoint, restricting access to the specific distribution using aws:SourceArn.\n\nThe author verified the setup by sending requests both directly to the Lambda Web Function endpoint and through the CloudFront distribution. Direct requests resulted in a 403 Forbidden response, expected due to the IAM-signed requirement. However, requests through the CloudFront distribution returned a successful 200 OK response, confirming that the configured origin successfully delivered the requested content.\n\nThis setup allows serverless web applications running on Lambda Web Functions to leverage CloudFront's content delivery and security capabilities while maintaining restricted access to the origin through OAC. Such configurations are suitable for serverless web applications requiring custom domains, managed TLS certificates, caching benefits, and additional application-layer security through AWS WAF. The integration ensures that direct access to the origin is restricted, providing a secure entry point for CloudFront to serve the content.",
  "summary": "On October 12, 2026, Amazon Web Services introduced support for using AWS Lambda Web Functions as origins for Amazon CloudFront . This capability allows web applications running on Lambda Web Functions to be delivered through CloudFront's global edge network without requiring changes to application code. By placing CloudFront in front of a Lambda Web Function, applications can benefit from…",
  "key_points": [
    "Lambda Web Functions can serve as CloudFront origins without code changes.",
    "CloudFront Origin Access Control restricts Lambda Web Function access.",
    "Direct Lambda access returns 403, CloudFront access returns 200."
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}