<?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 Lonfo Blog</title><link>https://blog.lonfo.fr/tags/lambda/</link><description>Recent content in Lambda on Lonfo Blog</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 20 Oct 2026 09:00:00 +0200</lastBuildDate><atom:link href="https://blog.lonfo.fr/tags/lambda/index.xml" rel="self" type="application/rss+xml"/><item><title>Daily Actions: Read your data back with a DynamoDB Query behind GET /actions</title><link>https://blog.lonfo.fr/posts/daily-actions-list-dynamodb-query-api-gateway-lambda/</link><pubDate>Tue, 20 Oct 2026 09:00:00 +0200</pubDate><guid>https://blog.lonfo.fr/posts/daily-actions-list-dynamodb-query-api-gateway-lambda/</guid><description>&lt;h1 id="daily-actions-read-your-data-back-with-a-dynamodb-query-behind-get-actions">Daily Actions: Read your data back with a DynamoDB Query behind GET /actions&lt;/h1>
&lt;p>In the previous article, our users learned to &lt;strong>write&lt;/strong>: a signed-in user sends an action to &lt;code>POST /actions&lt;/code>, a Lambda stores it in DynamoDB, and anonymous requests are rejected. But if you add a task and refresh the &lt;code>/todo&lt;/code> page, the list stays empty. Nothing reads the data back.&lt;/p>
&lt;p>In this article we add the missing half: a &lt;code>GET /actions&lt;/code> endpoint that returns &lt;strong>only the actions of the signed-in user&lt;/strong>, using a DynamoDB &lt;code>Query&lt;/code>.&lt;/p></description></item><item><title>Daily Actions: Save data in DynamoDB through an API Gateway and Lambda secured by Cognito</title><link>https://blog.lonfo.fr/posts/daily-actions-secure-api-gateway-lambda-dynamodb-with-cognito/</link><pubDate>Tue, 13 Oct 2026 09:00:00 +0200</pubDate><guid>https://blog.lonfo.fr/posts/daily-actions-secure-api-gateway-lambda-dynamodb-with-cognito/</guid><description>&lt;h1 id="daily-actions-save-data-in-dynamodb-through-an-api-gateway-and-lambda-secured-by-cognito">Daily Actions: Save data in DynamoDB through an API Gateway and Lambda secured by Cognito&lt;/h1>
&lt;p>In the previous article, our static Next.js application learned to authenticate users with Amazon Cognito. But a login page protects nothing by itself: as long as our backend accepts anonymous requests, anyone can write into our database.&lt;/p>
&lt;p>In this article we connect the pieces. The signed-in user will send a new action to an API Gateway endpoint, a Lambda function will insert it into DynamoDB, and &lt;strong>only requests carrying a valid Cognito token will get through&lt;/strong>.&lt;/p></description></item><item><title>Give memory to your API: Build a complete CRUD with DynamoDB and CDK</title><link>https://blog.lonfo.fr/posts/give-memory-to-your-api-build-a-complete-crud-with-dynamodb-and-cdk/</link><pubDate>Fri, 14 Nov 2025 12:25:40 +0100</pubDate><guid>https://blog.lonfo.fr/posts/give-memory-to-your-api-build-a-complete-crud-with-dynamodb-and-cdk/</guid><description>&lt;h1 id="give-memory-to-your-api-build-a-complete-crud-with-dynamodb-and-cdk">Give memory to your API: Build a complete CRUD with DynamoDB and CDK&lt;/h1>
&lt;p>In the previous articles, we gradually introduced you to serverless, starting with the creation and deployment of a Lambda function in the first article, followed by the addition of an API Gateway to trigger the Lambda in the second article.
In both cases, the returned data consisted of simple mock responses. You have therefore acquired a solid foundation to move on to the next level: data persistence.
As stated in the title, we will use DynamoDB and remain within the same approach: the discovery of AWS CDK.&lt;/p></description></item><item><title>Build your first serverless API with API Gateway and Lambda function using CDK and TypeScript</title><link>https://blog.lonfo.fr/posts/build-your-first-serverless-api-with-api-gateway-and-lambda-function-using-cdk-and-typescript/</link><pubDate>Thu, 23 Oct 2025 20:35:01 +0100</pubDate><guid>https://blog.lonfo.fr/posts/build-your-first-serverless-api-with-api-gateway-and-lambda-function-using-cdk-and-typescript/</guid><description>&lt;h1 id="build-your-first-serverless-api-with-api-gateway-and-lambda-function-using-cdk-and-typescript">Build your first serverless API with API Gateway and Lambda function using CDK and TypeScript&lt;/h1>
&lt;p>Serverless is one of the most powerful approaches for building fast ,scalable and cost effective applications . In this article, I will walk you through building a simple API with two endpoints in under 10 minutes . We will leverage AWS lambda and Amazon API Gateway, deploying the entire infrastructure using AWS CDK with TypeScript.&lt;/p></description></item><item><title>Hello World Serverless : Deploy an AWS Lambda Function with CDK and TypeScript</title><link>https://blog.lonfo.fr/posts/hello-world-serverless-deploy-an-aws-lambda-function-with-cdk-and-typescript/</link><pubDate>Mon, 06 Oct 2025 20:59:13 +0100</pubDate><guid>https://blog.lonfo.fr/posts/hello-world-serverless-deploy-an-aws-lambda-function-with-cdk-and-typescript/</guid><description>&lt;h1 id="hello--world-serverless--deploy-an-aws-lambda-function-with-cdk-and-typescript">Hello World Serverless : Deploy an AWS Lambda Function with CDK and TypeScript&lt;/h1>
&lt;p>Serverless has become one of the most popular approaches for building &lt;strong>fast&lt;/strong>, &lt;strong>scalable&lt;/strong> and &lt;strong>cost-effective&lt;/strong> applications. With &lt;strong>AWS Lambda&lt;/strong> you only focus on writing code and AWS takes care of everything else: scaling, servers and availability.&lt;/p>
&lt;p>But there is a tool taht makes the experiences even better : &lt;strong>AWS CDK&lt;/strong>.
It allows you to define your infrastructure using familiar programming languages such as &lt;strong>TypeScript&lt;/strong>, &lt;strong>Java&lt;/strong>, &lt;strong>Python&lt;/strong>,&lt;strong>C#&lt;/strong> or &lt;strong>Go&lt;/strong>, instead of writing raw of CloudFormation template.&lt;/p></description></item></channel></rss>