Aws lambda expands support for high memory and vCPU configurations

AWS Lambda has expanded its capabilities by supporting up to 32 GB of memory and 16 vCPUs for functions executed on Lambda Managed Instances. This enhancement allows customers to efficiently handle compute-intensive tasks such as large-scale data processing, media transcoding, and scientific simulations without the need to manage infrastructure. Customers can now adjust the memory-to-vCPU ratio to 2:1, 4:1, or 8:1, providing flexibility to align resources with the specific needs of their workloads.

Lambda Managed Instances enable the execution of Lambda functions on managed Amazon EC2 instances, which come equipped with built-in routing, load balancing, and auto-scaling. This setup provides access to specialized compute configurations, including the latest-generation processors and high-bandwidth networking, all without operational overhead.

Developers building applications that require substantial memory and CPU resources, such as data processing pipelines, high-throughput API backends, and batch computation workloads, can now benefit from this increased capacity. These applications often need to process large datasets, deliver low-latency responses at scale, and perform complex computations efficiently. Previously, AWS Lambda function environments were limited to 10 GB of memory and approximately 6 vCPUs, with no option to customize the memory-to-vCPU ratio.

With the new configuration options, functions on Lambda Managed Instances can be tailored with up to 32 GB of memory and a choice of memory-to-vCPU ratios — 2:1, 4:1, or 8:1. This allows customers to select the optimal balance of memory and compute power for their specific workloads. For instance, with 32 GB of memory, customers can choose between configurations of 16 vCPUs (2:1), 8 vCPUs (4:1), or 4 vCPUs (8:1), depending on whether their workload is more CPU-intensive or memory-intensive.

This feature is now available in all AWS Regions where Lambda Managed Instances are generally available. Customers can configure these settings using various AWS tools, including the AWS Console, AWS CLI, AWS CloudFormation, AWS CDK, or AWS SAM. For further information, interested parties are encouraged to visit the AWS Lambda Managed Instances product page and documentation.