This topic details the 2022 release notes for Function Compute, covering new features, enhancements, and documentation updates.
November 2022
Feature | Type | Description | References |
Price reduction for all billable items in all regions | Enhancement | Effective November 3, 2022, Function Compute reduced prices for all billable items across all regions. Optimized billing rules help you flexibly allocate resources and improve utilization. This reduction applies to both pay-as-you-go and resource plan pricing. When your average daily resource utilization reaches 30%, you can expect cost savings of 12% to 47%. | |
Decoupled instance specifications | Enhancement | Instance memory and vCPU specifications are now decoupled, allowing for independent configuration. | |
Support for mounting an OSS file system to a service | New | Once configured, functions within the service can access the specified OSS file system as a local file system. | |
Adjustable GPU memory range | Enhancement | You can now adjust GPU memory in 1 GB increments, from 1 GB to 16 GB. |
September 2022
Feature | Type | Description | References |
Advanced features for EventBridge triggers | New | EventBridge triggers now support advanced features, including batch delivery, retry policies, and dead-letter queues. | |
New runtimes
| New | Function Compute added support for the following official runtimes:
| |
Auto scaling for gpu-accelerated instances | New | Function Compute now supports auto scaling for gpu-accelerated instances. You can now create policies to automatically scale provisioned instances based on the utilization of Streaming Multiprocessors (SMs), GPU memory, hardware encoders, and hardware decoders. | |
gRPC protocol support for http functions | New | HTTP functions can now be triggered by gRPC requests. In this mode, the function acts as a web server to process gRPC requests. | |
Non-web server mode | New | Custom Container runtimes now support a non-web server mode. If you do not configure a | |
Custom health check | New | If you select Use Custom Runtime or Use Container Image when you create a function and use your own container image as the function runtime environment, your custom runtime environment may be unstable, which may cause exceptions for function instances. Function Compute supports periodic health checks for function instances to avoid request failures caused by instance exceptions. | |
GPU-accelerated instances GA | Update | GPU-accelerated instances are now generally available (GA) and are no longer in public preview. Standard charges apply. |
August 2022
Feature | Type | Description | References |
Official public layers | New | Function Compute now provides official public layers, which you can use in your functions without needing to build and configure them yourself. | |
Rule-based canary release for http functions | New | Function Compute now supports rule-based canary releases for http functions. Requests that match specified rules are routed to the canary version. | |
New functions run as root user by default | Enhancement | Newly created functions in Function Compute now run as the root user by default. Existing functions continue to run as a non-root user with a user ID of 10000 or greater. | None |
Removed file write restrictions for new functions | Enhancement | Newly created functions in Function Compute can now write to any directory. The previous restriction of writing only to the /tmp directory has been removed. | None |
July 2022
Feature | Type | Description | References |
Expanded header support for http functions | Enhancement | The following request and response headers for http functions are now supported:
| |
System environment variables | New | You can now use the following system environment variables when configuring your function:
|
June 2022
Feature | Type | Description | References |
EventBridge trigger API | Update | The API for managing EventBridge triggers is now available. | |
Custom CORS request handling for http functions | Enhancement | By default, Function Compute allows cross-origin requests to invoke http functions. You can now implement custom logic in your function code to handle CORS requests. |
May 2022
Feature | Type | Description | References |
Enforced HTTPS redirection | New | Custom domain names support forced redirection from HTTP to HTTPS: when you enable the Force HTTPS switch, Function Compute redirects all HTTP requests for the custom domain name to HTTPS. |
April 2022
Feature | Type | Description | References |
Asynchronous invocation for http functions | New | HTTP triggers for http functions now support asynchronous invocation and asynchronous tasks. If your function includes long-running, resource-intensive, or error-prone logic, you can use asynchronous invocation to improve response times and reliability during traffic bursts. | |
WebSocket support for http functions | New | HTTP functions can now be triggered by WebSocket requests. In this mode, the function acts as a web server to process WebSocket requests. | |
Static public IP address | New | If your Function Compute function needs to access third-party services that use an IP address whitelist (such as databases or certain APIs), you can assign a static public IP address to your service. |
March 2022
Feature | Type | Description | References |
Idle billing | New | The Shallow Sleep (formerly Idle) billing feature is for function instances in provisioned mode. Function Compute allocates a CPU to each provisioned instance by default. If you enable the Shallow Sleep (formerly Idle) billing feature, CPU is allocated only to active instances, not to shallow sleep (formerly idle) instances. The unit price for a shallow sleep (formerly idle) instance is 10% of the unit price for an active instance, which significantly reduces your costs. | |
New domain for http triggers | Enhancement | The main domain for HTTP triggers has been changed to |