Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex Cloud Functions
  • Comparing with other Yandex Cloud services
    • All guides
    • Using functions to get an IAM token for a service account
    • Connecting to managed databases from functions
      • Adding environment variables
      • Specifying a cloud network
      • Transferring Yandex Lockbox secrets
      • Allocating memory for the /tmp directory
        • Mounting a bucket
        • Mounting an ephemeral disk
      • Viewing monitoring charts
      • Migration to the ru-central1-d availability zone
      • Deleting a function version
      • Deleting a function
    • Viewing operations with service resources
  • Tools
  • Pricing policy
  • Access management
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes
  • FAQ
  1. Step-by-step guides
  2. Managing a function
  3. Mounting external resources to a function file system
  4. Mounting a bucket

Mounting a bucket to a function

Written by
Yandex Cloud
Updated at July 29, 2025

You can mount Yandex Object Storage buckets to a function. Mounting a bucket automatically creates a new function version.

To mount buckets to a function:

Management console
CLI
Terraform
API
  1. In the management console, select the folder containing the function.

  2. From the list of services, select Cloud Functions.

  3. Select a function.

  4. Navigate to the Editor tab.

  5. In the Parameters section, select or create a new service account with one of these roles:

    • storage.viewer to only read data from the mounted bucket.
    • storage.uploader to read and write data from/to the mounted bucket.
  6. Expand Additional settings.

  7. Under Mounted buckets:

    1. Click Add bucket.

    2. Specify the following in the field:

      • Mount point: Name of the mount point. Use this path to access the directory the bucket will be mounted to: /function/storage/<mount_point>.
      • Bucket: Bucket you want to mount. If necessary, create a new bucket.
      • Directory: Bucket directory that will be mounted to the container. Leave this field empty to mount the entire bucket.
    3. Enable Read-only to disable writing to the bucket. With this option on, data from the mounted bucket will be read-only.

    To mount an additional bucket to the function, click Add bucket again and configure the parameters as needed.

  8. Click Save changes.

If you do not have the Yandex Cloud CLI installed yet, install and initialize it.

By default, the CLI uses the folder specified when creating the profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also set a different folder for any specific command using the --folder-name or --folder-id parameter.

Run this command:

yc serverless function version create \
  --function-name=<function_name> \
  --runtime <runtime_environment> \
  --entrypoint <entry_point> \
  --memory <RAM_size> \
  --execution-timeout <execution_timeout> \
  --source-path <path_to_ZIP_archive> \
  --service-account-id <service_account_ID> \
  --mount type=object-storage,mount-point=<mount_point>,bucket=<bucket_name>,prefix=<directory_name>,mode=<mount_mode>

Where:

  • --function-name: Function name.

  • --runtime: Function runtime environment.

  • --entrypoint: Entry point in the following format: <file_name_without_extension>.<listener_name>, e.g., index.handler.

  • --memory: Amount of RAM.

  • --execution-timeout: Maximum running time of the function until timeout.

  • --source-path: Path to the ZIP archive containing the function code and relevant dependencies.

  • --service-account-id: Service account ID. The service account needs the storage.viewer role to read from the bucket or the storage.uploader role to both read and write.

  • --mount: Object Storage bucket mounting parameters:

    • type: Mounted storage type. For a bucket, the value is always object-storage.
    • mount-point: Mount point. Use this path to access the directory the bucket will be mounted to: /function/storage/<mount_point>.
    • bucket: Bucket name.
    • prefix: Bucket directory that will be mounted to the function. Skip this field or leave it empty to mount the entire bucket.
    • mode: Bucket mount mode, ro (read-only) or rw (read and write).

    To mount several buckets to a function at the same time, set the --mount parameter as many times as you need.

With Terraform, you can quickly create a cloud infrastructure in Yandex Cloud and manage it using configuration files. These files store the infrastructure description written in HashiCorp Configuration Language (HCL). If you change the configuration files, Terraform automatically detects which part of your configuration is already deployed, and what should be added or removed.

Terraform is distributed under the Business Source License. The Yandex Cloud provider for Terraform is distributed under the MPL-2.0 license.

For more information about the provider resources, see the relevant documentation on the Terraform website or its mirror.

If you do not have Terraform yet, install it and configure the Yandex Cloud provider.

  1. Open the Terraform configuration file and add the mounts section to the function description:

    resource "yandex_function" "bucketfunction" {
      ...
    
      mounts {
        name = "<mount_point>"
        mode = "<mount_mode>"
        object_storage {
          bucket = "<bucket_name>"
          prefix = "<directory_name>"
        }
      }
    
    }
    

    Where:

    • mounts: Object Storage bucket mounting parameters:

      • name: Mount point. Use this path to access the directory the bucket will be mounted to: /function/storage/<mount_point>.
      • mode: Bucket mount mode, ro (read-only) or rw (read and write).
      • object_storage: Bucket parameters:
        • bucket: Bucket name.
        • prefix: Bucket folder that will be mounted to the container. Leave this field empty to mount the entire bucket.

      To mount several buckets to a function at the same time, set the mounts section as many times as you need.

    For more information about the yandex_function resource parameters, see this Terraform article.

  2. Apply the changes:

    1. In the terminal, go to the directory where you edited the configuration file.

    2. Make sure the configuration file is correct using this command:

      terraform validate
      

      If the configuration is correct, you will get this message:

      Success! The configuration is valid.
      
    3. Run this command:

      terraform plan
      

      You will see a detailed list of resources. No changes will be made at this step. If the configuration contains any errors, Terraform will show them.

    4. Apply the changes:

      terraform apply
      
    5. Type yes and press Enter to confirm the changes.

You can check the function version update and its settings using the management console or this CLI command:

yc serverless function version get <function_version_ID>

Use the createVersion REST API method for the Function resource or the FunctionService/CreateVersion gRPC API call.

See alsoSee also

  • Mounting external resources to a function file system
  • Mounting external resources to a container file system

Was the article helpful?

Previous
Allocating memory for the /tmp directory
Next
Mounting an ephemeral disk
© 2025 Direct Cursus Technology L.L.C.