Yandex Cloud
  • Services
  • Solutions
  • Why Yandex Cloud
  • Blog
  • Pricing
  • Documentation
  • Contact us
Get started
Language / Region
Yandex project
© 2023 Yandex.Cloud LLC
Yandex Object Storage
  • Getting started
  • Step-by-step instructions
    • All instructions
    • Buckets
      • Creating a bucket
      • Deleting a bucket
      • Limiting the maximum size of a bucket
      • Allowing public access to a bucket
      • Bucket encryption
      • Managing object lifecycles
      • Managing CORS configurations
      • Access policy management
      • Managing bucket versioning
      • Editing the ACL of a bucket
      • Enabling logging
      • Object lock management
    • Objects
      • Uploading an object
      • Getting information about an object
      • Downloading an object
      • Restoring an object's version
      • Getting a public link to an object
      • Configuring an object lock
      • Deleting an object
      • Deleting all objects
      • Deleting a partially uploaded object
      • Editing an object ACL
    • Static website hosting
      • Hosting setup
      • Support for your own domain
      • Support for multiple domain names
      • Configuring HTTPS
  • Tutorials
    • Getting object query statistics with S3 Select
    • Getting website traffic statistics with S3 Select
    • Generating a billing report with resource break-down using S3 Select
    • Server-side encryption
    • Integrating an L7 load balancer with the CDN and Object Storage
    • Blue-green and canary deployment of service versions
    • Analyzing logs in DataLens
    • Using initialization scripts to configure GeeseFS in Yandex Data Proc
    • Mounting a bucket as a disk on Windows
    • Migrating data from Yandex Data Streams using Yandex Data Transfer
  • Concepts
    • Overview
    • Bucket
    • Objects
    • Bucket versioning
    • Object locks
    • Encryption
    • Object lifecycles
    • CORS
    • Static website hosting
    • Pre-signed URLs
    • Multipart upload
    • Access control lists (ACLs)
    • Bucket Policy
    • Uploading files via an HTML form
    • Storage class
    • Logging actions with a bucket
    • Backups
    • TLS protocol
    • S3 Select query language
    • Quotas and limits
  • Tools
    • All tools
    • Console clients
      • AWS CLI
      • S3cmd
    • File browsers
      • CyberDuck
      • WinSCP
    • SDK
      • AWS SDK for Java
      • Python SDK (boto)
      • AWS SDK for .NET
      • AWS SDK for C++
      • AWS SDK for PHP
      • AWS SDK for Go
    • FUSE
      • GeeseFS
      • s3fs
      • goofys
    • FTP
      • Docker container for (S)FTP(S)
  • API reference
    • REST (Amazon S3-compatible)
      • How to use the API
      • Signing requests
      • REST
        • All services and methods
        • Bucket
          • All methods
          • create
          • getBucketEncryption
          • getMeta
          • listObjects
          • listBuckets
          • deleteBucket
          • deleteBucketEncryption
          • putBucketEncryption
          • putBucketVersioning
          • getBucketVersioning
          • putBucketLogging
          • getBucketLogging
          • listObjectVersions
          • putObjectLockConfiguration
          • getObjectLockConfiguration
        • Object
          • All methods
          • upload
          • get
          • copy
          • getObjectMeta
          • delete
          • deleteMultipleObjects
          • options
          • selectObjectContent
          • putObjectRetention
          • putObjectLegalHold
          • getObjectRetention
          • getObjectLegalHold
        • Multipart upload
          • General multipart upload procedure
          • startUpload
          • uploadPart
          • copyPart
          • listParts
          • abortUpload
          • completeUpload
          • listUploads
        • Static Website Hosting
          • All methods
          • upload
          • get
          • delete
          • Static website response codes
        • CORS
          • All methods
          • XML structure of CORS configuration
          • upload
          • get
          • delete
        • Lifecycles
          • All methods
          • XML structure of lifecycle configuration
          • upload
          • get
          • delete
        • ACL
          • All methods
          • XML structure of ACL configuration
          • objectGetAcl
          • objectPutAcl
          • bucketGetAcl
          • bucketPutAcl
        • Bucket Policy
          • All methods
          • GetBucketPolicy
          • PutBucketPolicy
          • DeleteBucketPolicy
          • Data schema
          • Actions
          • Conditions
        • Common request headers
        • Common response headers
        • Responses
    • gRPC and REST
      • Authentication in the API
      • gRPC
        • Overview
        • BucketService
        • OperationService
      • REST
        • Overview
        • Bucket
          • Overview
          • create
          • delete
          • deleteHTTPSConfig
          • get
          • getHTTPSConfig
          • getStats
          • list
          • setHTTPSConfig
          • update
  • Access management
  • Pricing policy
    • Current pricing policy
    • Archive
      • Before January 1, 2019
      • From January 1 to March 1, 2019
  • Questions and answers
  1. Concepts
  2. Bucket

