diff --git a/hardware-and-software-requirements.md b/hardware-and-software-requirements.md
index b083ac0495735..bc9c973ac50b1 100644
--- a/hardware-and-software-requirements.md
+++ b/hardware-and-software-requirements.md
@@ -55,6 +55,7 @@ You can deploy and run TiDB on the 64-bit generic hardware server platform in th
 | PD      | 4 core+   | 8 GB+  | SAS, 200 GB+ | Gigabit network card | 1 (can be deployed on the same machine with TiDB)       |
 | TiKV    | 8 core+   | 32 GB+  | SAS, 200 GB+ | Gigabit network card | 3       |
 | TiFlash | 32 core+  | 64 GB+  | SSD, 200 GB+ | Gigabit network card | 1     |
+| TiCDC | 8 core+ | 16 GB+ | SAS, 200 GB+ | Gigabit network card | 1 |
 
 > **Note:**
 >
@@ -72,6 +73,7 @@ You can deploy and run TiDB on the 64-bit generic hardware server platform in th
 | PD | 4 core+ | 8 GB+ | SSD | 10 Gigabit network card (2 preferred) | 3 |
 | TiKV | 16 core+ | 32 GB+ | SSD | 10 Gigabit network card (2 preferred) | 3 |
 | TiFlash | 48 core+ | 128 GB+ | 1 or more SSDs | 10 Gigabit network card (2 preferred) | 2 |
+| TiCDC | 16 core+ | 64 GB+ | SSD | 10 Gigabit network card (2 preferred) | 2 |
 | Monitor | 8 core+ | 16 GB+ | SAS | Gigabit network card | 1 |
 
 > **Note:**
@@ -87,6 +89,8 @@ Before you deploy TiFlash, note the following items:
 - It is recommended to deploy TiFlash on different nodes from TiKV. If you must deploy TiFlash and TiKV on the same node, increase the number of CPU cores and memory, and try to deploy TiFlash and TiKV on different disks to avoid interfering each other.
 - The total capacity of the TiFlash disks is calculated in this way: `the data volume of the entire TiKV cluster to be replicated / the number of TiKV replicas * the number of TiFlash replicas`. For example, if the overall planned capacity of TiKV is 1 TB, the number of TiKV replicas is 3, and the number of TiFlash replicas is 2, then the recommended total capacity of TiFlash is `1024 GB / 3 * 2`. You can replicate only the data of some tables. In such case, determine the TiFlash capacity according to the data volume of the tables to be replicated.
 
+Before you deploy TiCDC, note that it is recommended to deploy TiCDC on PCIe-SSD disks larger than 200 GB.
+
 ## Network requirements
 
 As an open source distributed NewSQL database, TiDB requires the following network port configuration to run. Based on the TiDB deployment in actual environments, the administrator can open relevant ports in the network side and host side.
diff --git a/ticdc/manage-ticdc.md b/ticdc/manage-ticdc.md
index a08a49993de94..983ef85ff1e79 100644
--- a/ticdc/manage-ticdc.md
+++ b/ticdc/manage-ticdc.md
@@ -12,6 +12,21 @@ This document describes how to deploy a TiCDC cluster and how to manage the TiCD
 
 You can deploy TiCDC using either TiUP or Binary.
 
+### Software and hardware recommendations
+
+In production environments, the recommendations of software and hardware for TiCDC are as follows:
+
+| Linux OS       | Version        |
+| :----------------------- | :----------: |
+| Red Hat Enterprise Linux | 7.3 or later versions   |
+| CentOS                   | 7.3 or later versions   |
+
+| **CPU** | **Memory** | **Disk Type** | **Network** | **Instances (Minimum Requirements)** |
+| --- | --- | --- | --- | --- |
+| 16 core+ | 64 GB+ | SSD | 10 Gigabit network card (2 preferred） | 2 |
+
+For more information, see [Software and Hardware Recommendations](/hardware-and-software-requirements.md)
+
 ### Use TiUP
 
 If you use TiUP to deploy TiCDC, you can choose one of the following ways: