About buckets and objects
The Object Store server consists of a collection of objects. The container of an object is known as a bucket. In Access Appliance Object Store, the buckets are stored on file systems as directories and objects are stored as files.
Buckets and objects are resources which can be managed using the APIs.
Once the Object Store Server is configured, you can create buckets and objects and perform the required operations.
Note:
It is recommended to have only one bucket per file system.
Access Appliance supports the following methods for accessing the buckets and the objects:
Path-style method
Virtual-hosted-style method
When using the virtual hosted-style method, the bucket_name.s3.cluster_name should be DNS resolvable. The bucket name is part of the endpoint URL (bucket_name.<endpoint_name>). For example, bucket_name.s3.cluster_name. You can send a request to the S3 server only if this URL is DNS resolvable by the client's DNS servers. A separate entry in the DNS server is required for every bucket.
See the objectaccess_bucket(1) manual page for more information.
Note:
Access S3 does not support creation of object with and without "/" at the same time. For example, you cannot create two objects such as, bucket1/object1 and bucket1/object1/, where the latter represents a directory. The user should use separate names for directories and real objects.
Note:
Object name containing …:: substring is not supported.
See the objectaccess manual pages for all of the Access Appliance Object Store server operations that can be performed.
Buckets are created by S3 clients by calling the standard S3 APIs to the Access Appliance S3 server. For creating a bucket, you need the endpoint of the Access Appliance server, access key, and the secret key. The endpoint of the Access Appliance Object Store server is s3.cluster_name:8143.
The Access Appliance Object Store server can also be accessed using the fully qualified domain name:
s3.cluster_name.fqdn:8143
Make sure that you associate one (or more) of the VIPs of the Access Appliance cluster to s3.cluster_name.fqdn in the client's DNS server.
You can delete a bucket using the standard API or by using the objectAccess bucket delete command.
objectaccess> bucket delete bucket_name
Table: Object and bucket restrictions describes the restrictions enforced by the Access Appliance Object Storage Server. Configure your S3 clients within these limitations to ensure that Access Appliance works correctly.
Table: Object and bucket restrictions
Description | Limit |
|---|---|
Maximum recommended parallel threads | 8 |
Maximum number of buckets per file system without MAP command | 50 The maximum number of supported file systems is 50. |
Maximum number of objects per file system | 1 billion |
Maximum length for bucket names | 63 |
Maximum length for '/' separated object name segment | 255 |
Maximum supported size of an object that can be uploaded using a single PUT | 100 MB |
Maximum supported size range of an object that can be downloaded using a single GET | 8 EB |
Maximum number of parts supported for multipart upload | 10,000 |
Maximum number of objects returned per list objects request | 1,000 |
Maximum number of objects returned per list object versions request | 1,000 |
Maximum number of parts returned per list parts request | 1,0000 |
Maximum number of multipart uploads returned per list multipart uploads request | 1,0000 |
Maximum number of grantees supported for setting ACL on buckets/objects | 128 |
Maximum retention time that can be set on objects | 60 years in future or less than year 2106 whichever is less Must be between the minimum and maximum retention period of the bucket |
Supported clustering modes to create WORM/lock-enabled bucket | Compliance and Enterprise modes |
Maximum number of supported S3 data and admin endpoints | 4 |
Note:
The maximum number of buckets supported is 50 since the maximum number of supported file systems is 50. If file systems are created for some other purposes, the number of available file systems for S3 buckets gets reduced.