9 posts tagged with "AWS"

In this article I am going to try to explain how much compute cost at AWS. I will compare three options: EC2, Fargate and Lambda.

Last year AWS announced that you can use Egress-only Internet Gateway to route the traffic out of VPC without need for NAT Gateway. For free. The only gotcha is that it needs to be IPv6 traffic.

This way you can finally stop paying for NAT Gateways - if you communicate through IPv6 of course.

Node.js 24 runtime is available on AWS Lambda from 25th November 2025. It removes support for callback-based function handlers. In this article I will go through things which you should know before you upgrade your runtime.

First of all, a big shout out to Martin Damovsky for providing re:Watch service where you can rewatch all the sessions from re:Invent 2025.

Two weeks ago I've published Lambda Bun Runtime and Lambda Keep Active CDK constructs which you can download and install from npm. I've also written about those in their respective articles.

Since there is strong community build around Constructs Hub I wanted my constructs to be available there as well. Unfortunatelly for me you need to use projen in order to be picked up by Construct Hub. So I have converted my repositories to projen repositories. This article is about my thorny path.

What is Bun and why you should use it? Also everything is more fun with AWS Lambda, right?

In this short article you will learn what does it mean when your Lambda transitions to inactive state and how to deal with it.

TL;DR​

You can use our CDK construct @beesolve/lambda-keep-active which invokes your Lambda functions regularly so they won't transition into inactive state.

When people compare things like on-prem vs cloud or vps vs serverless they tend to compare just the initial cost and the running cost. Very few people I've met are fully aware of things like maintenance cost, hardware deprecation, flexibility, scaling and all the hidden costs which you only find out after a few months/years of running your service online.

Each solution has it's fit, you just need to know the distinction. For me it goes like this:

Recently I've been talking to people on various meetups about the Serverless technology and I noticed pattern - lot of people think about serverless as limitation rather than solution to real problems.

I've decided to bust a few myths I've been hearing repeatedly lately regarding the whole Serverless ecosystem. I am going to focus on AWS serverless technologies not serverless technology in general.