tencent cloud

TDSQL for MySQL

Announcements
Alarm Upgrade
Product Introduction
Overview
Strengths
Use Cases
Regions and AZs
InnoDB engine
Purchase Guide
Billing Overview (InnoDB)
Product Pricing (InnoDB)
Purchase and Upgrade
Refund
Payment Overdue
Backup Space Billing
Getting Started
InnoDB Engine
Operation Guide(InnoDB)
Instance Management
Disaster Recovery Read-Only Instance
Changing Networks
Account Management
Security Management
Slow Query Analysis
Backup and Rollback
Data Migration
Database Audit
Practical Tutorial
Import from Standalone Instance to TDSQL Instance
Import Between TDSQL Instances
Selection of TDSQL Instance and Shard Configuration
Security White Paper
Platform Security Design
Tenant Security Features
Development Guide
InnoDB
API Documentation
History
Introduction
API Category
Security Group APIs
Other APIs
Making API Requests
TDSQL APIs
Data Types
Error Codes
FAQs
InnoDB
General References
Performance Comparison Data for Strong Sync
Glossary
Contact Us

Backup Encryption

PDF
フォーカスモード
フォントサイズ
最終更新日: 2024-01-06 17:33:30

Feature Overview

TDSQL for MySQL offers the transparent data encryption (TDE) feature that makes data encryption and decryption transparent to users. TDE supports data file encryption and decryption in real time. It allows data files to be encrypted before being written to disk and decrypted when read into memory from disk, meeting the static data encryption compliance requirements.
TDE is only supported for Percona 5.7 in Hong Kong region, but it will be available to more kernel versions in the future. You can access Data Security > Data Encryption on the instance management page in the TDSQL console
After data encryption is enabled, the database instances can’t be restored from a backup file. It is recommended to restore them as instructed in Rolling Back Database.
Note:
To use the data encryption feature, submit a ticket to apply for it.

Notes

Currently, you can’t create disaster recovery read-only instances for the instance with KMS enabled. For more information about KMS, see Getting Started with KMS.
TDE can't be disabled once enabled.
TDE enhances the security of static data while compromising the read-write performance of encrypted databases. Therefore, use it based on your actual needs.
After TDE is enabled, more CPU resources will be consumed, and about 5% of the performance will be compromised.

ヘルプとサポート

この記事はお役に立ちましたか?

フィードバック