David Behroozi

For example, if x-forwarded-for is set to 127.0.0.1,205.33.27.32 you get 127.0.0.1 at Lambda. Lambda doesn't seem to mess with other headers that are comma separated, just x-forwarded-for.

I discovered that if you use Lambda furls, the x-forwarded-for header is truncated to the leftmost value. If you front your furl with CloudFront, the ip in that header is spoofable. CloudFront appends the viewer ip to the value of x-forwarded-for. Workaround is: github.com/aws-samples/...

TIL I was still using http 1.1 to connect to my api which supported http3. Because http3 is still kind of broken in Firefox: bugzilla.mozilla.org/show_bug.cgi... and when you enable http3 in CloudFront using the CDK, it disables http2. github.com/aws/aws-cdk/...

TIL you can get edge location in your CloudFront Functions. docs.aws.amazon.com/AmazonCloudF...

Hello darkness my old friend. I just updated to JQuery 4.0.0. Ready for 10 more years of $.

Just turned it on, TIL too, thanks!

The places where nexus share breaks the thread into posts always seems unnatural. Consider breaking it on sentence boundaries or something more organic.

Fwiw, when I was in this situation, Fi support did some things but nothing changed and ultimately I had to wait 7 days before I was able to resubscribe. I didn't lose my storage however, it was still there when I resubscribed.

They really do need to do this instead of letting Fi takeover the subscription. I causes problems like when you downgrade Fi and lose a benefit, you can't resubscribe (i.e. Google One) for 7 days until Fi releases the hold. And while you can't resubscribe they tell you you will lose your storage!

PSA: There is a performance penalty when using named exports with ESM import vs. require on built-in node modules. This is why the AWS JavaScript V3 SDK has 50 ms slower Lambda coldstarts on Node 22+. Some notes here: github.com/aws/aws-sdk-...

Look, the plating and bread choice leaves room for improvement. But the flavor of my latest Persian-American cuisine; the sumac avocado toast slaps.

After many exasperated console.log's I looked at the docs and discovered CloudFront functions don't run on responses with a status code >= 400. So my edge metrics only work on successful requests. docs.aws.amazon.com/AmazonCloudF...

Seeing some Dr. Suess bird in my latte this morning

When I tried in us-east-2 I got an error that it wasn't enabled for my account. Both via cloudformation and the console.

Aaron's foray into the fast and furious franchise.

2025 year in review - Speedrun A fun look back on 2025

Ode to 2025. My pithy year in review. "May your 2026 involve some hand-written code and may it compile without errors." speedrun.nobackspacecrew.com/blog/2026/01...

It's important to know someone in London. Eventually you'll need their help unsubscribing from Domino's UK marketing because the US is region blocked 😂.

I swear AWS had some hero image on a docs site with this hotel carpet vibe once.

The embedded metrics format allows me to combine metrics with metadata. I mainly use metrics and request logs only, never traces so it's a good encapsulation of what I need: docs.aws.amazon.com/AmazonCloudW...

Rerun the benchmark? · Issue #1166 · awslabs/llrt Is it possible to rerun the benchmark with the latest release? Since January 2024, the llrt binaries have grown 2+ MB. I've been doing some coldstart benchmarking to compare LLRT standard sdk with ...

E2E can vary across runtimes because there is overhead not measured in init duration. I.e. pulling the bits from s3 is not included. So something that has 61ms init could actually be 225ms to the client. See llrt/node comparison here: github.com/awslabs/llrt...

I'm using LLRT with hono for my REST api. For SSR, I do it manually (using template literals). I don't have an immediate need for this, but always appreciate new fast ways of doing things. Have you measured E2E time from the client in addition to Init Duration?

Took a quick break from the curiosities of London to have a curry and a pint with Cloudflare's lord of logs and corduroy trousers @ankcorn.dev

A short story:

1. This showed up in the group chat
2. Replied with "Nicolas UNCAGED?"
3. Checked El goog to see if this pun was a world first
4. Alas

Logging for scale - Speedrun Using request logs to understand your service at scale

That way you can validate the logs have the necessary fields to answer operational questions. There's lots of material out there on wide events: speedrun.nobackspacecrew.com/blog/2023/09...

So the wide events that Boris discusses largely have that context (with error_code remediation described in an easily editable doc like a wiki). If your devs aren't giving the context, you might request they submit sample logs for successful and failed requests during qa/code review.

Boris is still at it and still gets it. Logging properly is on you and rn your: loggingsucks.com

The answer to why account based endpoints didn't reduce the blast radius of the DynamoDb Oct event was in DAT458. They don't point to cells yet, they still point to the regional endpoint🤦‍♂️. youtu.be/YZUNNzLDWb8?...

Being able to deeplink would be useful too, like cloudwatch insights.

I'm relishing using AI to click the bait for me.

Clearly the old spice product marketing team was cut from the same cloth as me.