Bucket in Object Storage

Written by
Yandex Cloud
  • Naming buckets
  • Bucket URL
  • Accessing a bucket via HTTPS
  • Bucket settings
  • Bucket access
  • Guidelines and limitations

A logical entity that helps store objects.

Naming buckets

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

Naming rules:

  • Bucket names are unique throughout Object Storage, so you can't create two buckets with the same name (even in different folders in different clouds). Keep this in mind if you plan to create buckets automatically via the API.

  • Bucket names are subject to the following restrictions:

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

When selecting a bucket name, please keep in mind that names containing dots are used for hosting static websites. You may encounter a name conflict that prevents you or another user from hosting a website in Object Storage.

Bucket URL

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

  • https://storage.yandexcloud.net/<bucket>?<parameters>
  • http://<bucket>.storage.yandexcloud.net?<parameters>

Note

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

Accessing a bucket via HTTPS

Object Storage supports secure connections over HTTPS. When accessing your buckets, use URLs in the format https://storage.yandexcloud.net/<bucket>?<parameters>.

When you use URLs in the format http://<bucket>.storage.yandexcloud.net?<parameters> HTTPS isn't available.

Read about HTTPS support when hosting websites in Object Storage under Static website hosting.

Bucket settings

You can:

  • Limit the maximum size of a bucket.

    Object Storage doesn't let you upload objects if adding them exceeds the maximum bucket size.

  • Set the default storage class.

    Objects uploaded to a bucket are by default saved with the storage class specified for that bucket.

  • Configure a bucket for static website hosting.

  • Uploading the CORS configuration for the bucket.

  • Enable bucket encryption.

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

  • Set up object lifecycles.

Bucket access

By default, buckets are created with restricted access, as set in the IAM. You can use the management console to enable public access:

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

Public access to each operation is issued separately. In other words, if you have opened read-only access to your objects, anonymous users can't get the list of objects and bucket settings.

If necessary, you can configure permissions to the buckets and objects they contain using the ACL.

Guidelines and limitations

  • A bucket can't be renamed.

  • Object Storage performance doesn't depend on the number of buckets. You can store all your data in one or several buckets.

  • Buckets can't be nested.

  • You can only delete an empty bucket.

  • It may take some time after deleting a bucket before you can create a new bucket with the same name. There is also a risk that another Yandex Cloud user might create a bucket with the name you've released before you claim it again. Don't delete buckets without a reason.

  • When objects are uploaded in quick succession, the maximum specified bucket size can be exceeded.

  • After deleting objects from a bucket, their storage capacity is considered occupied for some time.

    Note

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

Was the article helpful?

Language / Region
Yandex project
© 2023 Yandex.Cloud LLC
In this article:
  • Naming buckets
  • Bucket URL
  • Accessing a bucket via HTTPS
  • Bucket settings
  • Bucket access
  • Guidelines and limitations