Build Function Compute service and function configurations with triggers, VPC access, and concurrency settings.
Last verified: May 2026
Build Function Compute service and function configurations with triggers, VPC access, logging, and concurrency settings.
Required Fields
serviceNamefunctionsOutput will appear here...The builder collects service name, description, role for execution, log project/store, VPC config, and a list of functions. Each function has handler, runtime, memory, timeout, environment variables, and triggers (HTTP, OSS, OTS, MNS, timer, log). The builder validates runtime against currently-supported FC runtimes and emits Terraform resources with proper dependencies.
Alibaba Cloud Function Compute (FC) is the serverless runtime — services contain functions, functions have triggers (HTTP, OSS events, scheduled, message queue), and configurable runtime, memory, and concurrency. The Function Compute Config Builder produces complete service and function specs including VPC access, environment variables, and concurrency settings. Output is Terraform-ready and matches `alicloud_fc_service` and `alicloud_fc_function`.
Your team has been running webhook receivers on ECS instances with nginx — total cost meaningful, plus the operational overhead of TLS certs and OS patching. You move each webhook to a Function Compute HTTP-triggered function with the builder. Total infrastructure cost drops by 80% and the operational surface area collapses to 'are the functions running'. The ECS instances are decommissioned.
Right-size memory based on profiling, not guessing. Setting too little memory makes functions run longer (and CPU is throttled), often costing more than picking a sensible memory allocation upfront.
Use provisioned concurrency for latency-critical endpoints. The cost of keeping a few instances warm is small compared to the user-experience cost of cold-start spikes on a customer-facing API.
You pay per invocation and per GB-second of execution. A 512 MB function running 1 second costs roughly the same as a 1024 MB function running 0.5 seconds — total resource-time is what matters. Memory also determines CPU allocation, so higher memory often runs faster (and not always more expensively, depending on the workload).
Yes — function instances are created on demand and torn down after idle periods. Cold starts are typically under a second for small functions, longer for functions with large dependencies or VPC-attached. For latency-sensitive endpoints, configure provisioned concurrency to keep instances warm.
Was this tool helpful?
Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.