Build Functions application configurations with subnet placement and provisioned concurrency.
Last verified: May 2026
Build Functions application configurations with subnet placement, config variables, tracing, and provisioned concurrency.
Required Fields
compartmentIddisplayNamesubnetIdsconfigOutput will appear here...Build Functions application configurations with subnet placement and provisioned concurrency. This tool helps OCI engineers generate valid configurations quickly without consulting documentation, reducing errors and accelerating infrastructure deployment. All processing runs in your browser with no data sent to external servers.
Your team has 20 microservices implemented as Functions, currently each in its own application. Network changes (new NSG rule, subnet migration) require updating 20 applications individually. The builder helps consolidate: 4 applications (one per domain — payments, notifications, ingestion, admin), each with multiple functions. Network changes update 4 applications instead of 20. Operational burden drops dramatically; each domain's functions share consistent networking and IAM context.
Applications are the deployment unit for Functions — multiple individual functions group inside an application sharing networking, IAM, and image registry config. Plan your application boundaries by team or domain (e.g., `payment-functions`, `notifications-functions`) rather than per-function.
Subnet placement matters for performance and security. Place applications in private subnets with NAT Gateway egress for security — public subnets are unnecessary unless your functions need direct inbound from the internet (which is rare; use API Gateway as the entry point).
Provisioned concurrency (similar to AWS Lambda's feature) eliminates cold starts at additional cost. Use it for user-facing functions where the first-request-latency matters; skip it for async/event-driven functions where 1-2 second cold starts are acceptable.
The builder constructs OCI Functions application configurations: application resource (compartment, name, subnet OCIDs for VCN placement, image policy referencing Container Registry, optional provisioned concurrency, network security group bindings, application-level configuration variables that all member functions inherit), and individual function resources (name, image reference, memory, timeout, function-level config overrides). Output is generated as oci fn application + oci fn function commands and Terraform oci_functions_application + oci_functions_function resources.
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.