@andrewlocknet Good to see CBOR get more coverage. At AWS we have been migrating AWS services to use CBOR from JSON using the AWS SDKs like the .NET SDK.
@jsneedles Great find but to be clear this affects image based Lambda functions. The manage runtime is built by taking specific folders from the image like the .NET install and our runtime bits. But the whole image including the cache are not imported into the managed runtime.
We now have .NET support for AWS Lambda response streaming. Great for APIs and AI workloads, letting you stream responses as soon as you have data. This has been a passion project of mine for a while, so I'm happy to finally get this over the line.
https://t.co/gJGdvdE8XG
I'm particularly happy with how the ASP .NET Core bridge library turned out. All you have to do is set EnableResponseStreaming to true. Combine that with the recently announced v2.0 of the MCP C# SDK, and you have an easily scalable solution for MCP HTTP servers.
We released version 13.6.0 of the https://t.co/8S9UFsM9Rh package that starts exposing some of our Aspire features for Node.js AppHost.
https://t.co/kNDudb5aRh
Kiro Crew is here! ๐ We open sourced this agent dev workspace tool today, used already by 39k users inside Amazon. This pace of this project is incredible: already at 500 contributors and 995 merged PRs in the last 2.5 weeks alone
https://t.co/CyZTFYywlO
What I love about it:
1. It starts work on its own. Cron jobs, webhooks, and messaging events kick off work with nobody at a terminal, and heartbeats watch a system until something actually needs me.
2. I can reach it from anywhere. I install one Gateway, and I can access the same agent and sessions from the desktop app, the dashboard, the CLI, Slack, Discord, or Telegram.
3. I can run it anywhere. A Mac, a container, or an EC2 instance that stays up when my laptop does not. The desktop app tunnels into whichever one I picked. Conversation history, memory, and knowledge indexes stay on that host.
4. It remembers. Tell it "always run linting before calling a change done" and that correction becomes a durable lesson, not a line of chat history that evaporates when I close the window. Failures teach it too, and after enough repetition of the same workflow it writes itself a skill. I can open the dashboard, read every lesson and skill it has accumulated, and delete the ones it got wrong.
5. It's actually safe to run at work. It enforces an OS sandbox, interactive approvals, credential redaction, and an audit log of every action.
Try it in one line, then open http://localhost:5476 and start a conversation:
curl -fsSL https://t.co/Y64nuROVlI | sh
Another AWS .NET post this week. This one on how we are making it easier to build and deploy .NET agents with Bedrock AgentCore. Our new work also includes integrations with Aspire for local emulation and deployment.
https://t.co/mD4JoFZ06U
As part of our effort to keep the AWS SDK for .NET modern, we've published a new annual schedule for adding and removing .NET target frameworks. This builds on the work in V4 to take advantage of new .NET features and improve SDK performance.
https://t.co/tadlj9w7vQ
@indy_singh_uk@ChetHusk@mjovanovictech Building and publishing containers from the dotnet CLI is a cool feature. I remember couple years ago partnering with @ChetHusk to iron out the kinks with pushing the images to ECR.
Aspire really lights up your developer experience. Today is a huge milestone as we have GA support for Typescript.
If you havenโt given it a try yet, take 5 mins to play with it!
Super easy to get started:
https://t.co/KikC1uObWN
@ICooper Sadly I don't know of a .NET native implementation. My team has talked about it several times over the years but something always comes up. I'll try and revisit the issue again.