I noticed quite some time ago that my CDK deployments had gotten slow, and that a lot of the churn was SQS. I did not really have time to dig into it, and I half-convinced myself it was just a feeling - that it had not actually slowed down. Eventually it nagged at me enough that I sat down with an LLM agent to investigate. The culprit turned out to be a one-liner buried in a construct I use everywhere.

Last year when I left my job I wanted to see whether I could build something without the help of all the internal tools I'd been using for the last 5 years. I had a great chance to change anything I wanted within my own stack. That's when the Group Expense with Ease site was born. Today I am celebrating a year since its initial release which I have celebrated with what else than a rewrite.

I was super excited to hear the news about Remix 3 stable being released last week. Similarly to SvelteKit 3 I wanted to run it in AWS Lambda. For SvelteKit I've built kit-on-lambda and I was curious if something similar could be done for Remix as well.

I've closed more than 200 tabs today. This is the selection of most interesting articles I came across.

Towards the Cloud recently published an article where they described 25+ Production-Ready Policies for 2026. I liked the idea very much so I've decided to encode these policies into my @beesolve/aws-accounts library so you can easily manage them with code.

I haven't set up a new AWS account via Create Account button for ages. Currently I am setting up new AWS accounts via code with @beesolve/aws-accounts. I want the tool to be usable for users with existing AWS Organizations and also users who are trying to onboard to AWS. That's why I needed to create new Organization myself so I could understand how the tool can help the newcomers.

Managing the AWS Organization shouldn't require you to fight CloudFormation or click through Control Tower. It should be code. That's the reason I've built a tool which lets you do exactly that. The tool is called @beesolve/aws-accounts and it is publicly available. If you manage multiple accounts and you are not satisfied with existing solutions this article might be for you.

When I created @beesolve/lambda-bun-runtime I mostly did it because it seems that the Lambda is very low on the Bun priority list and I wanted to have something which is up to date where I can fix the bugs quickly. I also wanted to provide better DX and tooling built around the CDK.

After using it for a while I realized that the approach of the official Bun's custom layer for Lambda does not align with my mindset.

As always here are some links which I found interesting and I want to share with the world.

In this article I will show you how to implement simple cron job processing using AWS Lambda and EventBridge Scheduler. We'll also look into most common problems you can hit and compare 3 different approaches of how to solve them.