Overall, AWS is crushing it this season with new goodies! My favorites are almost always incremental improvements to existing services, not so much the new products. #AWSreInvent
Let's start with the `provided.al2023` Lambda custom runtime! As someone who writes endless Lambda functions in Go, this ensures every deployed function can run unaltered for 5+ years. And existing functions running on `provided.al2` can be updated without any code updates* or recompilation. 👏 https://aws.amazon.com/blogs/compute/introducing-the-amazon-linux-2023-runtime-for-aws-lambda/
Introducing the Amazon Linux 2023 runtime for AWS Lambda | Amazon Web Services

With this launch, you can now build your Lambda functions using Amazon Linux 2023 as the custom runtime or use it as the base image to run your container-based Lambda functions.

Amazon Web Services
*I actually got bit by a function that depends on tzdata, which is preinstalled in AL2 but not in AL2023. Turns out there's a `timetzdata` Go tag you can apply when building to have it embedded in the binary. Quick fix, but unexpected! https://pkg.go.dev/time/tzdata
tzdata package - time/tzdata - Go Packages

Lambda with SQS as an event source polls 5x faster. The SQS <=> Lambda integration is magical. It was already blazing fast at moderate scale, this makes it a no-brainer at any scale. And don't worry, you can slow it down if you don't want to overload things downstream. https://aws.amazon.com/blogs/compute/introducing-faster-polling-scale-up-for-aws-lambda-functions-configured-with-amazon-sqs/
Introducing faster polling scale-up for AWS Lambda functions configured with Amazon SQS | Amazon Web Services

The improved Lambda SQS event source polling scale-up capability enables up to five times faster scale-up performance for spiky event-driven workloads using SQS queues, at no additional cost.

Amazon Web Services

Up next - Advanced logging controls for Lambda. Finally we can turn off START/END/REPORT logs, consolidate logs across functions to a single log group, and log everything with JSON.

One minor gripe with this one - the "system" logs don't all include the function name, so when logs are consolidated there's no way to know which function those entries were for. Hoping the Lambda team can sneak that into the payload #awswishlist https://aws.amazon.com/blogs/compute/introducing-advanced-logging-controls-for-aws-lambda-functions/

Introducing advanced logging controls for AWS Lambda functions | Amazon Web Services

Advanced logging controls for Lambda give you greater control over logging. Use advanced logging controls to control your Lambda function’s log level and format, allowing you to search, query, and filter logs to troubleshoot issues more effectively.

Amazon Web Services
And all that was before #awsreinvent. That brings us to Vegas! Here's a beautiful sunrise with a massive eye sore.