diff --git a/docs/en/cloud/reference/byoc.md b/docs/en/cloud/reference/byoc.md
index 428332324dc..6e638e2faa5 100644
--- a/docs/en/cloud/reference/byoc.md
+++ b/docs/en/cloud/reference/byoc.md
@@ -62,37 +62,81 @@ After creating the CloudFormation stack, you will be prompted to set up the infr
 
 ### Optional: Setup VPC Peering
 
-To create or delete VPC peering for ClickHouse BYOC, submit a ticket with the following details:
+To create or delete VPC peering for ClickHouse BYOC, follow the steps:
 
-- ClickHouse BYOC name for the VPC peering request.  
-- VPC ID (`vpc-xxxxxx`) to peer with the BYOC VPC.  
-- CIDR range of the VPC.  
-- AWS account owning the peering VPC.  
-- AWS region of the VPC.  
+#### Step 1 Create a peering connection
+1. Navigate to the VPC Dashboard in ClickHouse BYOC account.
+2. Select Peering Connections.
+3. Click Create Peering Connection
+4. Set the VPC Requester to the ClickHouse VPC ID.
+5. Set the VPC Acceptor to the target VPC ID. (Select another account if applicable)
+6. Click Create Peering Connection.
 
-Once the support ticket is received and processed, you will need to complete a few steps in your AWS account to finalize the peering setup:
+<br />
+
+<img src={require('./images/byoc-vpcpeering-1.png').default}
+    alt='BYOC Create Peering Connection'
+    class='image'
+    style={{width: '800px'}}
+/>
+
+<br />
+
+#### Step 2 Accept the peering connection request
+Go to the peering account, in the (VPC -> Peering connections -> Actions -> Accept request) page customer can approve this VPC peering request.
+
+<br />
+
+<img src={require('./images/byoc-vpcpeering-2.png').default}
+    alt='BYOC Accept Peering Connection'
+    class='image'
+    style={{width: '800px'}}
+/>
 
-1. Accept the VPC peering request in the AWS account of the peered VPC.  
-   - Navigate to **VPC -> Peering connections -> Actions -> Accept request**.
+<br />
 
-2. Adjust the route table for the peered VPC:  
-   - Locate the subnet in the peered VPC that needs to connect to the ClickHouse instance.  
-   - Edit the subnet's route table and add a route with the following configuration:  
-     - **Destination**: ClickHouse BYOC VPC CIDR (e.g., `10.0.0.0/16`)  
-     - **Target**: Peering Connection (`pcx-12345678`, the actual ID will appear in the dropdown list)  
+#### Step 3 Add destination to ClickHouse VPC route tables
+In ClickHouse BYOC account,
+1. Select Route Tables in the VPC Dashboard.
+2. Search for the ClickHouse VPC ID. Edit each route table attached to the private subnets.
+3. Click the Edit button under the Routes tab.
+4. Click Add another route.
+5. Enter the CIDR range of the target VPC for the Destination.
+6. Select “Peering Connection” and the ID of the peering connection for the Target.
 
 <br />
 
-<img src={require('./images/byoc-2.png').default}
-    alt='BYOC network configuration'
+<img src={require('./images/byoc-vpcpeering-3.png').default}
+    alt='BYOC Add route table'
     class='image'
-    style={{width: '600px'}}
+    style={{width: '800px'}}
 />
 
 <br />
 
-3. Check existing security groups and ensure no rules block access to the BYOC VPC.
+#### Step 4 Add destination to the target VPC route tables
+In the peering AWS account,
+1. Select Route Tables in the VPC Dashboard.
+2. Search for the target VPC ID.
+3. Click the Edit button under the Routes tab.
+4. Click Add another route.
+5. Enter the CIDR range of the ClickHouse VPC for the Destination.
+6. Select “Peering Connection” and the ID of the peering connection for the Target.
 
+<br />
+
+<img src={require('./images/byoc-vpcpeering-4.png').default}
+    alt='BYOC Add route table'
+    class='image'
+    style={{width: '800px'}}
+/>
+
+<br />
+
+#### Step 5 Enable Private Load Balancer for ClickHouse BYOC
+Contact ClickHouse support to enable Private Load Balancer. 
+
+---
 The ClickHouse service should now be accessible from the peered VPC.
 
 To access ClickHouse privately, a private load balancer and endpoint are provisioned for secure connectivity from the user's peered VPC. The private endpoint follows the public endpoint format with a `-private` suffix. For example:  
diff --git a/docs/en/cloud/reference/images/byoc-2.png b/docs/en/cloud/reference/images/byoc-2.png
deleted file mode 100644
index dcb54f675b6..00000000000
Binary files a/docs/en/cloud/reference/images/byoc-2.png and /dev/null differ
diff --git a/docs/en/cloud/reference/images/byoc-vpcpeering-1.png b/docs/en/cloud/reference/images/byoc-vpcpeering-1.png
new file mode 100644
index 00000000000..d131ef8ce51
Binary files /dev/null and b/docs/en/cloud/reference/images/byoc-vpcpeering-1.png differ
diff --git a/docs/en/cloud/reference/images/byoc-vpcpeering-2.png b/docs/en/cloud/reference/images/byoc-vpcpeering-2.png
new file mode 100644
index 00000000000..50b688b392f
Binary files /dev/null and b/docs/en/cloud/reference/images/byoc-vpcpeering-2.png differ
diff --git a/docs/en/cloud/reference/images/byoc-vpcpeering-3.png b/docs/en/cloud/reference/images/byoc-vpcpeering-3.png
new file mode 100644
index 00000000000..750612d2a00
Binary files /dev/null and b/docs/en/cloud/reference/images/byoc-vpcpeering-3.png differ
diff --git a/docs/en/cloud/reference/images/byoc-vpcpeering-4.png b/docs/en/cloud/reference/images/byoc-vpcpeering-4.png
new file mode 100644
index 00000000000..6d71606a709
Binary files /dev/null and b/docs/en/cloud/reference/images/byoc-vpcpeering-4.png differ