# Lambda@Edge Published articles for Lambda@Edge. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Week Notes 26#44 DevFeed: [Week Notes 26#44]() Original publisher: [Read original article]() Author: Jamie Tanna Published: 2026-11-01T21:08:28Z Content type: article Language: en Sources: [Jamie Tanna]() Topics: [CI/CD](), [hosting](), [cache-invalidation](), [Claude Code]() Tags: [2026](), [caching](), [calendar](), [cat](), [ci](), [claude-code](), [halloween](), [hugo](), [iac](), [infra](), [lambda-edge](), [metadata](), [node](), [notifications](), [pagination](), [pizza](), [readability](), [scraping](), [week-notes]() ### AI overview The author made a substantial site and infrastructure refresh after upgrading Hugo from 0.101.0 to 0.168.0. Changes included using `lastmod` instead of `.GitInfo`, date-based pagination, readability tweaks, a calendar view, infrastructure as code, and revised CloudFront caching that saves about 1-2 GB of transfer per day. With larger CI runners, build and deploy time fell from about nine minutes to 3.5 minutes. The post also notes a roughly one-minute outage after a Node upgrade exposed needed Lambda@Edge code changes, and delayed releases of a reporting plugin due to Maven Central publishing limits. The supplied text is an excerpt from week notes that also covers personal activities and media. ### Source excerpt Been nice to get back to doing some things on my site again, which has been a busy week (with thanks to Claude Code for helping actually get some of this stuff done) Upgraded from Hugo 0.101.0 (2022-06-16) to Hugo 0.168.0 (2026-10-13) Made some tweaks to my site for readability - hopefully some of them are quite noticeable! After the Hugo upgrade, I then removed .GitInfo from Hugo (so each post now uses lastmod), which wasn't possible until I moved into my Micropub endpoint over to my rewrite I've finally got to date-based pagination, which is now much nicer - and saves on unnecessary changes on my site With that all done - and increasing the CI runners' sizes - I've managed to bring this down to ~3.5m/build+deploy down from ~9m! I've made some much-needed tweaks to my CloudFront caching, ending up saving ~1-2GB/day worth of transfer Added a calendar view i.e. on my Week Notes or for my main feed / for articles, which is cool Ended up IAC'ing up my site infra which has been ClickOps until now pšŸ«£ Set up my standard.site metadata (thanks to Bridgy Fed) but given it needs a manual update to a post to link back to the at:// I did end up breaking my site for ~1 minute earlier in the week when I did a Node upgrade on my Lambda@Edge, but didn't realise my Lambda code wouldn't run (as code changes were needed) šŸ«£ Cookie enjoyed me moving her overnight bed into my office so she could be much comfier when she's in my office šŸ„° Been trying to investigate how I've been getting notifications from Claude Code, when my work machine has had no instances running - turns out it was on my desktop, but I'd not updated the Pushover creds or the claude-hook binary šŸ«£ Morph is coming a real cat - wanting to go in and out and in and out šŸ˜¹ It was Halloween this week, but thankfully no knocking (as we had our lights off), and not many fireworks I've had some somewhat significant scraping of my site Had a nice pizza night - and the Biscoff cheesecake was back, which is so so good šŸ˜‹ Had a nice wa ## How Amazon CloudFront secures and accelerates the AWS MCP Server DevFeed: [How Amazon CloudFront secures and accelerates the AWS MCP Server]() Original publisher: [Read original article]() Author: Salman Ahmed Published: 2026-10-19T20:43:15Z Content type: article Language: en Sources: [Networking & Content Delivery]() Topics: [MSP MCP](), [Amazon Web Services](), [Remote Procedure Call (RPC)]() Tags: [advanced-300](), [amazon-cloudfront](), [amazon-cloudwatch](), [amazon-route-53](), [amazon-s3](), [api](), [aws](), [aws-cloudtrail](), [aws-waf](), [backend](), [cloudfront](), [has](), [lambda-edge](), [mcp](), [mcp-server](), [model](), [model-context-protocol](), [model-context-protocol-mcp](), [networking-content-delivery](), [production]() ### AI overview The AWS MCP Server handles public and authenticated requests behind Amazon CloudFront. The article explains how CloudFront, AWS WAF, and Lambda@Edge route requests, block abuse, answer static protocol calls and OAuth challenges near callers, and reduce origin load. It also describes monitoring across edge locations and reports a limited latency comparison from one client and one PoP. ### Source excerpt The AWS MCP Server, a managed remote server for the Model Context Protocol (MCP), runs in production behind Amazon CloudFront. Hundreds of thousands of AWS accounts call it, and it handles millions of tool calls every month. Every request enters one of CloudFront's more than 750 Points of Presence (PoPs), the edge locations nearest the [...] ## Reducing Infrastructure Complexity: Why I Ditched S3+CloudFront+Lambda DevFeed: [Reducing Infrastructure Complexity: Why I Ditched S3+CloudFront+Lambda]() Original publisher: [Read original article]() Author: Shivam Anand Published: 2025-08-24T07:48:09Z Content type: opinion Language: en Sources: [Shivam Anand - DevOps & Cloud Engineering Blog]() Topics: [Amazon S3](), [migration](), [Optimization](), [Image](), [Cross-origin resource sharing (CORS)]() Tags: [api-keys](), [aws](), [aws-s3](), [blog-performance](), [cloud-infrastructure](), [cloudfront](), [cloudinary](), [cors](), [devops](), [devops-cloud-infrastructure](), [iam](), [image](), [image-transformations](), [lambda](), [lambda-edge](), [media-optimization](), [migration](), [optimization](), [performance](), [strapi]() ### AI overview The author describes migrating a blog's media management from AWS S3, CloudFront, and Lambda to Cloudinary after finding the multi-service setup unnecessarily complex for a small blog. They highlight Cloudinary's simpler onboarding and URL-based image transformations. ### Source excerpt Discover how I simplified media management for my blog by moving from AWS S3, CloudFront, and Lambda to Cloudinary. Learn about URL-based transformations, automatic optimization, and faster performance.