COS offers a variety of best practices for common use cases, such as access control and permission management, performance optimization, data migration, direct data upload and backup, data security, endpoint management, big data, and serverless architecture, facilitating your diverse business needs. Specific best practices are outlined as follows:
|Access control and permission management
||Access control and permission management is one of the most practical features of COS. Best practices are outlined in the following documents:
Cloud Access Management Practices
Granting Sub-accounts Access to COS
Cases of Permission Setting
Working with COS API Access Policies
Temporary Key Security Guide for Frontend Direct Upload to COS
Generating and Using Temporary Keys
Granting Sub-account Permissions 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.
If the device side offers a poor network, you can adjust the part sizes dynamically for a higher upload success rate. For more information, please see Multipart Upload Resumption in a Weak Network Environment.
||Best practices are outlined for the following 5 scenarios:
Migrating Local Data to COS
Migrating Data in Non-Tencent Cloud Storage to COS
Migrating Data from URL to COS
Data Migration within COS
Migrating Data Between HDFS and COS
|Accessing COS Using the AWS S3 SDK
||COS offers APIs compatible with AWS S3. You can access files in COS using the AWS S3 SDK with simple configurations.
|Disaster recovery and backup
||Best practices are outlined for the following 3 scenarios:Disaster Recovery and High Availability Architecture Based on Cross-Bucket Replication
Cloud Data Backup
Local Data Backup
||You can configure a custom endpoint for HTTPS access to COS. For more information, please see Configuring Custom Domain Names to Support HTTPS Access.
You can configure a cross-origin access rule in COS. For more information, please see Setting Cross-Origin Access.
You can host a static website in COS. For more information, please see Hosting Static Website.
||Best practices are outlined for the following 3 scenarios:
Practice of Direct Transfer for Web End
Uploading Directly Through a WeChat Mini Program
Practice of Direct Upload for Mobile Apps
||You can configure hotlink protection in COS to monitor and control access origins. For more information, please see Hotlink Protection Practice.
||You can ensure the integrity of data uploaded to COS using MD5 checksum. For more information, please see MD5 Verification.
You can verify data using CRC-64 checksum. For more information, please see CRC64 Check.
||You can use COS as Deep storage for Druid. For more information, please see Using COS as Deep Storage of Druid.
Best practices regarding how to use Terraform to manage COS are also offered.
|Using COS in third-party apps
||You can store data of S3-compatible third-party apps to COS using COS general settings. For more information, please see Use the general configuration of COS in third-party applications compatible with S3.
You can store multimedia content in COS using the WordPress plugin. For more information, please see Storing multimedia content in WordPress to COS.
|Introduction to COS Data Security Solution
||This document describes the COS data security solution, concerning pre-event protection, during-event monitoring, and post-event tracking.