Prem Kashyap’s Post

🚀 AWS Lambda is leveling up your local coding experience with some new VS Code features 💻 https://lnkd.in/enwEzVu4 ✨ Streamlined workflow, productivity boosts, and seamless local-cloud integration. The AWS Toolkit now includes an Application Builder for Visual Studio Code: The new goodies include: 🔷 Guided setup for your local environment 🔷 Sample apps to streamline local-cloud iteration 🔷 Configure your build and debug setting 🔷 Quick sync + full deploy of local code changes to the cloud 🔷 Local & remote function testing with shareable events 🔷 One-click build, deploy, & invoke actions 🔷 View a filter logs in your IDE This has been a HUGE collaborative effort across numerous Lambda + toolkit dev teams, product managers, UX designers, docs, multiple internal and external developers. I've been involved from the very first doc about this so SUPER happy to see this out...and there's more to come! Great work: Rahul Chaudhary, Seshu Brahma, Simon Setterstrom, Renato Valenzuela, Frederic Mbea, Jonathan Ifegunni, ruojia zhang, Vandita Patidar, Lo Wheelwright, Jie Leng, Justin Keyes, Korin Weinstok, Sisira Narayana, Ethan Marsh 🌟 #AWSDeveloper #Lambda #VSCode #CloudDevelopment #Serverless

I have a feeling this would help developers deliver features faster, than them wrestling to get Amazon Q to do it! The only thing pending is hooking it all up with a an existing CI/CD set-up, like Jenkins OR providing a guided way to build a brand new one, say with GitHub Actions #AWS #Serverless #API #Lambda #IaC #InnerLoop 

🚀 Exciting news for developers! AWS Lambda has introduced a powerful new set of enhancements for local IDE workflows, aimed at boosting productivity in Lambda-based application development. 🌐 Now, developers can easily author, build, debug, test, and deploy their Lambda applications directly from Visual Studio Code (VS Code), bringing the power of serverless to their fingertips in a streamlined, developer-friendly environment. Whether you’re just getting started with serverless or a seasoned Lambda developer, these features make it simpler than ever to manage your Lambda applications without leaving your local IDE. Say goodbye to complex workflows and hello to faster, more efficient cloud-native development! Read more here: https://lnkd.in/eT3phrtT #AWS #AmazonWebServices #AWSLambda #CloudComputing #Serverless #DeveloperExperience #DX #VSCode #Innovation

AWS Lambda is introducing an enhanced local IDE experience to simplify Lambda-based application development. The new features help developers to author, build, debug, test, and deploy Lambda applications more efficiently in their local IDE when using Visual Studio Code (VS Code). #aws #lambda #serverless #developers

TFW you deploy a package via CDK and you can see the code in the console directly instead of having to download the ZIP. Good update.

Exciting News for AWS Lambda Users! 🚀 We're thrilled to announce a major update to the AWS Lambda console: a new code editor based on Code-OSS (the open-source version of Visual Studio Code)! This integration brings a familiar and powerful coding experience directly to your browser, enhancing productivity and ease of use when building serverless applications. Key Features: - Familiar Interface: Enjoy a layout similar to the desktop version of VS Code, complete with the command palette and quick search functionalities. - Customization: Personalize your coding environment with themes and settings that match your local setup. - Amazon Q Developer Extension: Enable this feature for real-time code suggestions and insights, boosting your development efficiency. - Enhanced Workflow: View function code and test results side-by-side, streamlining development and debugging processes. This new editor is available in all AWS Regions where Lambda is offered. Dive into a seamless coding experience and elevate your serverless application development! #AWS #Lambda #CodeOSS #Serverless #CloudComputing #DeveloperTools For more details, check out the latest update on the AWS website. Citations: https://lnkd.in/gqu3NiTw

Amazon Web Services (AWS) introduced an enhanced code editing experience right in the AWS Lambda console, built on Code-OSS, the open-source version of Visual Studio Code. This update brings the familiar VS Code interface and many of its powerful features directly into the Lambda console, so you can enjoy your preferred coding environment in the cloud. 💡 What's New? 🔹 A familiar VS Code IDE interface with support for plugins, customizable themes, and an improved debugging experience—all directly in the console. 🔹 A split-screen view to seamlessly see your code and test results side-by-side, making it easier to configure and validate test events. 🔹 Support for larger function package sizes and improved visibility of environment variables. 🔹 Integration with Amazon Q Developer, an AI-powered coding assistant that offers real-time suggestions, insights, and troubleshooting tips to help you write better Lambda functions faster. This new experience makes building, testing, and deploying serverless functions even more intuitive and efficient. I personally love VS Code, and having it integrated right into the AWS Lambda Console is a game-changer. Give it a try! Happy coding! 💻💙 https://lnkd.in/dfDA6sPu #AWSLambda #Serverless #VSCode #AWS #CloudComputing #Developers

When working with AWS Lambda you will have to edit your function code. There are times when i want to quickly edit files in the AWS console and the editor there is now based on VS Code and is capable of working with bigger packaged functions. I typically edit the code used in my AWS Lambda functions locally on my laptop and then deploy to my AWS account using an Infrastructure as Code (IaC) tools like the Serverless Application Model (SAM) or Terraform. Being able to edit function code directly in the AWS console is convenient and with the latest changes a Visual Studio code interface is provided. When a Lambda function is deployed it is typically done with a zip file containing all the source code and dependencies. Previously the editor in the console would only work if the zip size was up to 3MB but now the limit is increased to 50MB which should make editing more function packages possible. Check out this article from Julian Wood on the improved AWS Lambda console editing experience. https://lnkd.in/eStkAdFu

AWS Lambda has launched a new code editing experience within its console, featuring an integration based on the Visual Studio Code Open Source (Code-OSS) editor. The Code-OSS integration delivers a coding environment like a local setup, with the ability to install preferred extensions and customize settings. Developers can now view function packages up to 50 MB directly within the console, addressing a limitation of previous Lambda editors. Although a 3 MB per file size limit remains, this change allows users to handle functions with extensive dependencies better. #osseditor #aws #awslambda #lambda #codeeditor #infoq https://lnkd.in/ecX-6dd9

Excited about .NET Aspire but not a Visual Studio user? You can use JetBrains Rider and the newly released .NET Aspire plugin https://lnkd.in/duwXZtRj The ability to uses OpenTelemetry trace information to create an architectural diagram is quite neat. The plugin is open-course and the code can be found in this GitHub repo https://lnkd.in/dUeJ_KcU Want a free license of Rider? Join the Productive C# membership and on top that get access to practical videos and benefits to become a software engineering leader. https://lnkd.in/gwPyhXb Don't forget to like and repost the content to help other Rider users start developing cloud apps using .NET Aspire. #csharp #dotnet #rider #jetbrains #dotnetaspire