All news with #aws lambda tag

🛡️ AWS outlines core concepts and a hands-on walkthrough for implementing security response automation to detect and remediate threats across AWS environments. The post maps automation to the NIST Cybersecurity Framework and demonstrates a CloudFormation deployment using EventBridge, Lambda, GuardDuty, and Security Hub to automatically restart CloudTrail and notify operators. It also highlights the Automated Security Response library, testing guidance, and cost and cleanup considerations.

🔁 AWS Lambda now supports cross-account access for DynamoDB Streams event-source mappings, enabling streams in one account to trigger Lambda functions in another. By attaching a resource-based policy to a DynamoDB stream, owners can grant functions in other accounts permission to consume change events without replicating data. The capability is generally available across AWS Commercial and AWS GovCloud (US) Regions and can be configured via the Console, CLI, SDKs, CloudFormation, or APIs. This reduces operational overhead and simplifies multi-account event-driven architectures.

🚀 AWS Lambda now supports creating serverless applications using .NET 10 as both a managed runtime and a container base image, with AWS automatically applying updates to the managed runtime and base image as they become available. .NET 10 is a long-term support release with security and bug fix coverage through November 2028, and it brings features such as file-based apps. The release also adds support for Lambda Managed Instances, enabling functions to run on Amazon EC2 while retaining serverless operational simplicity, and Powertools for AWS Lambda (.NET) supports the new runtime. The runtime is available in all Regions, including AWS GovCloud (US) and China, and you can deploy using the Lambda console, AWS CLI, AWS SAM, AWS CDK, and CloudFormation.

📣 AWS Lambda now offers durable functions in 14 additional Regions, enabling developers to build reliable multi-step applications and AI workflows closer to users and data. Durable functions add primitives such as "steps" and "waits" to checkpoint progress, recover from failures, and pause execution without incurring compute charges for on-demand functions. Activation is available for new Python (3.13, 3.14) and Node.js (22, 24) functions via the API, Console, SDK, or Infrastructure as Code tools like CloudFormation, SAM, and CDK.

🔁 AWS announced Lambda durable functions, a built-in capability for authoring reliable multi-step applications and AI workflows within the Lambda developer experience. Durable functions automatically checkpoint execution, can suspend runs for up to one year, and recover from failures without requiring additional infrastructure. New primitives like steps and waits let developers pause and resume logic without incurring compute charges, while the service handles state and error recovery so teams can focus on business logic.

⚙️ AWS Lambda Managed Instances lets you run Lambda functions on Amazon EC2 instances while preserving Lambda's serverless operational model. AWS fully manages instance lifecycle tasks — including OS and runtime patching, routing, load balancing, and autoscaling — and exposes the broad EC2 instance catalog (including Graviton4 and high‑bandwidth networking). You attach functions to a configurable capacity provider via Console, APIs or IaC, and the service integrates with CloudWatch, X‑Ray and AWS Config; current Java, Node.js, Python and .NET runtimes are supported. The feature is now available in US East (N. Virginia, Ohio), US West (Oregon), Asia Pacific (Tokyo) and Europe (Ireland).

🆕 AWS Lambda now supports creating serverless applications with Node.js 24, available as both a managed runtime and a container base image. AWS will automatically apply updates to the managed runtime and base image as they become available, and the runtime is offered in all Regions including GovCloud (US) and China. The release emphasizes modern async/await handlers and removes callback-based handlers; Lambda@Edge and Powertools for AWS Lambda (TypeScript) are also supported, and standard AWS deployment tools (Console, CLI, SAM, CDK, CloudFormation) can be used to deploy Node.js 24 functions.

🔁 AWS Lambda now offers enhanced error handling for Amazon Managed Streaming for Apache Kafka (MSK) and self-managed Kafka event sources, enabling developers to define custom retry configurations and route failed messages to a Kafka topic as an on-failure destination. The update extends Kafka event source mapping (ESM) in Provisioned mode to support retry limits, time-bound retry windows, automatic discards of exceeded records, and per-message failure reporting to optimize retries. Configure these settings via the ESM API, AWS Console, or AWS CLI.

🔗 AWS announced integration of AWS Lambda Kafka event source mapping directly in the Amazon MSK Console, allowing you to connect MSK topics to Lambda functions without switching consoles. The MSK Console now requires only a topic and target function while automatically creating and configuring the event source mapping (ESM), applying optimized defaults and optional IAM role generation. The integration defaults to Provisioned Mode to improve latency and throughput, and is generally available in most AWS Commercial Regions with a few regional exceptions.

⚡ AWS announces enhancements to Lambda's Provisioned mode for Kafka event source mappings, enabling grouping of ESMs and higher density of event pollers to reduce costs by up to 90% for low-throughput workloads. Each Event Poller Unit (EPU) still provides 20 MB/s but now defaults to 10 pollers per EPU and supports shared capacity via the new PollerGroupName parameter. Changes are available today across AWS Commercial Regions and can be configured via API, CLI, Console, SDK, CloudFormation, or SAM.

