COS offers a variety of best practices suitable for common use cases, such as access control and permission management, performance optimization, data migration, direct data upload and backup, data security, domain name management, big data, and serverless architecture, helping you meet an array of diverse business needs. Specific best practices are outlined below:
|Access control and permission management
||Access control and permission management is one of the most practical features offered by COS. Best practices are outlined in the following documents:
Granting Sub-accounts Access to COS
Guidelines on COS API Authorization Policies
Temporary Key Security Guide for Frontend Direct Upload to COS
Generating and Using Temporary Keys
Granting Sub-Accounts Permission to Pull Tag List
Granting Sub-account Under One Root Account Permission to Manipulate Buckets Under Another Root Account
||COS supports performance expansion to achieve a higher request rate. For more information, please see Request Rate and Performance Optimization.
The following document describes how to dynamically adjust the part size of a multipart upload to improve the upload success rate fore mobile devices with poor network connection. For more information, please see Resuming Multipart Upload in Weak Network Environment
||Best practices and applicable solutions for data migration are outlined in the following five migration scenarios.
Migrating Local Data to COS
Migrating Data in Non-Tencent Cloud Storage to COS
Migrating URL-based Data to COS
Data Migration within COS
Migrating Data Between HDFS and COS
|Accessing COS using the AWS S3 SDK
||COS provides APIs compatible with AWS S3. The document linked above describes how to access files in COS using the AWS S3 SDK through simple configuration modifications
|Disaster recovery and backup
||Best practices and applicable solutions for for disaster recovery and backup are outlined in the following three scenarios.High-Availability Disaster Recovery Architecture Based on Cross-Region Replication
Cloud Data Backup
Local Data Backup
|Domain name management
||The following describes how to configure a custom domain name for HTTPS access to COS. For more information, please see Configuring Custom Domain Names to Support HTTPS Access
The following describes how to configure a cross-origin access rule in COS. For more information, please see Setting Cross-Origin Access
The following describes how to host a static website in COS. For more information, please see Hosting Static Website.
||Best practices for direct upload are outlined in the following 3 scenarios:
Direct Upload for Web
Uploading Directly Through a WeChat Mini Program
Direct Upload for Mobile Apps
||The following describes how to configure hotlink protection in COS to manage access sources. For more information, please see Hotlink Protection.
||The following describes how to ensure the integrity of data uploaded to COS through MD5 verification. For more information, please see MD5 Verification.
The following introduces how to perform data verification using CRC64 check codes. For more information, please see CRC64 check.
||The following describes how to use COS as Deep storage for Druid. For more information, see Using COS as Deep Storage of Druid.
Best practices regarding using Terraform to manage COS are also offered.
|Using COS in Third-Party Apps
||The following describes how to use general COS settings to store data from S3-compatible third-party Apps in COS. For more information, see Using General COS Settings in S3-Compatible Third-Party Apps.
Best practices regarding storing forum attachments in COS using the remote attachment feature are also offered.
The following describes how to store multimedia content in COS using the WordPress plugin. For more information, see Storing Multimedia Content in WordPress to COS.