All news with #aws lambda tag

🚀 AWS announces Lambda MicroVMs, a new serverless compute primitive delivering VM-level isolation, near-instant launch and resume speeds, and up to 8 hours of state preservation. Built on Firecracker, MicroVMs let developers provide each user or job a dedicated, secure execution environment without managing virtualization infrastructure. MicroVM images are created from Dockerfiles and support HTTP/2, gRPC, and WebSockets, with regional availability and pay-for-use pricing.

🔔 AWS Lambda Managed Instances (LMI) now supports tag propagation to automatically apply tags to managed resources such as Amazon EC2 instances, Amazon EBS volumes, and ENIs. This enables consistent cost allocation, enforcement of service control policies, and compliance across resources provisioned by LMI. Configure the PropagateTags setting via CreateCapacityProvider or UpdateCapacityProvider in Explicit mode and provide key-value pairs; the feature is available in all commercial Regions where LMI is GA.

🛠️ Amazon CloudWatch Application Signals now ranks service health on the application map and adds new infrastructure, logs, and traces tabs on the service overview page, enabling operators to triage unhealthy services and inspect compute, log snippets, and trace details in one place. These features surface runtime indicators for Amazon EKS, Amazon ECS, AWS Lambda, and Amazon EC2, and provide curated metrics with deep links to relevant monitoring tools to speed root-cause analysis. The capabilities are available in all Regions that support Application Signals.

🔧 AWS Lambda Managed Instances (LMI) is now available in all commercial AWS Regions except Israel (Tel Aviv), Middle East (Bahrain), Middle East (UAE), and Asia Pacific (Auckland). LMI lets you run Lambda functions on managed Amazon EC2 instances to access specialized compute configurations and EC2 pricing benefits while maintaining Lambda's operational simplicity. It fully manages instance lifecycle, OS and runtime patching, routing, load balancing, and auto-scaling, and supports parallel request processing per execution environment. Customers can leverage EC2 pricing models such as Compute Savings Plans and Reserved Instances and integrate LMI with existing Lambda workflows, event sources, and observability tools.

🚦 Amazon Application Recovery Controller (ARC) Region Switch adds a Lambda event source mapping execution block to automate coordinated failover of event-driven streams across Regions. The block enables or disables Lambda event source mappings for Kinesis, DynamoDB Streams, MSK, and SQS to prevent duplicate processing. Customers can chain a disable block before an enable block, or run plans in ungraceful mode for impaired Regions. Native cross-account support lets a single plan span multiple AWS accounts.

🚀 Scheduled scaling is now available for AWS Lambda Managed Instances, using Amazon EventBridge Scheduler to set one-time or recurring adjustments to function capacity limits. This lets you proactively raise capacity before expected peaks and lower it (including to zero) during idle periods to balance performance and cost. Schedules can be created via the EventBridge Scheduler console, AWS CLI, AWS SDKs, AWS CDK, or AWS CloudFormation and are available in all Regions that support Lambda Managed Instances.

🚀 Amazon EventBridge Scheduler expands its AWS SDK integrations with 619 new API actions across 13 additional services, including support for AWS Lambda Managed Instances. This update enables customers to schedule direct API invocations for a broader set of AWS services without writing custom integration code. As a serverless scheduler, EventBridge Scheduler can manage billions of scheduled events and now supports time-based scaling of Lambda managed instances for more precise capacity control. The enhancements are generally available in all Regions where Scheduler is offered, subject to target service availability.

🚀 AWS Lambda now supports creating serverless applications with Ruby 4.0. Developers can use Ruby 4.0 as both a managed runtime and a container base image, and AWS will automatically apply updates to the managed runtime and base image as they become available. The runtime adds advanced logging controls including JSON structured logs, configurable logging levels, and the ability to target specific Amazon CloudWatch log groups. Ruby 4.0 is available in all AWS Regions, including China and AWS GovCloud (US).

🚀 AWS Lambda now offers Provisioned Mode for event source mappings that consume Apache Kafka in the Asia Pacific (Taipei) and both AWS GovCloud (US‑East) and GovCloud (US‑West) Regions. Provisioned Mode lets you provision and auto-scale a configured minimum and maximum number of event pollers so polling capacity is ready to handle sudden traffic spikes and reduce processing delays. It supports Amazon MSK and self‑managed Kafka and can be enabled via the ESM API, Console, CLI, SDKs, or CloudFormation. Usage of event pollers is billed by Event Poller Units (EPUs).

