Norm Johanson

.NET 10 runtime now available in AWS Lambda | Amazon Web Services Amazon Web Services (AWS) Lambda now supports .NET 10 as both a managed runtime and base container image. .NET is a popular language for building serverless applications. Developers can now use the ne...

Starting the year strong at AWS for .NET with .NET 10 support Lambda. A new feature we added for .NET 10 is support for writing C# file based Lambda functions. Would love to hear feedback on the new support.

aws.amazon.com/blogs/comput...

AWS Enhancements Check out the latest enhancements to NServiceBus support for AWS. All of these updates aim to give you more control, fewer surprises, and a smoother experience when building distributed message-based…

A lot of really cool AWS .NET enhancements for NServiceBus. I especially appreciate the support for our Lambda Annotations framework.

particular.net/blog/aws-enh...

Congrats!

YouTube video by James Eastham Master Local Async Lambda Development with .NET Aspire

Another video from @jameseastham.co.uk showing off the power of combining AWS and .NET Aspire.

www.youtube.com/watch?v=Jxj2...

YouTube video by James Eastham Simplify your local AWS Lambda development with .NET Aspire

Great video by @jameseastham.co.uk showing off our AWS Lambda support for .NET Aspire. Making it easy to local develop and debug your .NET Lambda functions.

www.youtube.com/watch?v=Ph9w...

Thanks, added to the issue my reasoning for asking.

Is there any plans to support "dotnet publish App.cs" to get a deployment bundle for the single file application?

We don't have support of TypeScript CDK. It Is something we should look into. For now I think your suggestion of referencing the generated CloudFormation template is problem the way to go.

I hear you. I have been battling the flu for almost a week now :(

General Availability of AWS SDK for .NET V4.0 | Amazon Web Services Version 4.0 of the AWS SDK for .NET has been released for general availability (GA). V4 has been in development for a little over a year in our SDK’s public GitHub repository with 13 previews being re...

V4 of the AWS SDK for .NET is GA today! It is an evolutionary major version bump with significant performance improvements. aws.amazon.com/blogs/develo...

AWS Lambda and .NET Aspire | Serverless Office Hours - aws on Twitch aws went live on Twitch. Catch up on their Talk Shows & Podcasts VOD now.

To see AWS Lambda and .NET Aspire in action together here is the recording of my appearance on the AWS Twitch channel diving deep into our support.

www.twitch.tv/videos/24275...

Support for SQS event source in our .NET Aspire integration for AWS Lambda. Available in version 9.1.6 for our hosting NuGet package nuget.org/packages/Asp...

AWS - Twitch Tech Tales S04E08 - The Tale of EC2 Graviton Migrations

I'll be on the AWS Twitch channel for the AWS Serverless office hours tomorrow, April 8th, at 11:00 am PST. I'll be talking about Lambda with .NET Aspire. Come check out what we have built and ask questions about Lambda + Aspire or .NET Lambda in general.

www.twitch.tv/aws

Just tried this out in one of my personal projects, and it found two bugs that I wasn’t otherwise aware of in my own code within 5 minutes 😅

That is great to hear!

Building and Debugging .NET Lambda applications with .NET Aspire (Part 2) | Amazon Web Services In Part 1 of our blog posts for .NET Aspire and AWS Lambda, we showed you how .NET Aspire can be used for running and debugging .NET Lambda functions. In this part, Part 2, we’ll show you how to take ...

Part 2 in my blog posts for AWS Lambda and .NET Aspire is out. This goes beyond simple testing of Lambda functions to how you can take advantage of the .NET Aspire programming model for tying together components and OpenTelemetry.

aws.amazon.com/blogs/develo...

#dotnet #aspire

We released developer preview of our AWS Lambda support for .NET Aspire. I'm excited about what we can do with .NET Aspire and Lambda.

Here is part 1 blog post of a 2 part series on taking advantage of .NET Aspire when developing .NET Lambda functions.

t.co/RNcSBvo7KJ

What about allowing integrations to add metadata that would show up on the lines of the graph? For example an integration where different Aspire resources handle different HTTP resource paths. I think it would make the graph more useful to see what the purpose of the connections were.

Integrating AWS with .NET Aspire | Amazon Web Services .NET Aspire is a new way of building cloud-ready applications. In particular, it provides an orchestration for local environments in which to run, connect, and debug the components of distributed appl...

New post talking about what AWS features we have been building for .NET Aspire. Including the recent addition of integrating DynamoDB local into your Aspire application. aws.amazon.com/blogs/develo...

Love to hear about your results trying it out.

In our testing we are seeing significant allocation reduction for JSON based services like DynamoDB and SQS.

For the DynamoDB Native AOT changes I saw with the code below my cold start improve from 1,700 ms to 500 ms by using Native AOT with the DynamoDB high level libraries.

V4 Development Tracker · Issue #3362 · aws/aws-sdk-net V4 Development Tracker This issue is for tracking the changes being made for V4 of the AWS SDK for .NET. Development of V4 is happening in the v4-development branch in this repository. V4 is an evo...

Preview 6 of the V4 version of the AWS SDK for .NET is out. The big changes in this preview is the DynamoDB high level libraries now support Native AOT and the SDK is now using System.Text.Json for serialization. github.com/aws/aws-sdk-...

Announcement: S3 default integrity change · Issue #3610 · aws/aws-sdk-net In AWS SDK for .NET package AWSSSDK.S3 version 3.7.412.0, we released changes to the S3 client that adopts new default integrity protections. For more information on default integrity behavior, ple...

Last week the AWS SDKs including the .NET SDK updated data integrity checks for S3. The changes are transparent to existing code but if you are using S3 emulators you might run into problems. The announcement below has the details and how disable if you need to.

github.com/aws/aws-sdk-...

First year not going to reinvent so I actually had time to do the Seattle marathon.

I’m sure there has been conversations but I haven’t been part of them. It would be a pretty big change to programming model particular with the runtime client and reporting back to the Lambda service. It is one of those ideas that sounds simple but gets complicated fast on the implementation side.

There is a lot gray area between small single purpose Lambda function and monolithic that will also benefit. I can imagine a function that pulls an object from S3 and render's a PDF is single purpose but with the library warm up cost that could have a significant cold start that SnapStart would help

Imagine there is roughly a flat time spent on the restore. If your cold start was already faster than that flat time you won't see a benefit. If your cold start was greater than that flat time you will see a difference. The farther your cold start was from that flat time the bigger difference.

SnapStart is really impactful for cold starts that are multi seconds reducing them to less than second. If your function was already sub second then you aren't likely to see a benefit.

AWS Lambda SnapStart for Python and .NET functions is now generally available | Amazon Web Services AWS Lambda SnapStart boosts Python and .NET functions' startup times to sub-second levels, often with minimal code changes, enabling highly responsive and scalable serverless apps.

Continuing to make .NET a powerful Serverless platform we have added SnapStart support to our .NET AWS Lambda managed runtime. For those hesitant to use .NET for serverless due to cold start performance SnapStart can be a game changer.

aws.amazon.com/blogs/aws/aw...