Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI Studio
    • 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
    • Education and Science
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Yandex Object Storage
    • Overview
    • Bucket
    • Object
    • Bucket versioning
    • Object lock
    • Partial object updates
    • Encryption
    • Object lifecycles
    • CORS
    • Hosting static websites
    • Pre-signed URLs
    • Multipart upload
    • Access control list (ACL)
    • Bucket policy
    • Uploading files via an HTML form
    • Storage class
    • Bucket actions logging mechanism
    • Backups
    • TLS protocol
    • Labels
    • S3 Select query language
    • Quotas and limits
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Bucket logs
  • Release notes
  • FAQ

In this article:

  • Naming buckets
  • Bucket URL
  • Accessing a bucket via HTTPS
  • Bucket settings
  • Accessing buckets from Yandex Virtual Private Cloud cloud networks
  • Public access to buckets
  • Statistics
  • Recommendations and limitations
  • Use cases
  • See also
  1. Concepts
  2. Bucket

Bucket in Object Storage

Written by
Yandex Cloud
Updated at August 4, 2025
  • Naming buckets
  • Bucket URL
  • Accessing a bucket via HTTPS
  • Bucket settings
  • Accessing buckets from Yandex Virtual Private Cloud cloud networks
  • Public access to buckets
  • Statistics
  • Recommendations and limitations
  • Use cases
    • See also

A bucket is an Object Storage storage unit allocated for user data. Each Yandex Cloud bucket has a unique name used in requests to Object Storage.

Buckets store data as objects. To organize data, you can create multiple buckets or use folders (prefixes) within a single bucket.

You can also use buckets to host static websites.

For more information on getting started with buckets, see Getting started with Yandex Object Storage.

You can create a bucket via the management console, CLI, Terraform, API, or using popular tools designed to work with the Amazon S3 HTTP API.

Naming bucketsNaming buckets

A bucket name is used as part of the data access URL and is visible to your users, e.g., https://storage.yandexcloud.net/bucket-name.

The naming requirements are as follows:

  • Bucket names are unique throughout Object Storage, i.e., you cannot create two buckets with the same name, even in different folders of different clouds. Keep this in mind if you are going to create buckets automatically through the API.

  • Bucket names are subject to the following restrictions:

    • The name must be from 3 to 63 characters long.
    • The name may contain lowercase Latin letters, numbers, hyphens, and periods.
    • The first and last characters must be letters or numbers.
    • The characters to the right and left of the period must be letters or numbers.
    • The name must not look like an IP address, e.g., 10.1.3.9.

When choosing a name for your bucket, keep in mind that names containing dots are used for static website hosting. You may encounter a name conflict that will prevent you or another user from hosting a website in Object Storage.

Bucket URLBucket URL

You can use the following URL formats to access a bucket:

  • http(s)://storage.yandexcloud.net/<bucket_name>?<parameters>
  • http(s)://<bucket_name>.storage.yandexcloud.net?<parameters>

Note

If you use the AWS SDK for .NET, access the s3.yandexcloud.net host.

Accessing a bucket via HTTPSAccessing a bucket via HTTPS

Object Storage supports secure connections over HTTPS.

Note

If you use such URLs as http(s)://<bucket_name>.storage.yandexcloud.net, the HTTPS protocol is available for the bucket only if the bucket name does not contain dots, e.g.:

  • https://example.storage.yandexcloud.net: HTTPS is available for this bucket.
  • http://example.ru.storage.yandexcloud.net: HTTPS is not available for this bucket.

This is because Object Storage uses Wildcard certificates that only support one level of subdomains.

To provide HTTPS support for a bucket with a dot in the name, upload your own security certificate to Object Storage.

For more information on HTTPS support when hosting websites in Object Storage, see Hosting static websites.

Alert

As of August 1, 2025, Object Storage no longer supports the TLS protocol versions 1.0 and 1.1.

For more information, see TLS protocol.

Bucket settingsBucket settings

You can:

  • Limit the maximum bucket size.

    Object Storage will not allow you to upload an object if doing so leads to exceeding the maximum bucket size.

  • Set the default storage class.

    By default, objects uploaded to a bucket are saved with the storage class specified for that bucket.

  • Configure a bucket for static website hosting.

  • Upload a CORS configuration for a bucket.

  • Enable bucket encryption.

    By default, objects added to the bucket are encrypted with the specified KMS key.

  • Set up object lifecycles.

Accessing buckets from Yandex Virtual Private Cloud cloud networksAccessing buckets from Yandex Virtual Private Cloud cloud networks

Warning

The VPC Private Endpoints feature is at the Preview stage. To request access to the feature, contact your account manager.

To make Object Storage buckets accessible from VPC cloud networks directly, use a VPC service connection. With this connection, you can access Object Storage via VPC internal IP addresses without any Internet access.

For more information on configuring access, see Accessing a bucket using a service connection from Yandex Virtual Private Cloud.

Public access to bucketsPublic access to buckets

Object Storage incorporates several access management mechanisms. To learn how these mechanisms interact, see Access management methods in Object Storage: Overview.

By default, bucket access is restricted, as specified in the IAM settings. You can enable public access:

  • To read objects in a bucket.
  • To view the list of objects in a bucket.
  • To read settings:
    • CORS
    • Static website hosting
    • Object lifecycles

Public access to each operation is granted separately. This means, if you have granted only read access to your objects, anonymous users cannot get the list of objects and bucket settings.

Warning

Public access is granted to an unlimited number of anonymous users. Use it only when other access grant mechanisms are not available.

If required, you can configure permissions to the buckets and objects they contain using ACLs or the access policy.

StatisticsStatistics

Object Storage automatically delivers bucket performance metrics to Yandex Monitoring.

Performance statistics are available on the bucket page or in the Monitoring interface.

For the list of metrics delivered to Monitoring, see the reference.

You can also access aggregate bucket statistics through the Yandex Cloud CLI.

Recommendations and limitationsRecommendations and limitations

  • Updating bucket statistics may take up to 20 minutes. Therefore, sometimes the specified maximum bucket size may be exceeded (e.g., during fast sequential upload of multiple objects).

  • In the management console, the information about the number of objects in the bucket and used up space is updated with a delay.

  • You cannot rename buckets.

  • The number of buckets does not affect the performance of Object Storage. How many buckets you use to store your data is up to you.

  • Buckets cannot be nested.

  • You can only delete an empty bucket.

  • After you delete objects from a bucket, the vacated space is not considered free for a while longer.

  • After deleting a bucket, you may not be able to create a new one with the same name right away. There is also a risk that another Yandex Cloud user may create a bucket with this name before you claim it again. Do not delete buckets without a good reason.

    Note

    If you limit the maximum size of a bucket, it may remain temporarily unavailable for writes even after you free up enough space for new objects.

Use casesUse cases

  • Mounting Object Storage buckets to the file system of Yandex Data Processing hosts
  • Connecting a bucket as a disk in Windows
  • Automatically copying objects from one Object Storage bucket to another
  • Regular asynchronous recognition of audio files in Object Storage buckets
  • Creating an external table from a bucket table using a configuration file

See alsoSee also

  • Access management methods in Object Storage: Overview

Was the article helpful?

Previous
Overview
Next
Object
© 2025 Direct Cursus Technology L.L.C.