🔒 AWS announced a new tenant isolation mode for AWS Lambda, enabling customers to isolate request processing per tenant or end-user invoking the same function. By providing a unique tenant identifier on invocation, Lambda routes requests to execution environments dedicated to that tenant and ensures those environments are never used for other tenants. This simplifies building multi-tenant SaaS workloads and reduces the need for custom per-tenant function routing.

🔔 AWS Lambda now supports Python 3.14 for both managed runtimes and as a container base image. AWS will automatically apply updates to the managed runtime and base image as they become available, reducing maintenance overhead. The runtime is available in all Regions, including AWS GovCloud (US) and China Regions, and is supported for Lambda@Edge in applicable Regions. Developers can deploy using the Lambda console, AWS CLI, AWS SAM, AWS CDK, and CloudFormation, and Powertools for AWS Lambda (Python) also supports Python 3.14.

🔔 AWS Lambda now offers Provisioned Mode for SQS event-source mappings (ESMs), letting you provision persistent event pollers to handle sudden traffic spikes. Provisioned ESMs scale up to 3x faster (up to 1,000 concurrent executions/min) and support up to 16x higher concurrency (up to 20,000 concurrent executions), reducing latency for bursty workloads. The feature is generally available in all AWS Commercial Regions and is configurable via the Console, API, CLI, SDK, CloudFormation, and SAM; billing is by Event Poller Units (EPU).

🚀 AWS has declared Rust support in AWS Lambda Generally Available, promoting the runtime out of its prior experimental status and making it suitable for production workloads. The GA release is backed by AWS Support and the Lambda SLA and is available in all AWS Regions, including GovCloud (US) and China. Rust on Lambda delivers high performance, memory efficiency, and compile-time safety for serverless functions. Developers can now build business-critical serverless applications in Rust while leveraging Lambda's event integrations, fast scaling from zero, automatic patching, and usage-based pricing.

🚀 AWS Lambda now supports Java 25, using the latest long‑term support distribution from Amazon Corretto. The runtime is available as a managed runtime and as a container base image, and AWS will automatically apply updates to each as they are released. The release introduces new language features and performance improvements, including Ahead‑of‑Time caches and adjusted tiered compilation defaults. Lambda Snap Start and Powertools for AWS Lambda (Java) support Java 25, and the runtime is available in all Regions, including GovCloud (US) and China.

🔧 The AWS Serverless Model Context Protocol (MCP) Server now includes specialized tools to configure and manage AWS Lambda event source mappings (ESM), combining AI assistance with ESM expertise. The new toolset—comprising the ESM guidance tool, the ESM optimization tool, and an ESM Kafka troubleshooting tool—translates high-level throughput, latency, and reliability requirements into concrete ESM configurations and generates optimized AWS SAM templates. It also validates VPC network topology for VPC-based event sources and diagnoses common ESM issues to streamline setup, tuning, and troubleshooting workflows.

🚀 AWS has increased the maximum payload size for AWS Lambda asynchronous invocations from 256 KB to 1 MB. This change lets customers deliver richer, complex events—such as LLM prompts, telemetry batches, or detailed JSON outputs—without splitting, compressing, or externalizing data. The increase is generally available in all AWS Commercial and AWS GovCloud (US) Regions and can be used via the Lambda invoke API. Billing counts 1 request for the first 256 KB and an additional request per 64 KB chunk beyond that up to 1 MB.

🧪 Amazon Kinesis Data Streams now integrates with AWS Fault Injection Service (FIS) to simulate Kinesis API errors and validate application error handling, retry logic, and monitoring. Customers can induce throttling, internal errors, service unavailable, and expired iterator exceptions—covering 500, 503, and 400 responses for GET and PUT operations—to test resilience and CloudWatch alarms. FIS experiments support templates, CI integration, and automatic stop thresholds to keep tests controlled, and are generally available in all Regions where FIS is offered, including AWS GovCloud (US).

🔐 AWS Lambda now supports code signing in AWS GovCloud (US-West and US-East) through the managed AWS Signer service. Lambda validates signatures at deployment to ensure code has not been altered and that it originates from trusted signers. Administrators can create Signing Profiles, bind allowed profiles to functions, and configure whether failed signature checks produce warnings or reject deployments. Access and permissions are controlled via IAM, and there is no additional charge to use this capability.

⚙️ AWS Step Functions now expands Distributed Map input sources and adds visibility metrics. Distributed Map can now iterate S3 objects via S3ListObjectsV2, read AWS Athena data manifests and Parquet files directly, and extract arrays from JSON stored in S3 or passed as state input. New observability metrics — Approximate Open Map Runs Count, Open Map Run Limit, and Approximate Map Runs Backlog Size — provide operational insight. These features are available in all commercial AWS Regions; enable Distributed Map mode in the Step Functions console and consult the developer guide for examples.