Cloud Functions prerequisites

Available in Classic and VPC

Review supported environments, pricing plans, and service limits before using Cloud Functions.

Cloud specifications

Cloud Functions supports the following cloud environment specifications:

Item	Specification
Region (zone)	Korea (KR-1, KR-2), Singapore (SGN-4, SGN-5), Japan (JPN-4, JPN-5)
Platform	VPC, Classic
Language	Korean, English, and Japanese

Note

If you are configuring VPC resource access from a VPC environment in the Korea Region, you can only connect a subnet created within the KR-2 zone. Support for subnets within the KR-1 zone is under preparation.

You can access KR-1 subnets and resources from actions connected to KR-2 zone subnets.

Runtime specifications

The languages supported by Cloud Functions and the recommended versions for use are as follows:

Caution

The specifications supported by Cloud Functions may change without notice depending on the policies of each supported language.

Supported languages

Supported languages	Latest version
Node.js	22
Python	3.13
Java	21
Swift	3.1.1
PHP	7.3
Go	1.19
.Net Core	2.2

Note

For more information on action runtime, see Cloud Functions runtime information.

Trigger type specifications by region

The following trigger types are supported by Cloud Functions for each Region:

Region	Cron type	GitHub event	API Gateway type	Cloud Insight type	Object Storage type	SourceCommit type	Secret Manager type	Resource Manager type
Korea	O	O	O	O	O	O	O	O
Singapore	O	O	O	O	O	X	X	X
Japan	O	O	O	O	O	X	O	X

Resource limitations

The following describes the limitations for Cloud Functions resources (actions, triggers, packages):

Resource count limits: You can create up to 500 actions, triggers, and packages each.
- This limit also applies to resources created in the Classic environment. We do not support increasing these resource count limits.
Timeout: Maximum time limit for which the action can be run. Forcibly finished if the timeout is exceeded.
- Unit: ms.
- Default: 60,000 (60 seconds).
- Range: 500–300,000.
- Set when you create the action.
Memory: Maximum memory assignable to an action container.
- Unit: MB.
- Default: 128.
- Range: 128–1,024.
- Set when you create the action.
Logs: Maximum stdout size that actions can create. When output exceeds this maximum size, the system discards additional logs and adds a warning to the final line.
- Unit: MB.
- Default: 1.
- Maximum size for log storage in Cloud Log Analytics service and viewable in dashboard/monitoring is 50 KB.
Concurrent: Number of actions (action containers) you can execute simultaneously per namespace at any given time.
- Unit: Count.
- Default: 1000.
- For high volumes, contact Customer Support > Contact us and request a limit increase.
CodeSize: Maximum code size.
- Unit: MB.
- Fixed value: 38.
- You cannot change this value arbitrarily.
Parameters: Maximum size of parameters you can forward to actions or triggers.
- Unit: MB.
- Fixed value: 1.
- You cannot change this value arbitrarily.
Result: Maximum size of result values that actions return upon execution.
- Unit: MB.
- Fixed value: 1.
- You cannot change this value arbitrarily.
- Maximum size for log storage in Cloud Log Analytics service and viewable in dashboard/monitoring is 150 KB.
Max open files ulimit value of action container: Maximum number of files that an action container can open.
- Fixed value: 1024:1024.
- You cannot change this value arbitrarily.
- When you execute the docker run command, the system forwards this as --ulimit nofile=1024:1024. For more information, see the Docker official documentation.
Max process ulimit value of action container: Maximum number of processes an action container can create.
- Fixed value: 1024.
- You cannot change this value arbitrarily.
- When you execute the docker run command, the system forwards this as --pids-limit 1024. For more information, see the Docker official documentation.

Note

To prevent performance degradation due to unnecessary usage of resources, the number of concurrent actions is limited for each namespace.

Parameter application priority

Cloud Functions offers various parameters for running actions or triggers. These parameters are applied based on the priority rule. Therefore, if two parameters have the same keys, the parameter with a higher priority is applied. The following describes the priority rule for parameter application:

Runtime parameter: Parameter forwarded at the time of run, including HTTP request body and query parameters called through API Gateway-type trigger.
Trigger default parameter: Parameters applied to triggers in general.
Action default parameter: Parameters applied to actions in general.
Package default parameter: Parameters applied in general to actions belonging to packages.

Caution

A field with an encrypted action default parameter is applied with the highest priority.

Source code security

Cloud Functions uses the following methods to protect the security of the code you entered:

Isolated storage: Your uploaded code is securely stored in an isolated DB.
Independent container: Once raised, your request is executed in an isolated space before the result is returned. The space itself is deleted after a certain amount of time.

Caution

For security, the space where your code was run is never shared with another user nor reused.

Pricing information

Cloud Functions is serviced on a pay-as-you-go pricing plan. For detailed pricing criteria for Cloud Functions, see the pricing information in Portal > Services > Compute > Cloud Functions.

Portal > Services > Compute > Cloud Functions