Norm Johanson
banner
normj.bsky.social
Norm Johanson
@normj.bsky.social
190 followers 46 following 30 posts
I work at AWS, making .NET great on AWS. All opinions expressed are my own.
Posts Media Videos Starter Packs
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...
Simplify your local AWS Lambda development with .NET Aspire
YouTube video by James Eastham
www.youtube.com
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 :(
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...
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.
www.twitch.tv
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...
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
AWS - Twitch
Tech Tales S04E08 - The Tale of EC2 Graviton Migrations
www.twitch.tv
Reposted by Norm Johanson
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 😅
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
https://aws.amazon.com/blogs/developer/building-lambda-with-aspire-part-1/
t.co
That is great to hear!
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
https://aws.amazon.com/blogs/developer/building-lambda-with-aspire-part-1/
t.co
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.
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.
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-...
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...
github.com
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.