All news with #aws lambda tag

🚀 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.

🧬 AWS HealthOmics now supports task-level timeout for Workflow Description Language (WDL) workflows, letting users set maximum execution durations for individual tasks. The new omicsTimeout runtime attribute can be added to any task's runtime section and accepts standard time units (e.g., 90s, 2h, 1d). When a task exceeds the specified duration, HealthOmics stops the task and marks the task and run as failed, helping control costs and enable automated error recovery.

🚀 AWS Lambda increases the maximum event pollers for Provisioned Mode SQS event source mappings from 2,000 to 10,000, enabling up to 100,000 concurrent invocations per ESM. This change helps developers build highly responsive, large-scale event-driven applications for use cases like real-time order processing, financial pipelines, IoT telemetry ingestion, and fan-out workloads. The feature is generally available in all AWS Commercial Regions and is configurable via the ESM API, Console, CLI, SDKs, CloudFormation, and SAM. Billing for pollers continues to use the Event Poller Unit (EPU) pricing model.

🛠️ AWS Lambda now supports Java 8, Java 11, and Java 17 runtimes on Amazon Linux 2023 (AL2023), available as managed runtimes and container base images. These AL2023-based runtimes let customers migrate from Amazon Linux 2 (AL2) without having to upgrade their Java version immediately. AL2 reached end of life on June 30, 2026; AL2-based Java runtimes will receive critical and selected important patches until June 30, 2027 to assist migration.

🚀 AWS CodeDeploy is now available in five additional AWS Regions: Asia Pacific (New Zealand), Asia Pacific (Thailand), Asia Pacific (Taipei), Asia Pacific (Malaysia), and Mexico (Central). The fully managed deployment service automates application rollouts to Amazon EC2, on-premises servers, AWS Lambda, and Amazon ECS, enabling lower latency and helping meet data residency needs for customers in these regions. CodeDeploy now operates across 34 commercial regions plus AWS GovCloud (US) and the AWS China Regions.

📣 AWS Lambda now sends logs for Lambda Managed Instances (LMI) capacity providers to Amazon CloudWatch Logs, providing visibility into scaling activity and instance lifecycle operations. LMI lets you run Lambda functions on Amazon EC2 instances while keeping serverless operational simplicity. Capacity provider logs capture structured JSON lifecycle events like launches, terminations, and health checks to help monitor, troubleshoot, and optimize managed EC2 resources. Logs are enabled by default across supported AWS Commercial Regions and incur standard CloudWatch Logs charges.

🔧 AWS has announced the general availability of the AWS Lambda Durable Execution SDK for .NET, enabling C# developers to build resilient, long-running workflows using Lambda durable functions. The SDK provides idiomatic C# constructs for progress checkpointing, durable invocation, callbacks for human or agent-in-the-loop workflows, and suspension waits of up to a year. It installs via NuGet, includes a local testing emulator for debugging, and supports common multi-step scenarios like payment pipelines and AI orchestration.

🔒 AWS Lambda durable functions now support encrypting durable execution data with an AWS KMS customer managed key. Durable functions let you run long-lived workflows with automatic state management; execution state is encrypted at rest by default with an AWS‑owned key. With this update you can select and manage your own KMS key for execution data, enabling separate control of rotation and access for execution history and state. The feature is available in all Regions where durable functions exist; standard AWS KMS charges apply.

🔔 AWS Secrets Manager now publishes events to Amazon EventBridge when secret values change, enabling event-driven responses without parsing CloudTrail. You can create EventBridge rules to detect active secret value changes and route them to targets like AWS Lambda, Amazon SNS, Amazon SQS, or Amazon Step Functions. Notifications are published to the default event bus automatically, require no opt-in, and are available in all Regions where AWS Secrets Manager is offered at no extra cost.

🛠️ Amazon RDS for SQL Server now supports Microsoft SQL Server 2025 across Enterprise, Standard, and Developer editions. SQL Server 2025 integrates AI into the database engine, enabling T-SQL to call external REST endpoints and work with AWS services like Amazon Bedrock, Amazon SageMaker, Amazon S3, and AWS Lambda. Standard Edition capacity and features have been expanded, and a new free Developer edition is available for testing.

🔔 Amazon S3 Event Notifications now include system-generated tags in events delivered to destinations such as Amazon EventBridge, Amazon SQS, Amazon SNS, and AWS Lambda. These tags are metadata labels applied to buckets by AWS services and can be used to filter events across thousands of buckets with a single EventBridge rule rather than listing each bucket individually. Enable S3 Event Notifications via the AWS Management Console, SDK, or CLI; tags already applied by services like AWS CloudFormation are automatically included in new notifications. This capability is available at no additional cost in all AWS Regions and requires no configuration changes.

🛠️ AWS Lambda now supports referencing code directly from your own Amazon S3 buckets using self-managed code storage, removing the prior requirement for Lambda to copy deployment packages into Lambda-managed storage. This change eliminates the previous 75GB default storage constraint (now raised to 300GB) and can reduce function activation time by avoiding the copy step. No additional Lambda charges apply; you pay standard S3 storage and any applicable data transfer fees.

🔔 Amazon Timestream for InfluxDB now publishes lifecycle events to Amazon EventBridge for instance and cluster state changes, including creation, deletion, scaling, parameter updates, maintenance, and reboots. Events cover both successes and failures and are sent to the default event bus with source aws.timestream-influxdb. This enables programmatic automation, alerting, and audit/event routing to targets like AWS Lambda, Step Functions, SQS, SNS, and cross-account buses.

🔔 Amazon Aurora DSQL change data capture (CDC) is now generally available, enabling real-time streaming of database changes to Amazon Kinesis Data Streams for event-driven architectures and data integration workflows. Aurora DSQL CDC captures insert, update, and delete operations as change events and delivers them to Kinesis Data Streams with no infrastructure to manage. Use CDC to synchronize microservices, trigger AWS Lambda, or route changes to Amazon S3, Amazon Redshift, and Amazon OpenSearch Service via Amazon Data Firehose. CDC streaming is available in all Regions where Aurora DSQL is offered and is designed to have zero impact on database workload performance.

🔒 Amazon GameLift Streams introduces Stream Session Admin Shell, a secure terminal connection for live stream sessions that enables real-time troubleshooting. You can inspect logs, query processes, check GPU utilization, and examine application state without managing SSH keys, open ports, or infrastructure credentials. The feature uses the CreateStreamSessionAdminShell API and the SSM Session Manager plugin, supports Linux, Proton, and Windows Server 2022 runtimes, and automatically closes when the session ends. It is available at no additional cost in all supported AWS Regions.

🔒 This post explains how to use two enhancements to the AWS Workload Credentials Provider: role chaining for cross-account secret retrieval and prefetching to reduce cold-start latency. It covers configuration, required IAM permissions, SSRF token usage, and how to build and deploy the Rust-based provider across EC2, ECS, EKS, and Lambda. Examples show curl and Python calls, TOML configuration for max roles, and prefetch settings for individual secrets or tag-based discovery.

🧬 AWS HealthOmics now supports Nextflow profiles, letting users activate predefined execution settings at run time. This allows separation of platform-specific configuration from core workflow logic and enables switching between development and production settings without editing workflow source code. The feature reduces errors, improves portability, and supports nf-core built-in and institutional profiles. It is available in all AWS HealthOmics Regions listed.