All news with #aws lambda tag

🚀 Vinext 1.0 general availability brings a Vite-backed framework that makes Next.js apps portable to multiple platforms including Cloudflare Workers, Netlify, and AWS Lambda. The release improves compatibility, stability, and caching, supports both App and Pages routers, and adds build-time prerendering plus page-level ISR. Migration is simplified with two commands and a broad test suite ensures ongoing compatibility with Next.js.

🔔 The updated Amazon EventBridge Custom event bus is a serverless event broker that enables scalable, decoupled event-driven applications. It supports cross-account sharing via AWS Resource Access Manager, strict ordering, CloudEvents JSON formats, built-in retention up to one year, and advanced transformations. A new Subscriber resource can filter and deliver events to over 250 AWS services, and a revised pricing model charges for data transfer rather than per-event.

🛡️ AWS Lambda durable functions are now available in the AWS European Sovereign Cloud, enabling developers to build reliable multi-step applications and AI workflows within the Lambda developer experience. These functions introduce primitives like step and wait to checkpoint progress, recover from failures, and pause executions without incurring on-demand compute charges. Support covers new Python (3.13, 3.14), Node.js (22, 24), and Java (17+) runtimes, and activation is possible via the AWS Lambda API, Console, SDKs, and IaC tools such as AWS CloudFormation, AWS SAM, and AWS CDK.

🚀 The new AgentCore Runtime for Amazon Bedrock AgentCore is now generally available, introducing elastic memory management that reclaims unused memory and consistent cold start times regardless of container image size. It preserves serverless benefits—no pre-provisioning, scale-to-zero, hardware-enforced isolation, and pay-for-use—while lowering costs and speeding startup. Sessions begin with a compact memory profile and expand on demand; idle memory is reclaimed. Snapshot-based cold start restoration delivers P75 cold starts of ~1.9–2.0s across 200 MB–2 GB images in tests. The runtime is available in select regions and can be enabled by setting platformVersion to V2 when creating or updating a runtime.

🛠️ AWS Step Functions now automatically adds AWS SDK integrations for newly released AWS services and capabilities within weeks, starting with AWS Lambda MicroVMs and AWS Lambda Core. This lets you orchestrate the latest AWS services from workflows without waiting for manual updates. The integrations are generally available in all Regions where Step Functions is offered, though specific APIs depend on regional service availability. Continuous updates mean AWS will no longer publish What's New posts for these SDK integration updates.

📢 AWS Lambda now supports configurable direct reads for Amazon S3 Files, letting you choose whether functions read from S3 Files high-performance storage or directly from your S3 bucket. This setting enables optimizing throughput and latency per application by routing large reads (≥1 MB) directly from the bucket for maximum throughput when enabled, or serving all reads from high-performance storage for lowest latency when disabled. The feature is available across most AWS commercial and GovCloud regions and can be configured via Console, CLI, SDKs, or CloudFormation with no additional charge beyond standard pricing.

🔒 AWS Lambda recursive loop detection is now supported in Europe Sovereign Cloud, helping prevent unintended billing by automatically detecting and stopping recursive invocations between Lambda functions and supported services. The feature covers common event sources like Amazon S3, Amazon SQS, and Amazon SNS, and halts processing when a loop is detected while sending an AWS Health Dashboard notification with troubleshooting guidance. Recursive loop detection is enabled by default for Lambda functions using a supported SDK version, and can be disabled per function using the PutFunctionRecursionConfig API for intentional recursion.

🛠️ AWS Lambda durable functions now integrates with Pydantic AI, enabling Python AI agents to persist progress and resume after interruptions. Each model and tool call becomes a durable execution step, preventing repeated work and avoiding duplicate costs or side effects. The integration is available in all Regions where Lambda durable functions run and can be used in any Python Lambda durable function.

🚀 AWS Lambda now supports AWS Graviton5-powered C9g, C9gd, M9g, and M9gd instances on Lambda Managed Instances, delivering up to 25% better compute performance versus Graviton4. Lambda Managed Instances lets you run Lambda functions on EC2 while retaining Lambda’s operational simplicity, with infrastructure tasks fully managed. You can specify Graviton5 instance types when creating a capacity provider or leave the instance type as default so Lambda can select Graviton5 based on function configuration. Support is available in all Regions where both Lambda Managed Instances and the listed EC2 instances are offered.

🚀 AWS Lambda now supports a 90-minute function timeout for asynchronous and event source mapping (ESM) invocations on Lambda Managed Instances (LMI), increasing the previous 15-minute limit sixfold. This change enables longer-running workloads such as data processing, media transcoding, financial calculations, AI inference, and batch jobs without re-architecting applications. Configuration is available via the AWS Lambda Console, CLI, API, IaC tooling, or the Agent Toolkit. Synchronous invocations remain limited to 15 minutes; the feature is available in all Regions that support LMI.

