Yandex.Cloud
  • Services
  • Why Yandex.Cloud
  • Pricing
  • Documentation
  • Contact us
Get started
Yandex Cloud Functions
  • Getting started
    • Overview
    • Creating and executing functions
    • Creating a timer
    • Creating a trigger for Message Queue
    • Creating a trigger for Object Storage
    • Creating a trigger for Container Registry
    • Creating a trigger for Cloud Logs
    • Creating a trigger for IoT Core
  • Step-by-step instructions
    • All instructions
    • Using functions to get an IAM token for a service account
    • Managing rights to access functions
    • Managing functions
      • Creating a function
      • Managing function versions
      • Working in the code editor
      • Invoking a function
      • Updating a function
      • Viewing monitoring charts
      • Viewing the execution log
      • Deleting a function
    • Managing triggers
      • Getting information about a trigger
      • Creating a timer
      • Creating a trigger for Message Queue
      • Creating a trigger for Object Storage
      • Creating a trigger for Container Registry
      • Creating a trigger for Cloud Logs
      • Creating a trigger for Yandex IoT Core
      • Updating a trigger
      • Deleting a trigger
  • Concepts
    • Overview
    • Function
    • Invoking a function
    • Runtime
      • Overview
      • Environment
      • Execution context
    • Builder
    • Trigger
      • Overview
      • Timer
      • Trigger for Message Queue
      • Trigger for Object Storage
      • Trigger for Container Registry
      • Trigger for Cloud Logs
      • Trigger for Yandex IoT Core
    • Log groups
    • Monitoring
    • Backups
    • Quotas and limits
  • Developing in Node.js
    • Overview
    • Managing dependencies
    • Request handler
    • Invocation context
    • Logging
    • Handling errors
    • Using the SDK
  • Developing in Python
    • Overview
    • Managing dependencies
    • Request handler
    • Invocation context
    • Logging
    • Handling errors
    • Using the SDK
  • Developing in Go
    • Overview
    • Managing dependencies
    • Request handler
    • Invocation context
    • Logging
    • Handling errors
    • Using the SDK
  • Developing in PHP
    • Overview
    • Managing dependencies
    • Request handler
    • Invocation context
    • Logging
    • Handling errors
  • Developing in Bash
    • Overview
    • Request handler
    • Logging
    • Handling errors
    • Using the SDK
  • Developing in Java
    • Overview
    • Programming model
      • Overview
      • Function interface
      • YcFunction interface
      • HttpServlet class
      • Spring Boot
    • Managing dependencies
    • Request handler
    • Invocation context
    • Logging
    • Handling errors
    • Using the SDK
  • Developing in R
    • Overview
    • Programming model
    • Managing dependencies
    • Request handler
    • Invocation context
    • Logging
    • Handling errors
  • Developing in C#
    • Overview
    • Programming model
      • Overview
      • Function interface
      • YcFunction interface
    • Managing dependencies
    • Request handler
    • Invocation context
    • Logging
    • Handling errors
    • Using the SDK
  • Use cases
    • Creating skills for Alice
  • Pricing policy
  • Access management
  • API Functions reference
    • Authentication in the API
    • gRPC
      • Overview
      • FunctionService
      • OperationService
    • REST
      • Overview
      • Function
        • Overview
        • create
        • createVersion
        • delete
        • get
        • getVersion
        • getVersionByTag
        • list
        • listAccessBindings
        • listOperations
        • listRuntimes
        • listTagHistory
        • listVersions
        • removeTag
        • setAccessBindings
        • setTag
        • update
        • updateAccessBindings
  • API Triggers reference
    • Authentication in the API
    • gRPC
      • Overview
      • TriggerService
      • OperationService
    • REST
      • Overview
      • Trigger
        • Overview
        • create
        • delete
        • get
        • list
        • listOperations
        • pause
        • resume
        • update
  • Questions and answers
  1. Step-by-step instructions
  2. Managing functions
  3. Creating a function

