Skip to main content
logologo
Docs
NewsBlogContact Us
Help CenterAPI DocsBlogFAQ

Arvancloud Object Storage Policies and Restrictions

The many uses of object storage have made this service one of the most widely used cloud infrastructure services. Object Storage has reduced the costs of online businesses by providing multiple capabilities and the possibility of storing and retrieving all types of data in different volumes. Arvancloud's Object Storage reduces the traffic and load of your website's main server by integrating with CDN and content caching.

Using Arvancloud Object Storage is as simple as copying the Access Key, Secret Key, and Endpoint URL. Also, many third-party tools such as S3cmd, S3browser, Rclone, and Cyberduck are provided for various Linux, Mac, and Windows operating systems, which together with the SDK and API of this product, make it possible for you to access the service from anywhere and anytime.

In this article, we explain the limitations and policies of Arvancloud's Object Storage for a better user experience.

Service Level Policies​

  • Each bucket can only be accessed in the same data center (Region) that was created and has its own URL address.
  • The buckets are by default integrated with the CDN and you can set the duration of your data cache.
  • There is no limit to the number of requests and the amount of traffic in the Arvancloud. If you ever experience slowness, use third-party tools. If you are experiencing slowness using the SDKs, pay attention to the number of concurrent requests.
  • To use the cache feature of the CDN to receive objects, be sure to use the Virtual Host address format. Which means, in the form of {bucketname}.s3.{region}. arvanstorage.ir where the name of the region is different depending on the data center.
  • By using a custom domain, the domain cache settings are applied to the data and the bucket cache settings are ignored.
  • For more details, you can check out the Pricing Policy and Terms of Service.

Bucket Level Policies​

By default, each user can define 50 buckets in their account. If you need to increase this number, send a request to our support team. In terms of service efficiency, it doesn't matter if you have a few buckets or more.

  • There is no limit to the number of objects in each bucket, but to avoid reducing the efficiency, a limit of 3,700,000 numbers has been applied to the buckets by default. Although it is not recommended to store more than this amount in each bucket, you can increase this limit by sending a request to Arvancloud support.

  • Programs should have the ability to retry when encountering a 5xx error to avoid the problem of slow time and temporary disconnection.

  • If a bucket is empty, you can delete it. After the bucket is deleted, its name is available for reuse. However, in some situations, this name may still not be usable for some reason.

    For example, when you delete a bucket its name becomes available for reuse, and someone else may create a bucket with that name. Additionally, it may take some time before you can reuse the name of a deleted bucket. If you want to use the same name, we recommend not deleting the bucket.

  • The access policy on the bucket is private and public. Objects in a bucket do not inherit from a bucket. For example, by making the bucket private, unauthorized users cannot see the list of objects inside the bucket, and it doesn't matter if the objects are public or private; Only bucket operations are affected.

  • When you enable the static website feature for the bucket, its access address is different from the default address and is like this: s3-website.{region}.arvanstorage.ir.

  • There is no such thing as a folder in Object Storage services. If you need to group objects inside a bucket, this can be done with a prefix. A prefix is a part of an object name that is separated by /. And it is displayed in the panel in the form of folders. You can also use client tools for this.

  • When you create a bucket in a region and choose its name, it will not be possible to change them.

Rules for Naming Buckets​

  • The name of the bucket must contain 3 (minimum) to 63 (maximum) characters.
  • The bucket name must contain only lowercase letters, numbers, period (.), and hyphens (-).
  • The name of the bucket must start and end with a number or letter.
  • The name of the bucket should not have two dots next to each other.
  • The name of the bucket should not be in IP form. (like 192.168.1.1)

Examples of Allowed Names for Buckets

The following names follow the rules above and are allowed to be defined:

  • docexamplebucket1
  • log-delivery-march-2020
  • my-hosted-content

The following names are allowed but not recommended except for static websites:

The following names are not allowed:

  • doc_example_bucket (includes underline)
  • DocExampleBucket (includes capital letters)
  • doc-example-bucket- (ends with a hyphen)

Object Level Policies​

  • The request to upload each file is allowed up to 5GB.
  • Each part of the multipart upload is a maximum of 400MB.
  • The minimum size of each part of the multipart is 5MB.
  • The maximum number of parts is 10 thousand.
  • The maximum supported final volume of the object using multipart is 5TB.
  • If you have a large number of objects, it is recommended to use client tools such as s3cmd, because you may encounter slowness and limitations in the Arvancloud panel.
  • When you have a file larger than 500MB, it is recommended to use multipart so that you don't get disturbed when uploading a large file.
  • At the time of sending the object, if a multi-part is used and an incomplete file is uploaded, you must delete the incomplete parts that exist through the SDK or go to the desired bucket in the Arvancloud panel, and if the incomplete upload warning is displayed clean it. Keep in mind that during the upload and until it is complete, the system calculates the parts as incomplete and you should not delete them.