OSS provides secure, cost-effective, and high-durability services for you to store large amounts of data in the cloud. This topic lists the common scenarios and corresponding features of OSS. You can select the best solution based on your business requirements.
Before you use OSS, we recommend that you have a good understanding of the basic terms used in OSS, including buckets, objects, regions, and endpoints. For more information, see Terms.
The following table lists the features provided by OSS.
Scenario | Description | Reference |
---|---|---|
Upload objects | Before you upload objects to OSS, you must create a bucket in an Alibaba Cloud region to store your objects. After you create a bucket, you can upload objects to the bucket. | |
Search for objects | OSS allows you to search for objects and folders and find the object you want to access in a bucket. | Search for objects |
View, share, and download objects | OSS allows you to use the signed URL of an object to view, share, and download the object. | Download objects |
Delete objects or folders | OSS allows you to delete one or more objects, folders, and parts at a time. You can delete expired objects at regular intervals to save storage space. | |
Automatically delete multiple objects at a specified point in time | OSS supports lifecycle rules. You can configure lifecycle rules to periodically convert the storage class of non-hot data to Infrequent Access (IA), Archive, or Cold Archive, and delete expired data. | Lifecycle rules |
Accelerate the upload and download of data | OSS supports transfer acceleration. Transfer acceleration uses optimal route selection and protocol stack tuning to reduce timeouts in remote transmission and improve user experience. | Transfer acceleration |
Recover accidentally deleted data | OSS supports versioning. When you enable versioning, OSS saves the overwritten and deleted objects as previous versions. Versioning allows you to recover objects in a bucket to any previous version, and prevents data loss caused by accidental deletion or overwriting of objects. | Configure versioning |
Zone-disaster recovery | OSS uses the multi-zone mechanism to distribute user data across three zones within the same region. Even if one zone becomes unavailable, the data still remains accessible. This feature can provide 99.9999999999% (twelve 9's) data durability (designed for) and 99.995% service availability. | ZRS |
Geo-disaster recovery | OSS supports cross-region replication (CRR). You can use CRR to synchronize operations performed on data such as create, update, and delete operations from the source bucket to the destination bucket in a different zone. This way, you can implement geo-disaster recovery. | Cross-region replication |
Data retention compliance | OSS supports the Write Once Read Many (WORM) strategy that prevents an object from being deleted or overwritten for a specified period of time. | Retention policy |
Control access to data | OSS supports flexible authorization and authentication mechanisms. You can control
access to OSS resources by using the following methods:
|
|
Encrypt data | OSS supports client-side and server-side encryption. You can select an encryption method to encrypt and store your data in OSS. | |
Manage data by category | OSS allows you to configure tagging to manage data based on the data category:
|
|
Record the access information for OSS resources | OSS supports logging. You can configure logging to audit operations, collect access statistics, track exceptions, and troubleshoot problems in OSS. | |
Use custom domain names to access OSS resources | OSS allows you to bind custom domain names to OSS buckets, and use custom domain names to access data in the buckets. If you want to use your custom domain name to access OSS by using HTTPS, you can host your SSL certificate in OSS. | |
Configure static website hosting | OSS supports static website hosting. You can configure static website hosting for your bucket and access static websites by using the bucket domain name. | Static website hosting |
Cross-origin resource sharing (CORS) | OSS supports CORS in HTML5. CORS allows client web applications that are loaded in one domain to interact with resources in another domain. | Configure CORS |
Obtain data from the origin | OSS supports back-to-origin configurations. If your user accesses data in a bucket that has no back-to-origin rules configured and the data does not exist, 404 Not Found is returned. However, if you configure back-to-origin rules that contain the correct origin URL, your user can obtain the data based on the back-to-origin rules. You can configure back-to-origin rules for hot data migration and specific request redirection. | Manage back-to-origin configurations |
View object metadata | OSS supports the inventory feature. You can configure inventory rules for buckets to export the metadata of specified objects including the object sizes and encryption status. | Bucket inventory |
Modify HTTP headers | OSS allows you to modify the HTTP headers of objects. You can configure HTTP headers to customize HTTP request policies such as the cache policy and forced object download policy. | Configure object HTTP headers |
View resource usage | OSS supports the monitoring feature. You can use the monitoring feature to view real-time information about OSS service usage such as the running status and performance of the system. | Overview of the monitoring service |
Traffic throttling | OSS supports single-connection bandwidth throttling. You can configure single-connection bandwidth throttling for upload, download, and copy operations on OSS to ensure sufficient bandwidth for other applications. | Single-connection bandwidth throttling |
Analyze and process data | OSS supports Image Processing (IMG) and video snapshot capturing for you to analyze
and process data stored in OSS:
|
|
Use tools to manage OSS resources | OSS provides graphical, CLI, file mounting, and FTP tools for you to manage OSS resources. | OSS tools |
Use SDKs to manage OSS resources | OSS provides SDKs for a variety of programming languages to facilitate secondary development. | SDK sample code |