Creating a function

    Management console
    CLI
    Terraform
    1. In the management console, select the folder to create your function in.

    2. Click Create resource.

    3. Choose Function.

    4. Enter a function name.

      • The name must be unique within the folder.
      • The name may contain lowercase Latin letters, numbers, and hyphens.
      • The first character must be a letter. The last character can't be a hyphen.
      • The maximum length of the name is 63 characters.
    5. Click Create.

    If you don't have the Yandex.Cloud command line interface yet, install and initialize it.

    The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name or --folder-id parameter.

    Create a function:

    $ yc serverless function create --name=<function name>
    

    Result:

    id: b09bhaokchn9pnbrlseb
    folder_id: aoek49ghmknnpj1ll45e
    created_at: "2019-06-14T10:03:37.475Z"
    name: my-python-function
    log_group_id: eolm8aoq9vcppsieej6h
    http_invoke_url: https://functions.yandexcloud.net/b09bhaokchn9pnbrlseb
    status: ACTIVE
    

    With Terraform, you can quickly create a cloud infrastructure in Yandex.Cloud. The infrastructure components are identified through configuration files that specify the required cloud resources and their parameters.

    If you don't have Terraform yet, install it and configure the Yandex.Cloud provider.

    To create a function:

    1. In the configuration file, describe the parameters of resources that you want to create:

      • yandex_function: Description of the function being created and its source code.
        • name: Function name.
        • folder_id: ID of the folder.
        • description: Text description of the function.
        • labels: Function labels in key:value format.
        • user_hash: An arbitrary string that identifies the function version. When the function changes, update this string, too. The function will update when this string is updated.
        • runtime: Function runtime environment. For a full list of runtimes, see Runtime environments.
        • entrypoint: Function name in the source code that will serve as an entry point to the applications.
        • memory: The amount of memory allocated for function execution, in MB.
        • execution_timeout: Function execution timeout.
        • service_account_id: ID of the service account that should be used to invoke the function.
        • environment: Environment variables in key:value format.
        • tags: Function tags.
        • version: Function version.
        • image_size: Size of the image for the function.
        • loggroup_id: ID of the log group for the function.
        • package: Package with the source code of the function version. You can only use either the package or content field.
        • package.0.sha_256: SHA256 hash of the deployed package.
        • package.0.bucket_name: Name of the bucket in Object Storage that stores the source code of the function version.
        • package.0.object_name: Name of the object in Object Storage that contains the source code of the function version.
        • content: Function source code. You can only use either the content or package field.
        • content.0.zip_filename: Name of the ZIP archive that contains the function source code.

      Example configuration file structure:

      provider "yandex" {
      token = "<OAuth or static key of service account>"
      folder_id = "<folder ID>"
          zone      = "ru-central1-a"
        }
      
      resource "yandex_function" "test-function" {
        name               = "test-function"
        description        = "Test function"
        user_hash          = "first-function"
        runtime            = "python37"
        entrypoint         = "main"
        memory             = "128"
        execution_timeout  = "10"
      service_account_id = "<service account ID>"
        tags               = ["my_tag"]
        content {
          zip_filename = "<path to ZIP archive>"
        }
      }
      
      output "yandex_function_test-function" {
        value = "${yandex_function.test-function.id}"
      }
      

      For more information about the resources you can create using Terraform, see the provider documentation.

    2. Make sure that the configuration files are correct.

      1. In the command line, go to the directory where you created the configuration file.

      2. Run the check using the command:

        $ terraform plan
        

      If the configuration is described correctly, the terminal displays a list of created resources and their parameters.If there are errors in the configuration, Terraform points them out.

    3. Deploy the cloud resources.

      1. If the configuration doesn't contain any errors, run the command:

        $ terraform apply
        
      2. Confirm that you want to create the resources.

      Afterwards, all the necessary resources are created in the specified folder. You can check resource availability and their settings in management console.

    Language
    Careers
    Privacy policy
    Terms of use
    © 2021 Yandex.Cloud LLC