This topic describes the Alibaba Cloud services that support integration with Key Management Service (KMS). These Alibaba Cloud services can use service keys or user-managed keys, including keys based on Bring Your Own Key (BYOK), to encrypt data.
Integration with KMS allows you to protect your data stored in Alibaba Cloud services at low costs, provides security boundaries for business data, and enhances the capabilities to protect business security in Alibaba Cloud. KMS can protect not only the business data that you can directly access, but also the business data that you can only indirectly access.
|Elastic Compute Service (ECS)||
By default, the disk encryption feature of ECS uses a service key to encrypt your data. This feature also supports user-managed keys. Each disk has its own customer master key (CMK) and data key (DK) and uses the envelope encryption mechanism to encrypt your data.
An ECS instance automatically encrypts the data transmitted to an encrypted disk and decrypts data read from the disk. Data is encrypted or decrypted on the host where the ECS instance resides. During encryption and decryption, the performance of the disk is almost not affected.
After an encrypted disk is created and attached to an ECS instance, the ECS instance encrypts the following data:
|Object Storage Service (OSS)||
OSS uses the server-side encryption (SSE) feature to encrypt uploaded data.
OSS can use an encryption system dedicated to OSS to implement the SSE feature. In this case, this feature is called SSE-OSS. The keys used in this encryption system are managed by OSS. Therefore, you cannot use ActionTrail to audit the use of these keys.
OSS can also use KMS to implement the SSE feature. In this case, this feature is called SSE-KMS. OSS uses the service key or user-managed keys to encrypt your data. OSS allows you to configure a default CMK for each bucket or specify the CMK to use when you upload an object.
|ApsaraDB for RDS||ApsaraDB for RDS supports the following methods to encrypt data:
|ApsaraDB for MongoDB||The encryption method for ApsaraDB for MongoDB is similar to that for ApsaraDB for RDS.||Configure TDE for an ApsaraDB for MongoDB instance|
|PolarDB||The encryption method for PolarDB is similar to that for ApsaraDB for RDS.||Configure TDE|
|Apsara File Storage NAS||
By default, Apsara File Storage NAS uses the service key to encrypt your data. Each volume has its own CMK and DK and uses the envelope encryption mechanism to encrypt your data.
By default, the encryption feature of Tablestore uses the service key to encrypt your data. This feature also supports user-managed keys. Each table has its own CMK and DK and uses the envelope encryption mechanism to encrypt your data.
MaxCompute uses the service key as the CMK to encrypt your data.
|Cloud Storage Gateway (CSG)||
CSG supports two encryption methods:
|ApsaraVideo for Media Processing||
ApsaraVideo for Media Processing supports two encryption methods: proprietary encryption and HLS standard encryption. No matter which encryption method is used, ApsaraVideo for Media Processing can be integrated with KMS to protect video content.
|ApsaraVideo for VOD||
ApsaraVideo for VOD supports two encryption methods: Alibaba Cloud video encryption and HLS standard encryption. No matter which encryption method is used, ApsaraVideo for VOD can be integrated with KMS to protect video content.
|Web App Service||
Web App Service is integrated with KMS to encrypt sensitive configuration data, such as access credentials of ApsaraDB for RDS.
|ApsaraDB for RDS instances|
|Application Configuration Management (ACM)||
ACM is integrated with KMS to encrypt application configurations. This ensures the security of sensitive configurations, such as data sources, tokens, usernames, and passwords, and reduces the risk of configuration leakage. ACM can use KMS in either of the following ways:
|Create and use encrypted configuration|