🚀 AWS has expanded Lambda durable functions into 16 additional regions, enabling developers to run orchestrated, multi-step serverless workflows closer to users and data. The feature adds primitives like steps and waits to checkpoint progress, recover from failures, and pause execution without incurring compute charges for on‑demand functions. You can enable durable functions for Python 3.13/3.14, Node.js 22/24, or Java 17+ via the API, Console, SDK, or IaC tools such as CloudFormation, SAM, and CDK.

📌 AWS Lambda now supports S3 Files, allowing functions to mount Amazon S3 buckets as file systems and perform standard file operations without pre-downloading objects. Built on Amazon EFS, S3 Files combines file-system performance with S3 scalability and durability, and multiple functions can share a mounted workspace concurrently. The integration streamlines stateful and AI/ML workflows and is configurable via console, CLI, SDKs, CloudFormation, or SAM; standard Lambda and S3 pricing applies.

🚀 AWS has made the AWS Lambda Durable Execution SDK for Java generally available, giving Java developers native tools to author resilient, long-running workflows using Lambda durable functions. The SDK automates checkpointing, supports waits of up to a year for external events, and provides durable invocation, callback integration for human/agent-in-the-loop flows, and a local testing emulator. Compatible with Java 17+, it can be deployed on Lambda managed runtimes or container images.

🚀 AWS Lambda response streaming is now available in all commercial AWS Regions, enabling the InvokeWithResponseStream API to progressively stream response payloads as they are produced. This reduces time-to-first-byte (TTFB) for latency-sensitive workloads such as LLM-based, web, and mobile applications by allowing partial responses up to a default 200 MB. Response streaming is supported via AWS SDKs, Amazon API Gateway REST APIs, Node.js managed runtimes, and custom runtimes; note that additional network transfer charges apply for the bytes streamed out over the initial 6 MB.

🚀 AWS now supports up to 32 GB of memory and up to 16 vCPUs for functions running on Lambda Managed Instances, enabling compute-intensive workloads without managing infrastructure. Customers can choose memory-to-vCPU ratios of 2:1, 4:1, or 8:1 to match CPU- or memory-heavy tasks (for example, 16, 8, or 4 vCPUs at 32 GB). The capability is available in all Regions where Lambda Managed Instances is GA and can be configured via Console, CLI, CloudFormation, CDK, or SAM.

🚀 AWS Lambda has raised the per-process file descriptor limit from 1,024 to 4,096 for functions running on Lambda Managed Instances (LMI). This 4x increase supports I/O-intensive and high-concurrency workloads by allowing larger connection pools and more simultaneous open files and sockets. The capability is available in all Regions where LMI is generally available and helps customers use managed EC2 instances with built-in routing, load-balancing, and auto-scaling without additional operational overhead.

🔍 AWS Lambda now exposes Availability Zone (AZ) metadata through a new metadata endpoint in the execution environment. Developers can retrieve the AZ ID (for example, use1-az1) to implement AZ-aware routing and prefer same-AZ endpoints to reduce cross-AZ latency. The feature supports all runtimes, custom runtimes, and container images, and works with SnapStart, provisioned concurrency, and VPC-enabled functions. Available at no extra cost in all commercial Regions.

🚀 AWS and Kiro introduce the SAM Kiro Power, an agentic-AI extension that brings serverless application development expertise directly into local development environments. It dynamically loads SAM guidance to initialize, build, deploy, and locally test Lambda-based applications while enforcing security best practices for IAM. Built-in defaults require SAM resources and Powertools for AWS Lambda for observability and structured logging, accelerating the path from prototype to production.

🚀 AWS now supports Rust on Lambda Managed Instances, enabling developers to run high-performance Rust functions on Lambda-managed EC2 instances while preserving Lambda’s operational simplicity. The integration exposes specialized compute configurations—latest-generation processors and high-bandwidth networking—and supports parallel request processing within each execution environment. Rust on Lambda Managed Instances is available today in all Regions where the service is offered.

🔔 AWS has announced the developer preview of the Lambda Durable Execution SDK for Java, enabling Java 17+ developers to build resilient, multi-step serverless applications without custom progress tracking. The SDK adds automatic checkpointing, wait primitives that suspend execution for up to a year, and durable futures for callback-based flows. Paused on-demand functions are not billed for duration, and the preview includes samples and guidance to get started.

🔍 AWS announced enhanced observability for AWS Lambda Kafka event source mappings (ESM), introducing configurable Amazon CloudWatch Logs and metrics to monitor event polling setup, scaling behavior, and processing state. The capability supports both Amazon MSK and self-managed Kafka, and offers selectable log levels plus metric groups (EventCount, ErrorCount, KafkaMetrics). Customers can view data on a dedicated ESM monitoring page and enable logs and metrics via the Console, Create/Update ESM APIs, AWS CLI, SDKs, CloudFormation, or AWS SAM; standard CloudWatch pricing applies.