🛠️ The AWS Model Context Protocol Server (AWS MCP Server) now supports a serverless capability enabling coding agents like Claude Code and Kiro to diagnose AWS Lambda functions and connected resources. The capability lets agents inspect Lambda, Amazon API Gateway, EventBridge, S3, DynamoDB, SNS, SQS, and Step Functions, correlate errors against a 7-day baseline, surface recurring errors, retrieve deployed configurations, provide change timelines, and analyze latency. It reduces token usage by aggregating comprehensive data in a single call. The MCP Server is available via the Agent Toolkit for AWS or as a standalone installation and can access services in all commercial AWS Regions while running in US East (N. Virginia) and Europe (Frankfurt).

🚀 Starting today, AWS Lambda supports SnapStart for functions packaged as container images, cutting startup times from several seconds to sub-second for latency-sensitive workloads. SnapStart snapshots an initialized execution environment at deployment and resumes from the cache on invocation, avoiding full reinitialization. The feature is opt-in and available in most commercial AWS Regions, and can be enabled via Console, CLI, APIs, and IaC tools.

🛡️ AWS Lambda recursive loop detection is now available in all commercial AWS Regions. This default-enabled guardrail detects and stops recursive invocations between Lambda functions and supported event sources like Amazon S3, Amazon SQS, and Amazon SNS, preventing runaway workloads and unexpected costs. When a loop is detected, Lambda halts processing and sends an AWS Health Dashboard notification with troubleshooting guidance. You can disable detection per function using the PutFunctionRecursionConfig API if intentional recursion is required.

🔒 AWS Lambda MicroVMs now support AWS PrivateLink, enabling private connectivity from Amazon VPC resources to Lambda MicroVMs without exposing traffic to the public internet. This helps regulated workloads in financial services, healthcare, and government meet strict network isolation requirements when building with MicroVMs. PrivateLink VPC Endpoints allow creation and invocation of MicroVM APIs and access to each MicroVM’s HTTP endpoint. Endpoints can be created via the Console, CLI, CloudFormation, or SDKs and are supported in all Regions where Lambda MicroVMs are available.

🔔 AWS Lambda has opened public preview for managed runtimes starting with Node.js 26 and Python 3.15. This preview lets customers, partners, and language communities test upcoming runtimes and provide feedback before general availability. Preview runtimes may change and are not covered by the Lambda SLA or AWS support plans, so they should not be used for production. The preview uses the same runtime identifiers as GA, enabling automatic graduation when released.

🔒 AWS Lambda functions now support full Identity and Access Management (IAM) resource-based policies, enabling platform and security teams to define granular permissions for multiple principals and actions within a single policy. This replaces the previous per-principal permission model and permits the use of the full range of IAM condition keys, such as source IP or principal tag restrictions. Policies can be managed via the Lambda console JSON editor, AWS CLI, SDKs, CloudFormation, and SAM. The feature is available in all AWS commercial Regions at no extra cost.

🚀 AWS Lambda MicroVMs are now available in five additional Regions: Asia Pacific (Mumbai), Asia Pacific (Singapore), Asia Pacific (Sydney), Europe (Frankfurt), and Europe (Stockholm), bringing availability to 10 Regions in total. Lambda MicroVMs deliver VM-level isolation, near-instant launch and resume speeds, and state preservation so developers can run isolated, stateful workloads without managing virtualization. Developers create a MicroVM image from a Dockerfile and launch per-user or per-job MicroVMs with dedicated HTTPS URLs supporting HTTP/2, gRPC, and WebSockets via the Lambda console, CloudFormation, CDK, or Agent Toolkit for AWS.

🛡️ Today AWS announces the general availability of Role Manager, a capability in AWS Identity and Access Management (IAM) that automatically creates or reuses IAM roles required by supported AWS service consoles. Role Manager can be enabled or disabled at any time and exposes the AWS-managed templates it deploys. At launch it supports six service consoles, including AWS Lambda and Amazon EventBridge, and is available in all Regions except AWS GovCloud (US) and China Regions.

🛠️ AWS Lambda console now extends console-to-IDE integration to support Kiro and Cursor IDEs, building on earlier Visual Studio Code support. Developers can follow a guided setup from the Lambda console to start local development in Kiro or Cursor while preserving code and configurations. The integration also enables conversion to AWS SAM templates to simplify IaC and CI/CD workflows. This feature is available in all commercial AWS Regions at no additional cost.

🚀 AWS Lambda now supports scalable network bandwidth for functions outside a VPC with 2 GB+ memory, enabling throughput to scale from 625 Mbps at 2 GB up to 3,000 Mbps at 10 GB. This reduces transfer times for latency-sensitive and high-volume data-processing workloads, helping lower execution time and per-invocation cost. Enable the feature via AWS Service Quotas under the Network bandwidth per execution environment quota; it is available at no additional charge in all commercial Regions.