diff --git a/en/docs/design/api-monetization/monetizing-an-api.md b/en/docs/design/api-monetization/monetizing-an-api.md
index 66e65332d4..1e02d92ef6 100644
--- a/en/docs/design/api-monetization/monetizing-an-api.md
+++ b/en/docs/design/api-monetization/monetizing-an-api.md
@@ -138,7 +138,13 @@ Let's use the [wso2-am-stripe-plugin](https://github.com/wso2-extensions/wso2-am
   
     1. Download and add the database related connector JAR into the`<APIM_HOME/repository/components/lib` directory. 
         
-        As a MySQL database is used for this example scenario, download and copy the [MySQL connector JAR](https://mvnrepository.com/artifact/mysql/mysql-connector-java/5.1.36) into the `<APIM_HOME/repository/components/lib` directory.
+        As a MySQL database is used for this example scenario, download and copy the [MySQL connector JAR](https://downloads.mysql.com/archives/c-j/) into the `<APIM_HOME/repository/components/lib` directory.
+
+        !!! tip
+            Look for the compatible MySQL Connector version based on the MySQL version being used.
+
+            - For MySQL version 8.0.x, the compatible MySQL Connector version is **8.0.x**.    
+            - For MySQL version 8.4.x, the compatible MySQL Connector version is **8.4.x**.
 
     2. Configure the WSO2 API Manager related datasource.  
         
diff --git a/en/docs/install-and-setup/setup/distributed-deployment/product-profiles.md b/en/docs/install-and-setup/setup/distributed-deployment/product-profiles.md
index 637c0fa61e..3ba4436844 100644
--- a/en/docs/install-and-setup/setup/distributed-deployment/product-profiles.md
+++ b/en/docs/install-and-setup/setup/distributed-deployment/product-profiles.md
@@ -82,8 +82,14 @@ Create an optimized distribution for a particular API-M profile.
    
      For example, if you are using a MySQL database,
 
-     1. Download the MySQL connector JAR file and extract it.
+     1. Download the [MySQL connector JAR](https://downloads.mysql.com/archives/c-j/) file and extract it.
      
+        !!! tip
+            Look for the compatible MySQL Connector version based on the MySQL version being used.
+
+            - For MySQL version 8.0.x, the compatible MySQL Connector version is **8.0.x**.
+            - For MySQL version 8.4.x, the compatible MySQL Connector version is **8.4.x**.
+
      2. Copy it to the `<API-M_HOME>/repository/components/lib/` directory.
 
 3. Create the required databases, namely the API-M database (`apimgtdb` also known as `WSO2_AM_DB`) and the shared database (`WSO2_SHARED_DB` also known as `shareddb`).
diff --git a/en/docs/install-and-setup/setup/setting-up-databases/changing-default-databases/changing-to-mysql.md b/en/docs/install-and-setup/setup/setting-up-databases/changing-default-databases/changing-to-mysql.md
index 951c6cc7ef..253f8e9af4 100644
--- a/en/docs/install-and-setup/setup/setting-up-databases/changing-default-databases/changing-to-mysql.md
+++ b/en/docs/install-and-setup/setup/setting-up-databases/changing-default-databases/changing-to-mysql.md
@@ -109,9 +109,15 @@ Follow the  instructions below to set up a MySQL database:
 
 1. Unzip the WSO2 API Manager pack. Let's refer to it as `<API-M_HOME>`.
 
-2. Download the MySQL Java connector [JAR file](https://dev.mysql.com/downloads/connector/j/), and extract it.
+2. Download the MySQL Java Connector from [MySQL Connector/J (Archived Versions)](https://downloads.mysql.com/archives/c-j/), and extract it.
 
-3. Copy it to the `<API-M_HOME>/repository/components/lib/` directory in all the nodes of the cluster.
+    !!! tip
+        Look for the compatible MySQL Connector version based on the MySQL version being used.
+
+        - For MySQL version 8.0.x, the compatible MySQL Connector version is **8.0.x**.
+        - For MySQL version 8.4.x, the compatible MySQL Connector version is **8.4.x**.
+
+3. Copy the connector JAR file to the `<API-M_HOME>/repository/components/lib/` directory in all the nodes of the cluster.
 
 !!! tip
     Be sure to use the connector version that is supported by the MySQL version you use. If you come across any issues due to version incompatibility, follow the  instructions below: