diff --git a/pages/account_and_service_management/account_information/iam-permission-groups/guide.de-de.md b/pages/account_and_service_management/account_information/iam-permission-groups/guide.de-de.md
index 9ec0b27f318..26095e6c06c 100644
--- a/pages/account_and_service_management/account_information/iam-permission-groups/guide.de-de.md
+++ b/pages/account_and_service_management/account_information/iam-permission-groups/guide.de-de.md
@@ -1,7 +1,7 @@
 ---
 title: Liste der Berechtigungsgruppen bei OVHcloud (EN)
 excerpt: Details of permission groups provided by OVHcloud
-updated: 2023-12-06
+updated: 2025-04-15
 ---
 
 <style>
@@ -2298,66 +2298,6 @@ This permission group resumes the rights formerly carried by the `nicBilling` ro
     {
         "action": "publicCloudProject:apiovh:database/kafkaMirrorMaker/replication/get"
     },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/capabilities/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/logs/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/maintenance/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/metric/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/node/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/advancedConfiguration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/backup/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/capabilities/advancedConfiguration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/capabilities/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/ipRestriction/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/logs/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/maintenance/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/metric/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/namespace/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/node/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/user/get"
-    },
     {
         "action": "publicCloudProject:apiovh:database/mongodb/backup/get"
     },
diff --git a/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-asia.md b/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-asia.md
index 3d953071116..c01c9aab144 100644
--- a/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-asia.md
+++ b/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-asia.md
@@ -1,7 +1,7 @@
 ---
 title: List of permission groups managed by OVHcloud
 excerpt: Details of permission groups provided by OVHcloud
-updated: 2023-12-06
+updated: 2025-04-15
 ---
 
 <style>
@@ -2298,66 +2298,6 @@ This permission group resumes the rights formerly carried by the `nicBilling` ro
     {
         "action": "publicCloudProject:apiovh:database/kafkaMirrorMaker/replication/get"
     },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/capabilities/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/logs/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/maintenance/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/metric/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/node/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/advancedConfiguration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/backup/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/capabilities/advancedConfiguration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/capabilities/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/ipRestriction/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/logs/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/maintenance/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/metric/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/namespace/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/node/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/user/get"
-    },
     {
         "action": "publicCloudProject:apiovh:database/mongodb/backup/get"
     },
diff --git a/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-au.md b/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-au.md
index 3d953071116..c01c9aab144 100644
--- a/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-au.md
+++ b/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-au.md
@@ -1,7 +1,7 @@
 ---
 title: List of permission groups managed by OVHcloud
 excerpt: Details of permission groups provided by OVHcloud
-updated: 2023-12-06
+updated: 2025-04-15
 ---
 
 <style>
@@ -2298,66 +2298,6 @@ This permission group resumes the rights formerly carried by the `nicBilling` ro
     {
         "action": "publicCloudProject:apiovh:database/kafkaMirrorMaker/replication/get"
     },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/capabilities/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/logs/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/maintenance/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/metric/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/node/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/advancedConfiguration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/backup/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/capabilities/advancedConfiguration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/capabilities/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/ipRestriction/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/logs/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/maintenance/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/metric/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/namespace/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/node/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/user/get"
-    },
     {
         "action": "publicCloudProject:apiovh:database/mongodb/backup/get"
     },
diff --git a/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-ca.md b/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-ca.md
index 3d953071116..c01c9aab144 100644
--- a/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-ca.md
+++ b/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-ca.md
@@ -1,7 +1,7 @@
 ---
 title: List of permission groups managed by OVHcloud
 excerpt: Details of permission groups provided by OVHcloud
-updated: 2023-12-06
+updated: 2025-04-15
 ---
 
 <style>
@@ -2298,66 +2298,6 @@ This permission group resumes the rights formerly carried by the `nicBilling` ro
     {
         "action": "publicCloudProject:apiovh:database/kafkaMirrorMaker/replication/get"
     },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/capabilities/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/logs/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/maintenance/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/metric/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/node/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/advancedConfiguration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/backup/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/capabilities/advancedConfiguration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/capabilities/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/ipRestriction/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/logs/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/maintenance/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/metric/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/namespace/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/node/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/user/get"
-    },
     {
         "action": "publicCloudProject:apiovh:database/mongodb/backup/get"
     },
diff --git a/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-gb.md b/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-gb.md
index 3d953071116..c01c9aab144 100644
--- a/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-gb.md
+++ b/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-gb.md
@@ -1,7 +1,7 @@
 ---
 title: List of permission groups managed by OVHcloud
 excerpt: Details of permission groups provided by OVHcloud
-updated: 2023-12-06
+updated: 2025-04-15
 ---
 
 <style>
@@ -2298,66 +2298,6 @@ This permission group resumes the rights formerly carried by the `nicBilling` ro
     {
         "action": "publicCloudProject:apiovh:database/kafkaMirrorMaker/replication/get"
     },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/capabilities/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/logs/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/maintenance/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/metric/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/node/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/advancedConfiguration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/backup/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/capabilities/advancedConfiguration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/capabilities/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/ipRestriction/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/logs/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/maintenance/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/metric/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/namespace/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/node/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/user/get"
-    },
     {
         "action": "publicCloudProject:apiovh:database/mongodb/backup/get"
     },
diff --git a/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-ie.md b/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-ie.md
index 3d953071116..c01c9aab144 100644
--- a/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-ie.md
+++ b/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-ie.md
@@ -1,7 +1,7 @@
 ---
 title: List of permission groups managed by OVHcloud
 excerpt: Details of permission groups provided by OVHcloud
-updated: 2023-12-06
+updated: 2025-04-15
 ---
 
 <style>
@@ -2298,66 +2298,6 @@ This permission group resumes the rights formerly carried by the `nicBilling` ro
     {
         "action": "publicCloudProject:apiovh:database/kafkaMirrorMaker/replication/get"
     },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/capabilities/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/logs/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/maintenance/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/metric/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/node/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/advancedConfiguration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/backup/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/capabilities/advancedConfiguration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/capabilities/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/ipRestriction/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/logs/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/maintenance/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/metric/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/namespace/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/node/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/user/get"
-    },
     {
         "action": "publicCloudProject:apiovh:database/mongodb/backup/get"
     },
diff --git a/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-sg.md b/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-sg.md
index 3d953071116..c01c9aab144 100644
--- a/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-sg.md
+++ b/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-sg.md
@@ -1,7 +1,7 @@
 ---
 title: List of permission groups managed by OVHcloud
 excerpt: Details of permission groups provided by OVHcloud
-updated: 2023-12-06
+updated: 2025-04-15
 ---
 
 <style>
@@ -2298,66 +2298,6 @@ This permission group resumes the rights formerly carried by the `nicBilling` ro
     {
         "action": "publicCloudProject:apiovh:database/kafkaMirrorMaker/replication/get"
     },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/capabilities/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/logs/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/maintenance/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/metric/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/node/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/advancedConfiguration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/backup/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/capabilities/advancedConfiguration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/capabilities/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/ipRestriction/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/logs/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/maintenance/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/metric/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/namespace/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/node/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/user/get"
-    },
     {
         "action": "publicCloudProject:apiovh:database/mongodb/backup/get"
     },
diff --git a/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-us.md b/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-us.md
index 3d953071116..c01c9aab144 100644
--- a/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-us.md
+++ b/pages/account_and_service_management/account_information/iam-permission-groups/guide.en-us.md
@@ -1,7 +1,7 @@
 ---
 title: List of permission groups managed by OVHcloud
 excerpt: Details of permission groups provided by OVHcloud
-updated: 2023-12-06
+updated: 2025-04-15
 ---
 
 <style>
@@ -2298,66 +2298,6 @@ This permission group resumes the rights formerly carried by the `nicBilling` ro
     {
         "action": "publicCloudProject:apiovh:database/kafkaMirrorMaker/replication/get"
     },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/capabilities/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/logs/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/maintenance/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/metric/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/node/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/advancedConfiguration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/backup/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/capabilities/advancedConfiguration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/capabilities/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/ipRestriction/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/logs/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/maintenance/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/metric/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/namespace/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/node/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/user/get"
-    },
     {
         "action": "publicCloudProject:apiovh:database/mongodb/backup/get"
     },
diff --git a/pages/account_and_service_management/account_information/iam-permission-groups/guide.es-es.md b/pages/account_and_service_management/account_information/iam-permission-groups/guide.es-es.md
index c7a26ed38c6..ebd71894163 100644
--- a/pages/account_and_service_management/account_information/iam-permission-groups/guide.es-es.md
+++ b/pages/account_and_service_management/account_information/iam-permission-groups/guide.es-es.md
@@ -1,7 +1,7 @@
 ---
 title: Lista de grupos de permisos de OVHcloud (EN)
 excerpt: Details of permission groups provided by OVHcloud
-updated: 2023-12-06
+updated: 2025-04-15
 ---
 
 <style>
@@ -2298,66 +2298,6 @@ This permission group resumes the rights formerly carried by the `nicBilling` ro
     {
         "action": "publicCloudProject:apiovh:database/kafkaMirrorMaker/replication/get"
     },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/capabilities/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/logs/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/maintenance/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/metric/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/node/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/advancedConfiguration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/backup/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/capabilities/advancedConfiguration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/capabilities/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/ipRestriction/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/logs/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/maintenance/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/metric/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/namespace/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/node/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/user/get"
-    },
     {
         "action": "publicCloudProject:apiovh:database/mongodb/backup/get"
     },
diff --git a/pages/account_and_service_management/account_information/iam-permission-groups/guide.es-us.md b/pages/account_and_service_management/account_information/iam-permission-groups/guide.es-us.md
index c7a26ed38c6..ebd71894163 100644
--- a/pages/account_and_service_management/account_information/iam-permission-groups/guide.es-us.md
+++ b/pages/account_and_service_management/account_information/iam-permission-groups/guide.es-us.md
@@ -1,7 +1,7 @@
 ---
 title: Lista de grupos de permisos de OVHcloud (EN)
 excerpt: Details of permission groups provided by OVHcloud
-updated: 2023-12-06
+updated: 2025-04-15
 ---
 
 <style>
@@ -2298,66 +2298,6 @@ This permission group resumes the rights formerly carried by the `nicBilling` ro
     {
         "action": "publicCloudProject:apiovh:database/kafkaMirrorMaker/replication/get"
     },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/capabilities/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/logs/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/maintenance/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/metric/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/node/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/advancedConfiguration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/backup/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/capabilities/advancedConfiguration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/capabilities/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/ipRestriction/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/logs/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/maintenance/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/metric/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/namespace/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/node/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/user/get"
-    },
     {
         "action": "publicCloudProject:apiovh:database/mongodb/backup/get"
     },
diff --git a/pages/account_and_service_management/account_information/iam-permission-groups/guide.fr-ca.md b/pages/account_and_service_management/account_information/iam-permission-groups/guide.fr-ca.md
index 60d0710f286..a5ac98f22bd 100644
--- a/pages/account_and_service_management/account_information/iam-permission-groups/guide.fr-ca.md
+++ b/pages/account_and_service_management/account_information/iam-permission-groups/guide.fr-ca.md
@@ -1,7 +1,7 @@
 ---
 title: "Liste des groupes de permissions d'OVHcloud"
 excerpt: "Détail des groupes de permissions mis à disposition par OVHcloud"
-updated: 2023-12-06
+updated: 2025-04-15
 ---
 
 <style>
@@ -2296,66 +2296,6 @@ Ce groupe de permissions reprend les droits anciennement porté par le rôle nic
     {
         "action": "publicCloudProject:apiovh:database/kafkaMirrorMaker/replication/get"
     },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/capabilities/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/logs/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/maintenance/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/metric/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/node/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/advancedConfiguration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/backup/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/capabilities/advancedConfiguration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/capabilities/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/ipRestriction/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/logs/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/maintenance/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/metric/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/namespace/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/node/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/user/get"
-    },
     {
         "action": "publicCloudProject:apiovh:database/mongodb/backup/get"
     },
diff --git a/pages/account_and_service_management/account_information/iam-permission-groups/guide.fr-fr.md b/pages/account_and_service_management/account_information/iam-permission-groups/guide.fr-fr.md
index 60d0710f286..a5ac98f22bd 100644
--- a/pages/account_and_service_management/account_information/iam-permission-groups/guide.fr-fr.md
+++ b/pages/account_and_service_management/account_information/iam-permission-groups/guide.fr-fr.md
@@ -1,7 +1,7 @@
 ---
 title: "Liste des groupes de permissions d'OVHcloud"
 excerpt: "Détail des groupes de permissions mis à disposition par OVHcloud"
-updated: 2023-12-06
+updated: 2025-04-15
 ---
 
 <style>
@@ -2296,66 +2296,6 @@ Ce groupe de permissions reprend les droits anciennement porté par le rôle nic
     {
         "action": "publicCloudProject:apiovh:database/kafkaMirrorMaker/replication/get"
     },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/capabilities/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/logs/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/maintenance/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/metric/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/node/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/advancedConfiguration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/backup/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/capabilities/advancedConfiguration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/capabilities/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/ipRestriction/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/logs/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/maintenance/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/metric/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/namespace/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/node/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/user/get"
-    },
     {
         "action": "publicCloudProject:apiovh:database/mongodb/backup/get"
     },
diff --git a/pages/account_and_service_management/account_information/iam-permission-groups/guide.it-it.md b/pages/account_and_service_management/account_information/iam-permission-groups/guide.it-it.md
index 11ace8c09ae..88704327e8e 100644
--- a/pages/account_and_service_management/account_information/iam-permission-groups/guide.it-it.md
+++ b/pages/account_and_service_management/account_information/iam-permission-groups/guide.it-it.md
@@ -1,7 +1,7 @@
 ---
 title: Lista dei gruppi di permessi di OVHcloud (EN)
 excerpt: Details of permission groups provided by OVHcloud
-updated: 2023-12-06
+updated: 2025-04-15
 ---
 
 <style>
@@ -2298,66 +2298,6 @@ This permission group resumes the rights formerly carried by the `nicBilling` ro
     {
         "action": "publicCloudProject:apiovh:database/kafkaMirrorMaker/replication/get"
     },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/capabilities/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/logs/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/maintenance/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/metric/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/node/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/advancedConfiguration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/backup/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/capabilities/advancedConfiguration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/capabilities/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/ipRestriction/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/logs/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/maintenance/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/metric/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/namespace/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/node/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/user/get"
-    },
     {
         "action": "publicCloudProject:apiovh:database/mongodb/backup/get"
     },
diff --git a/pages/account_and_service_management/account_information/iam-permission-groups/guide.pl-pl.md b/pages/account_and_service_management/account_information/iam-permission-groups/guide.pl-pl.md
index 40734f43ad0..e12454364a2 100644
--- a/pages/account_and_service_management/account_information/iam-permission-groups/guide.pl-pl.md
+++ b/pages/account_and_service_management/account_information/iam-permission-groups/guide.pl-pl.md
@@ -1,7 +1,7 @@
 ---
 title: Lista grup uprawnień OVHcloud (EN)
 excerpt: Details of permission groups provided by OVHcloud
-updated: 2023-12-06
+updated: 2025-04-15
 ---
 
 <style>
@@ -2298,66 +2298,6 @@ This permission group resumes the rights formerly carried by the `nicBilling` ro
     {
         "action": "publicCloudProject:apiovh:database/kafkaMirrorMaker/replication/get"
     },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/capabilities/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/logs/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/maintenance/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/metric/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/node/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/advancedConfiguration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/backup/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/capabilities/advancedConfiguration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/capabilities/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/ipRestriction/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/logs/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/maintenance/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/metric/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/namespace/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/node/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/user/get"
-    },
     {
         "action": "publicCloudProject:apiovh:database/mongodb/backup/get"
     },
diff --git a/pages/account_and_service_management/account_information/iam-permission-groups/guide.pt-pt.md b/pages/account_and_service_management/account_information/iam-permission-groups/guide.pt-pt.md
index 2b266d1da51..f43dd1af7ce 100644
--- a/pages/account_and_service_management/account_information/iam-permission-groups/guide.pt-pt.md
+++ b/pages/account_and_service_management/account_information/iam-permission-groups/guide.pt-pt.md
@@ -1,7 +1,7 @@
 ---
 title: Lista dos grupos de permissões da OVHcloud (EN)
 excerpt: Details of permission groups provided by OVHcloud
-updated: 2023-12-06
+updated: 2025-04-15
 ---
 
 <style>
@@ -2298,66 +2298,6 @@ This permission group resumes the rights formerly carried by the `nicBilling` ro
     {
         "action": "publicCloudProject:apiovh:database/kafkaMirrorMaker/replication/get"
     },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/capabilities/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/logs/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/maintenance/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/metric/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3aggregator/node/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/advancedConfiguration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/backup/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/capabilities/advancedConfiguration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/capabilities/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/integration/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/ipRestriction/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/logs/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/maintenance/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/metric/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/namespace/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/node/get"
-    },
-    {
-        "action": "publicCloudProject:apiovh:database/m3db/user/get"
-    },
     {
         "action": "publicCloudProject:apiovh:database/mongodb/backup/get"
     },
diff --git a/pages/index-translations.de.yaml b/pages/index-translations.de.yaml
index c4d1c71f6d8..4db5bb0ac74 100644
--- a/pages/index-translations.de.yaml
+++ b/pages/index-translations.de.yaml
@@ -161,10 +161,6 @@ public-cloud-data-analytics-kafka-mirrormaker: Kafka MirrorMaker
 public-cloud-data-analytics-kafka-mirrormaker-guides: Kafka MirrorMaker - Guides
 public-cloud-databases-cassandra: Cassandra
 public-cloud-databases-cassandra-guides: Cassandra - Guides
-public-cloud-databases-m3db: M3db
-public-cloud-databases-m3db-guides: M3db - Guides
-public-cloud-databases-m3-aggregator: M3 Aggregator
-public-cloud-databases-m3-aggregator-guides: M3 Aggregator - Guides
 public-cloud-data-analytics-opensearch: OpenSearch
 public-cloud-data-analytics-opensearch-guides: OpenSearch - Guides
 public-cloud-compute: Compute
diff --git a/pages/index-translations.es.yaml b/pages/index-translations.es.yaml
index ced2edf9c02..796f5acb737 100755
--- a/pages/index-translations.es.yaml
+++ b/pages/index-translations.es.yaml
@@ -161,10 +161,6 @@ public-cloud-data-analytics-kafka-mirrormaker: Kafka MirrorMaker
 public-cloud-data-analytics-kafka-mirrormaker-guides: Kafka MirrorMaker - Guides
 public-cloud-databases-cassandra: Cassandra
 public-cloud-databases-cassandra-guides: Cassandra - Guides
-public-cloud-databases-m3db: M3db
-public-cloud-databases-m3db-guides: M3db - Guides
-public-cloud-databases-m3-aggregator: M3 Aggregator
-public-cloud-databases-m3-aggregator-guides: M3 Aggregator - Guides
 public-cloud-data-analytics-opensearch: OpenSearch
 public-cloud-data-analytics-opensearch-guides: OpenSearch - Guides
 public-cloud-compute: Compute
diff --git a/pages/index-translations.fq.yaml b/pages/index-translations.fq.yaml
index baef8c6e5e5..a4de0c39ef3 100755
--- a/pages/index-translations.fq.yaml
+++ b/pages/index-translations.fq.yaml
@@ -161,10 +161,6 @@ public-cloud-data-analytics-kafka-mirrormaker: Kafka MirrorMaker
 public-cloud-data-analytics-kafka-mirrormaker-guides: Kafka MirrorMaker - Guides
 public-cloud-databases-cassandra: Cassandra
 public-cloud-databases-cassandra-guides: Cassandra - Guides
-public-cloud-databases-m3db: M3db
-public-cloud-databases-m3db-guides: M3db - Guides
-public-cloud-databases-m3-aggregator: M3 Aggregator
-public-cloud-databases-m3-aggregator-guides: M3 Aggregator - Guides
 public-cloud-data-analytics-opensearch: OpenSearch
 public-cloud-data-analytics-opensearch-guides: OpenSearch - Guides
 public-cloud-compute: Compute
diff --git a/pages/index-translations.fr.yaml b/pages/index-translations.fr.yaml
index 2abd4a9b739..cb806ac9dfd 100755
--- a/pages/index-translations.fr.yaml
+++ b/pages/index-translations.fr.yaml
@@ -162,10 +162,6 @@ public-cloud-data-analytics-kafka-mirrormaker: Kafka MirrorMaker
 public-cloud-data-analytics-kafka-mirrormaker-guides: Kafka MirrorMaker - Guides
 public-cloud-databases-cassandra: Cassandra
 public-cloud-databases-cassandra-guides: Cassandra - Guides
-public-cloud-databases-m3db: M3db
-public-cloud-databases-m3db-guides: M3db - Guides
-public-cloud-databases-m3-aggregator: M3 Aggregator
-public-cloud-databases-m3-aggregator-guides: M3 Aggregator - Guides
 public-cloud-data-analytics-opensearch: OpenSearch
 public-cloud-data-analytics-opensearch-guides: OpenSearch - Guides
 public-cloud-compute: Compute
diff --git a/pages/index-translations.it.yaml b/pages/index-translations.it.yaml
index bc8b40a430b..2e29a5314cc 100644
--- a/pages/index-translations.it.yaml
+++ b/pages/index-translations.it.yaml
@@ -161,10 +161,6 @@ public-cloud-data-analytics-kafka-mirrormaker: Kafka MirrorMaker
 public-cloud-data-analytics-kafka-mirrormaker-guides: Kafka MirrorMaker - Guides
 public-cloud-databases-cassandra: Cassandra
 public-cloud-databases-cassandra-guides: Cassandra - Guides
-public-cloud-databases-m3db: M3db
-public-cloud-databases-m3db-guides: M3db - Guides
-public-cloud-databases-m3-aggregator: M3 Aggregator
-public-cloud-databases-m3-aggregator-guides: M3 Aggregator - Guides
 public-cloud-data-analytics-opensearch: OpenSearch
 public-cloud-data-analytics-opensearch-guides: OpenSearch - Guides
 public-cloud-compute: Compute
diff --git a/pages/index-translations.pl.yaml b/pages/index-translations.pl.yaml
index 30af2e26289..ebb5ca95391 100755
--- a/pages/index-translations.pl.yaml
+++ b/pages/index-translations.pl.yaml
@@ -161,10 +161,6 @@ public-cloud-data-analytics-kafka-mirrormaker: Kafka MirrorMaker
 public-cloud-data-analytics-kafka-mirrormaker-guides: Kafka MirrorMaker - Guides
 public-cloud-databases-cassandra: Cassandra
 public-cloud-databases-cassandra-guides: Cassandra - Guides
-public-cloud-databases-m3db: M3db
-public-cloud-databases-m3db-guides: M3db - Guides
-public-cloud-databases-m3-aggregator: M3 Aggregator
-public-cloud-databases-m3-aggregator-guides: M3 Aggregator - Guides
 public-cloud-data-analytics-opensearch: OpenSearch
 public-cloud-data-analytics-opensearch-guides: OpenSearch - Guides
 public-cloud-compute: Compute
diff --git a/pages/index-translations.pt.yaml b/pages/index-translations.pt.yaml
index 23ed4c434d3..b7b8b432503 100755
--- a/pages/index-translations.pt.yaml
+++ b/pages/index-translations.pt.yaml
@@ -161,10 +161,6 @@ public-cloud-data-analytics-kafka-mirrormaker: Kafka MirrorMaker
 public-cloud-data-analytics-kafka-mirrormaker-guides: Kafka MirrorMaker - Guides
 public-cloud-databases-cassandra: Cassandra
 public-cloud-databases-cassandra-guides: Cassandra - Guides
-public-cloud-databases-m3db: M3db
-public-cloud-databases-m3db-guides: M3db - Guides
-public-cloud-databases-m3-aggregator: M3 Aggregator
-public-cloud-databases-m3-aggregator-guides: M3 Aggregator - Guides
 public-cloud-data-analytics-opensearch: OpenSearch
 public-cloud-data-analytics-opensearch-guides: OpenSearch - Guides
 public-cloud-compute: Compute
diff --git a/pages/index.md b/pages/index.md
index 73a34354f6f..8625f63b2a1 100644
--- a/pages/index.md
+++ b/pages/index.md
@@ -819,13 +819,6 @@
                 + [Cassandra - Capabilities and Limitations](public_cloud/public_cloud_databases/cassandra_01_capabilities)
                 + [Cassandra - Configure your Cassandra instance to accept incoming connections](public_cloud/public_cloud_databases/cassandra_02_prepare_for_incoming_connections)
                 + [Cassandra - Advanced parameters references](public_cloud/public_cloud_databases/cassandra_03_advanced_parameters_references)
-        + [M3db](products/public-cloud-databases-m3db)
-            + [Guides](public-cloud-databases-m3db-guides)
-                + [M3db - Capabilities and Limitations](public_cloud/public_cloud_databases/m3db_01_capabilities)
-                + [M3db - Configure your M3db instance to accept incoming connections](public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections)
-        + [M3 Aggregator](products/public-cloud-databases-m3-aggregator)
-            + [Guides](public-cloud-databases-m3-aggregator-guides)
-                + [M3 Aggregator - Capabilities and Limitations](public_cloud/public_cloud_databases/m3aggregator_01_capabilities)
     + [Containers & Orchestration](products/public-cloud-containers-orchestration)
         + [Managed Kubernetes (K8s)](products/public-cloud-containers-orchestration-managed-kubernetes-k8s)
             + [Getting started](public-cloud-containers-orchestration-managed-kubernetes-k8s-getting-started)
diff --git a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.de-de.md b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.de-de.md
index fa557148f85..1a8fbf47bbf 100644
--- a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.de-de.md
+++ b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.de-de.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka or Cassandra cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-asia.md b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-asia.md
index b1fa2e77327..c641f362988 100644
--- a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-asia.md
+++ b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-asia.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, or Cassandra cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-au.md b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-au.md
index b1fa2e77327..c641f362988 100644
--- a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-au.md
+++ b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-au.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, or Cassandra cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-ca.md b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-ca.md
index b1fa2e77327..c641f362988 100644
--- a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-ca.md
+++ b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-ca.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, or Cassandra cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-gb.md b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-gb.md
index b1fa2e77327..c641f362988 100644
--- a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-gb.md
+++ b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-gb.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, or Cassandra cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-ie.md b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-ie.md
index b1fa2e77327..c641f362988 100644
--- a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-ie.md
+++ b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-ie.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, or Cassandra cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-sg.md b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-sg.md
index b1fa2e77327..c641f362988 100644
--- a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-sg.md
+++ b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-sg.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, or Cassandra cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-us.md b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-us.md
index b1fa2e77327..c641f362988 100644
--- a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-us.md
+++ b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.en-us.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, or Cassandra cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.es-es.md b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.es-es.md
index fa557148f85..9dd5a7ecd30 100644
--- a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.es-es.md
+++ b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.es-es.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, or Cassandra cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.es-us.md b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.es-us.md
index fa557148f85..9dd5a7ecd30 100644
--- a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.es-us.md
+++ b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.es-us.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, or Cassandra cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.fr-ca.md b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.fr-ca.md
index fa557148f85..9dd5a7ecd30 100644
--- a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.fr-ca.md
+++ b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.fr-ca.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, or Cassandra cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.fr-fr.md b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.fr-fr.md
index fa557148f85..9dd5a7ecd30 100644
--- a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.fr-fr.md
+++ b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.fr-fr.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, or Cassandra cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.it-it.md b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.it-it.md
index fa557148f85..9dd5a7ecd30 100644
--- a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.it-it.md
+++ b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.it-it.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, or Cassandra cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.pl-pl.md b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.pl-pl.md
index fa557148f85..9dd5a7ecd30 100644
--- a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.pl-pl.md
+++ b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.pl-pl.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, or Cassandra cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.pt-pt.md b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.pt-pt.md
index fa557148f85..9dd5a7ecd30 100644
--- a/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.pt-pt.md
+++ b/pages/public_cloud/containers_orchestration/managed_private_registry/responsibility-model/guide.pt-pt.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered as a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Redis, Kafka, or Cassandra cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.de-de.md b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.de-de.md
index dc364885c0f..e4904513394 100644
--- a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.de-de.md
+++ b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.de-de.md
@@ -105,7 +105,7 @@ See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/dat
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
+Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-asia.md
index 6c0343780db..0c6bd7f0586 100644
--- a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-asia.md
+++ b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-asia.md
@@ -105,7 +105,7 @@ See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/dat
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
+Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-au.md b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-au.md
index 6cad4abefdb..adca24c002a 100644
--- a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-au.md
+++ b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-au.md
@@ -105,7 +105,7 @@ See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/dat
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
+Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-ca.md
index 40e7f68409a..3d93b226985 100644
--- a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-ca.md
+++ b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-ca.md
@@ -105,7 +105,7 @@ See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/dat
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
+Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-gb.md
index 35bb09bf3c1..31299278b65 100644
--- a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-gb.md
+++ b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-gb.md
@@ -105,7 +105,7 @@ See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/dat
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
+Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-ie.md
index 6dec94749ec..b345288d514 100644
--- a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-ie.md
+++ b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-ie.md
@@ -105,7 +105,7 @@ See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/dat
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
+Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-sg.md
index 25813beaab6..e5046fc18ec 100644
--- a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-sg.md
+++ b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-sg.md
@@ -105,7 +105,7 @@ See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/dat
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
+Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-us.md b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-us.md
index 3dbeb8b4e71..23b10391adb 100644
--- a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-us.md
+++ b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.en-us.md
@@ -105,7 +105,7 @@ See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/dat
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
+Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.es-es.md b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.es-es.md
index d0349e9b7a1..3789dcc30a1 100644
--- a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.es-es.md
+++ b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.es-es.md
@@ -105,7 +105,7 @@ See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/dat
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
+Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.es-us.md b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.es-us.md
index 55ce9e95ee9..14b099d891e 100644
--- a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.es-us.md
+++ b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.es-us.md
@@ -105,7 +105,7 @@ See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/dat
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
+Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.fr-ca.md
index aa84c2889c2..2340e6fca20 100644
--- a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.fr-ca.md
+++ b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.fr-ca.md
@@ -105,7 +105,7 @@ See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/dat
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
+Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.fr-fr.md
index 3fcc77d76f1..bc5b236ec58 100644
--- a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.fr-fr.md
+++ b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.fr-fr.md
@@ -105,7 +105,7 @@ See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/dat
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
+Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.it-it.md b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.it-it.md
index cdd5a1b5040..ad9a3b1e7d4 100644
--- a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.it-it.md
+++ b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.it-it.md
@@ -105,7 +105,7 @@ See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/dat
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
+Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.pl-pl.md
index 276f0c6074a..571f495369b 100644
--- a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.pl-pl.md
+++ b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.pl-pl.md
@@ -105,7 +105,7 @@ See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/dat
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
+Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.pt-pt.md
index 42afba06998..abd76869b48 100644
--- a/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.pt-pt.md
+++ b/pages/public_cloud/public_cloud_databases/cassandra_01_capabilities/guide.pt-pt.md
@@ -105,7 +105,7 @@ See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/dat
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
+Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Cassandra logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.de-de.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.de-de.md
index 7b3b8517443..2dd3d1c2a42 100644
--- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.de-de.md
+++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.de-de.md
@@ -29,7 +29,6 @@ MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minute
 PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 Caching | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
-M3 | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 
 ## Off-site backup
diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-asia.md
index 7b3b8517443..2dd3d1c2a42 100644
--- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-asia.md
+++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-asia.md
@@ -29,7 +29,6 @@ MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minute
 PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 Caching | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
-M3 | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 
 ## Off-site backup
diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-au.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-au.md
index 7b3b8517443..2dd3d1c2a42 100644
--- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-au.md
+++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-au.md
@@ -29,7 +29,6 @@ MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minute
 PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 Caching | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
-M3 | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 
 ## Off-site backup
diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-ca.md
index 7b3b8517443..2dd3d1c2a42 100644
--- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-ca.md
+++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-ca.md
@@ -29,7 +29,6 @@ MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minute
 PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 Caching | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
-M3 | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 
 ## Off-site backup
diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-gb.md
index 7b3b8517443..2dd3d1c2a42 100644
--- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-gb.md
+++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-gb.md
@@ -29,7 +29,6 @@ MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minute
 PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 Caching | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
-M3 | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 
 ## Off-site backup
diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-ie.md
index 7b3b8517443..2dd3d1c2a42 100644
--- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-ie.md
+++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-ie.md
@@ -29,7 +29,6 @@ MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minute
 PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 Caching | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
-M3 | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 
 ## Off-site backup
diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-sg.md
index 7b3b8517443..2dd3d1c2a42 100644
--- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-sg.md
+++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-sg.md
@@ -29,7 +29,6 @@ MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minute
 PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 Caching | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
-M3 | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 
 ## Off-site backup
diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-us.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-us.md
index 7b3b8517443..2dd3d1c2a42 100644
--- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-us.md
+++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.en-us.md
@@ -29,7 +29,6 @@ MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minute
 PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 Caching | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
-M3 | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 
 ## Off-site backup
diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.es-es.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.es-es.md
index 7b3b8517443..2dd3d1c2a42 100644
--- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.es-es.md
+++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.es-es.md
@@ -29,7 +29,6 @@ MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minute
 PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 Caching | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
-M3 | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 
 ## Off-site backup
diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.es-us.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.es-us.md
index 7b3b8517443..2dd3d1c2a42 100644
--- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.es-us.md
+++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.es-us.md
@@ -29,7 +29,6 @@ MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minute
 PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 Caching | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
-M3 | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 
 ## Off-site backup
diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.fr-ca.md
index 3d4674f3342..d56d13bbfa0 100644
--- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.fr-ca.md
+++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.fr-ca.md
@@ -29,7 +29,6 @@ MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minute
 PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 Caching | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
-M3 | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 
 ## Off-site backup
diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.fr-fr.md
index 3d4674f3342..d56d13bbfa0 100644
--- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.fr-fr.md
+++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.fr-fr.md
@@ -29,7 +29,6 @@ MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minute
 PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 Caching | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
-M3 | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 
 ## Off-site backup
diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.it-it.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.it-it.md
index 7b3b8517443..2dd3d1c2a42 100644
--- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.it-it.md
+++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.it-it.md
@@ -29,7 +29,6 @@ MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minute
 PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 Caching | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
-M3 | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 
 ## Off-site backup
diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.pl-pl.md
index 7b3b8517443..2dd3d1c2a42 100644
--- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.pl-pl.md
+++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.pl-pl.md
@@ -29,7 +29,6 @@ MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minute
 PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 Caching | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
-M3 | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 
 ## Off-site backup
diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.pt-pt.md
index 7b3b8517443..2dd3d1c2a42 100644
--- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.pt-pt.md
+++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/guide.pt-pt.md
@@ -29,7 +29,6 @@ MongoDB Enterprise | PITR on object storage | Off-site | Continuous | Few minute
 PostgreSQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 MySQL | PITR on object storage | On-Site, Off-Site | Continuous | Few minutes | Yes
 Caching | Backup on object storage | On-Site, Off-Site | 2 times a day | 12h | Yes
-M3 | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 Cassandra | Backup on object storage | On-Site, Off-Site | Daily | 24h | Yes
 
 ## Off-site backup
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.de-de.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.de-de.md
index f8985cf00af..7ececc7b51f 100644
--- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.de-de.md
+++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.de-de.md
@@ -1,7 +1,7 @@
 ---
 title: Public Cloud Databases - How to setup a service integration
 excerpt: Find out how to use Cross Service Integration for Public Cloud Databases engines
-updated: 2023-05-25
+updated: 2025-04-15
 ---
 
 ## Objective
@@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs
 
 The Cross Service Integrations for Logs and Metrics allow you for example:
 
-- To send Caching or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
+- To send Caching or MySQL metrics or Cassandra metrics in PostgreSQL.
 - To send PostgreSQL or MySQL metrics to OpenSearch.
 - To show metrics in Dashboards service.
 
@@ -49,18 +49,16 @@ For that you need:
 ### Integration matrix
 
 - All services support logs to opensearch & kafka_logs to kafka.
-- All services except m3db & m3agg support metrics to pg & metrics to m3db.
+- All services support metrics to pg.
 
 Other integrations:
 
-| source →<br>↓ destination | dashboards service	| m3db	| kafka |
-|:--|---|---|---|
-| pg | dashboard, datasource | | |
-| opensearch | datasource | | |
-| m3db | dashboard, datasource | | |
-| m3agg | | m3agg | |
-| kmm | | | kafka_mirrormaker |
-| kc | | | kafka_connect |
+| source →<br>↓ destination | dashboards service	| kafka |
+|:--|---|---|
+| pg | dashboard, datasource | |
+| opensearch | datasource | |
+| kmm | | kafka_mirrormaker |
+| kc | | kafka_connect |
 
 ## Instructions
 
@@ -81,11 +79,6 @@ Define the `Integration type`{.action} and the `Destination service`{.action}:
 > First create a Public Cloud Database for your *Destination* service via your Control Panel or API.
 >
 
-> [!primary]
->
-> If you want to store the metrics of your *postgresql* cluster to *m3db*, select `m3dbMetrics` as `Integration type`{.action} and `m3db` as `Destination service`{.action}, as shown below.
->
-
 ![Create integration](images/databases_07_cross_service_integration-20220708155848940.png){.thumbnail}
 
 Your first integration is ready:
@@ -182,16 +175,6 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/kafkaMirrorMaker
 >> >
-> M3 Aggregator
->> > [!api]
->> >
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3aggregator
->> >
-> M3db
->> > [!api]
->> >
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3db
->> >
 > MySQL
 >> > [!api]
 >> >
@@ -240,14 +223,6 @@ Get integration capabilities related to your Public Cloud Databases service:
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/capabilities/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/capabilities/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3db/{clusterId}/capabilities/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/mysql/{clusterId}/capabilities/integration
@@ -294,14 +269,6 @@ For that, you need to create a new integration:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3db/{clusterId}/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/mysql/{clusterId}/integration
@@ -358,14 +325,6 @@ Then create a second integration from your *Destination* service name:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3db/{clusterId}/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/mysql/{clusterId}/integration
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-asia.md
index a458bc2bf15..3f716fe19bb 100644
--- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-asia.md
+++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-asia.md
@@ -1,7 +1,7 @@
 ---
 title: Public Cloud Databases - How to setup a service integration
 excerpt: Find out how to use Cross Service Integration for Public Cloud Databases engines
-updated: 2023-05-25
+updated: 2025-04-15
 ---
 
 ## Objective
@@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs
 
 The Cross Service Integrations for Logs and Metrics allow you for example:
 
-- To send Caching or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
+- To send Caching or MySQL metrics or Cassandra metrics in PostgreSQL.
 - To send PostgreSQL or MySQL metrics to OpenSearch.
 - To show metrics in Dashboards service.
 
@@ -49,18 +49,16 @@ For that you need:
 ### Integration matrix
 
 - All services support logs to opensearch & kafka_logs to kafka.
-- All services except m3db & m3agg support metrics to pg & metrics to m3db.
+- All services support metrics to pg.
 
 Other integrations:
 
-| source →<br>↓ destination | dashboards service	| m3db	| kafka |
-|:--|---|---|---|
-| pg | dashboard, datasource | | |
-| opensearch | datasource | | |
-| m3db | dashboard, datasource | | |
-| m3agg | | m3agg | |
-| kmm | | | kafka_mirrormaker |
-| kc | | | kafka_connect |
+| source →<br>↓ destination | dashboards service	| kafka |
+|:--|---|---|
+| pg | dashboard, datasource | |
+| opensearch | datasource | |
+| kmm | | kafka_mirrormaker |
+| kc | | kafka_connect |
 
 ## Instructions
 
@@ -81,11 +79,6 @@ Define the `Integration type`{.action} and the `Destination service`{.action}:
 > First create a Public Cloud Database for your *Destination* service via your Control Panel or API.
 >
 
-> [!primary]
->
-> If you want to store the metrics of your *postgresql* cluster to *m3db*, select `m3dbMetrics` as `Integration type`{.action} and `m3db` as `Destination service`{.action}, as shown below.
->
-
 ![Create integration](images/databases_07_cross_service_integration-20220708155848940.png){.thumbnail}
 
 Your first integration is ready:
@@ -182,16 +175,6 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/kafkaMirrorMaker
 >> >
-> M3 Aggregator
->> > [!api]
->> >
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3aggregator
->> >
-> M3db
->> > [!api]
->> >
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3db
->> >
 > MySQL
 >> > [!api]
 >> >
@@ -240,14 +223,6 @@ Get integration capabilities related to your Public Cloud Databases service:
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/capabilities/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/capabilities/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3db/{clusterId}/capabilities/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/mysql/{clusterId}/capabilities/integration
@@ -294,14 +269,6 @@ For that, you need to create a new integration:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3db/{clusterId}/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/mysql/{clusterId}/integration
@@ -358,14 +325,6 @@ Then create a second integration from your *Destination* service name:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3db/{clusterId}/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/mysql/{clusterId}/integration
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-au.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-au.md
index ccfc7f320cc..e0ad8083cc6 100644
--- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-au.md
+++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-au.md
@@ -1,7 +1,7 @@
 ---
 title: Public Cloud Databases - How to setup a service integration
 excerpt: Find out how to use Cross Service Integration for Public Cloud Databases engines
-updated: 2023-05-25
+updated: 2025-04-15
 ---
 
 ## Objective
@@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs
 
 The Cross Service Integrations for Logs and Metrics allow you for example:
 
-- To send Caching or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
+- To send Caching or MySQL metrics or Cassandra metrics in PostgreSQL.
 - To send PostgreSQL or MySQL metrics to OpenSearch.
 - To show metrics in Dashboards service.
 
@@ -49,18 +49,16 @@ For that you need:
 ### Integration matrix
 
 - All services support logs to opensearch & kafka_logs to kafka.
-- All services except m3db & m3agg support metrics to pg & metrics to m3db.
+- All services support metrics to pg.
 
 Other integrations:
 
-| source →<br>↓ destination | dashboards service	| m3db	| kafka |
-|:--|---|---|---|
-| pg | dashboard, datasource | | |
-| opensearch | datasource | | |
-| m3db | dashboard, datasource | | |
-| m3agg | | m3agg | |
-| kmm | | | kafka_mirrormaker |
-| kc | | | kafka_connect |
+| source →<br>↓ destination | dashboards service	| kafka |
+|:--|---|---|
+| pg | dashboard, datasource | |
+| opensearch | datasource | |
+| kmm | | kafka_mirrormaker |
+| kc | | kafka_connect |
 
 ## Instructions
 
@@ -81,11 +79,6 @@ Define the `Integration type`{.action} and the `Destination service`{.action}:
 > First create a Public Cloud Database for your *Destination* service via your Control Panel or API.
 >
 
-> [!primary]
->
-> If you want to store the metrics of your *postgresql* cluster to *m3db*, select `m3dbMetrics` as `Integration type`{.action} and `m3db` as `Destination service`{.action}, as shown below.
->
-
 ![Create integration](images/databases_07_cross_service_integration-20220708155848940.png){.thumbnail}
 
 Your first integration is ready:
@@ -182,16 +175,6 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/kafkaMirrorMaker
 >> >
-> M3 Aggregator
->> > [!api]
->> >
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3aggregator
->> >
-> M3db
->> > [!api]
->> >
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3db
->> >
 > MySQL
 >> > [!api]
 >> >
@@ -240,14 +223,6 @@ Get integration capabilities related to your Public Cloud Databases service:
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/capabilities/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/capabilities/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3db/{clusterId}/capabilities/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/mysql/{clusterId}/capabilities/integration
@@ -294,14 +269,6 @@ For that, you need to create a new integration:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3db/{clusterId}/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/mysql/{clusterId}/integration
@@ -358,14 +325,6 @@ Then create a second integration from your *Destination* service name:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3db/{clusterId}/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/mysql/{clusterId}/integration
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-ca.md
index c851900ba75..cb926855fb1 100644
--- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-ca.md
+++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-ca.md
@@ -1,7 +1,7 @@
 ---
 title: Public Cloud Databases - How to setup a service integration
 excerpt: Find out how to use Cross Service Integration for Public Cloud Databases engines
-updated: 2023-05-25
+updated: 2025-04-15
 ---
 
 ## Objective
@@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs
 
 The Cross Service Integrations for Logs and Metrics allow you for example:
 
-- To send Caching or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
+- To send Caching or MySQL metrics or Cassandra metrics in PostgreSQL.
 - To send PostgreSQL or MySQL metrics to OpenSearch.
 - To show metrics in Dashboards service.
 
@@ -49,18 +49,16 @@ For that you need:
 ### Integration matrix
 
 - All services support logs to opensearch & kafka_logs to kafka.
-- All services except m3db & m3agg support metrics to pg & metrics to m3db.
+- All services support metrics to pg.
 
 Other integrations:
 
-| source →<br>↓ destination | dashboards service	| m3db	| kafka |
-|:--|---|---|---|
-| pg | dashboard, datasource | | |
-| opensearch | datasource | | |
-| m3db | dashboard, datasource | | |
-| m3agg | | m3agg | |
-| kmm | | | kafka_mirrormaker |
-| kc | | | kafka_connect |
+| source →<br>↓ destination | dashboards service	| kafka |
+|:--|---|---|
+| pg | dashboard, datasource | |
+| opensearch | datasource | |
+| kmm | | kafka_mirrormaker |
+| kc | | kafka_connect |
 
 ## Instructions
 
@@ -81,11 +79,6 @@ Define the `Integration type`{.action} and the `Destination service`{.action}:
 > First create a Public Cloud Database for your *Destination* service via your Control Panel or API.
 >
 
-> [!primary]
->
-> If you want to store the metrics of your *postgresql* cluster to *m3db*, select `m3dbMetrics` as `Integration type`{.action} and `m3db` as `Destination service`{.action}, as shown below.
->
-
 ![Create integration](images/databases_07_cross_service_integration-20220708155848940.png){.thumbnail}
 
 Your first integration is ready:
@@ -182,16 +175,6 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/kafkaMirrorMaker
 >> >
-> M3 Aggregator
->> > [!api]
->> >
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3aggregator
->> >
-> M3db
->> > [!api]
->> >
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3db
->> >
 > MySQL
 >> > [!api]
 >> >
@@ -240,14 +223,6 @@ Get integration capabilities related to your Public Cloud Databases service:
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/capabilities/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/capabilities/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3db/{clusterId}/capabilities/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/mysql/{clusterId}/capabilities/integration
@@ -294,14 +269,6 @@ For that, you need to create a new integration:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3db/{clusterId}/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/mysql/{clusterId}/integration
@@ -358,14 +325,6 @@ Then create a second integration from your *Destination* service name:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3db/{clusterId}/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/mysql/{clusterId}/integration
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-gb.md
index 743230bacb3..fd297f9cea4 100644
--- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-gb.md
+++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-gb.md
@@ -1,7 +1,7 @@
 ---
 title: Public Cloud Databases - How to setup a service integration
 excerpt: Find out how to use Cross Service Integration for Public Cloud Databases engines
-updated: 2023-05-25
+updated: 2025-04-15
 ---
 
 ## Objective
@@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs
 
 The Cross Service Integrations for Logs and Metrics allow you for example:
 
-- To send Caching or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
+- To send Caching or MySQL metrics or Cassandra metrics in PostgreSQL.
 - To send PostgreSQL or MySQL metrics to OpenSearch.
 - To show metrics in Dashboards service.
 
@@ -37,30 +37,28 @@ For that you need:
 - A source service
 - A destination service
 
-![Best practices](images/databases_07_cross_service_integration-20220708091945946.png){.thumbnail}
+![Best practices](images/databases_07_cross_service_integration_best_practice.png){.thumbnail}
 
 > [!warning]
 >
 > Although it is possible to define the same cluster as destination service and source service, this is a bad practice for multiple reasons (performance, security, resiliency, ...)
 >
 
-![Bad practices](images/databases_07_cross_service_integration-20220719203753927.png)
+![Bad practices](images/databases_07_cross_service_integration_bad_practice.png)
 
 ### Integration matrix
 
 - All services support logs to opensearch & kafka_logs to kafka.
-- All services except m3db & m3agg support metrics to pg & metrics to m3db.
+- All services support metrics to pg.
 
 Other integrations:
 
-| source →<br>↓ destination | dashboards service	| m3db	| kafka |
-|:--|---|---|---|
-| pg | dashboard, datasource | | |
-| opensearch | datasource | | |
-| m3db | dashboard, datasource | | |
-| m3agg | | m3agg | |
-| kmm | | | kafka_mirrormaker |
-| kc | | | kafka_connect |
+| source →<br>↓ destination | dashboards service	| kafka |
+|:--|---|---|
+| pg | dashboard, datasource | |
+| opensearch | datasource | |
+| kmm | | kafka_mirrormaker |
+| kc | | kafka_connect |
 
 ## Instructions
 
@@ -81,16 +79,11 @@ Define the `Integration type`{.action} and the `Destination service`{.action}:
 > First create a Public Cloud Database for your *Destination* service via your Control Panel or API.
 >
 
-> [!primary]
->
-> If you want to store the metrics of your *postgresql* cluster to *m3db*, select `m3dbMetrics` as `Integration type`{.action} and `m3db` as `Destination service`{.action}, as shown below.
->
-
-![Create integration](images/databases_07_cross_service_integration-20220708155848940.png){.thumbnail}
+![Create integration](images/databases_07_cross_service_integration_creation.png){.thumbnail}
 
 Your first integration is ready:
 
-![Result](images/databases_07_cross_service_integration-20220708160028574.png){.thumbnail}
+![Result](images/databases_07_cross_service_integration_list_example.png){.thumbnail}
 
 > [!primary]
 >
@@ -105,7 +98,7 @@ Your first integration is ready:
 
 Go to the `Service integration`{.action} tab of your `Destination service` service and click on `Add an integration`{.action}
 
-![Service integration](images/databases_07_cross_service_integration-20220708160203565.png){.thumbnail}
+![Service integration](images/databases_07_cross_service_integration_list_add.png){.thumbnail}
 
 > [!primary]
 >
@@ -114,11 +107,11 @@ Go to the `Service integration`{.action} tab of your `Destination service` servi
 
 Define `grafanaDashboard` as `Integration type`{.action} and the `Source service`{.action}:
 
-![Create integration](images/databases_07_cross_service_integration-20220708160400509.png){.thumbnail}
+![Create integration](images/databases_07_cross_service_integration_creation_grafana.png){.thumbnail}
 
 Your second integration is ready:
 
-![Result](images/databases_07_cross_service_integration-20220708160441618.png){.thumbnail}
+![Result](images/databases_07_cross_service_integration_list_example_2.png){.thumbnail}
 
 Connect to your Dashboards instance and browse the dashboards:
 
@@ -182,16 +175,6 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/kafkaMirrorMaker
 >> >
-> M3 Aggregator
->> > [!api]
->> >
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3aggregator
->> >
-> M3db
->> > [!api]
->> >
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3db
->> >
 > MySQL
 >> > [!api]
 >> >
@@ -240,14 +223,6 @@ Get integration capabilities related to your Public Cloud Databases service:
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/capabilities/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/capabilities/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3db/{clusterId}/capabilities/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/mysql/{clusterId}/capabilities/integration
@@ -265,7 +240,7 @@ Get integration capabilities related to your Public Cloud Databases service:
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/caching/{clusterId}/capabilities/integration
 >> >
 
-![Get Integration Capabilities](images/databases_07_cross_service_integration-20220708142931159.png){.thumbnail}
+![Get Integration Capabilities](images/databases_07_cross_service_integration_api_capa_integration.png){.thumbnail}
 
 #### Store yours logs or metrics
 
@@ -294,14 +269,6 @@ For that, you need to create a new integration:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3db/{clusterId}/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/mysql/{clusterId}/integration
@@ -321,7 +288,7 @@ For that, you need to create a new integration:
 
 Fill in the form with the information corresponding to the type of integration chosen.
 
-![Create a new integration](images/databases_07_cross_service_integration-2022070814275082.png){.thumbnail}
+![Create a new integration](images/databases_07_cross_service_integration_api_post_integration.png){.thumbnail}
 
 The `destionationServiceId` and the `sourceServiceId` correspond to the destination cluster ID and to the source cluster ID.
 
@@ -333,7 +300,7 @@ For that, first create a Public Cloud Database for Dashboards via our Control Pa
 
 Once done, get the `GrafanaDashboard` integration capability related to the destination service:
 
-![Get Dashboards integration capabilitie](images/databases_07_cross_service_integration-20220708141900814.png){.thumbnail}
+![Get Dashboards integration capabilitie](images/databases_07_cross_service_integration_api_capa_integration.png){.thumbnail}
 
 Then create a second integration from your *Destination* service name:
 
@@ -358,14 +325,6 @@ Then create a second integration from your *Destination* service name:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3db/{clusterId}/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/mysql/{clusterId}/integration
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-ie.md
index d926c3a8063..698531983f0 100644
--- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-ie.md
+++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-ie.md
@@ -1,7 +1,7 @@
 ---
 title: Public Cloud Databases - How to setup a service integration
 excerpt: Find out how to use Cross Service Integration for Public Cloud Databases engines
-updated: 2023-05-25
+updated: 2025-04-15
 ---
 
 ## Objective
@@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs
 
 The Cross Service Integrations for Logs and Metrics allow you for example:
 
-- To send Caching or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
+- To send Caching or MySQL metrics or Cassandra metrics in PostgreSQL.
 - To send PostgreSQL or MySQL metrics to OpenSearch.
 - To show metrics in Dashboards service.
 
@@ -49,18 +49,16 @@ For that you need:
 ### Integration matrix
 
 - All services support logs to opensearch & kafka_logs to kafka.
-- All services except m3db & m3agg support metrics to pg & metrics to m3db.
+- All services support metrics to pg.
 
 Other integrations:
 
-| source →<br>↓ destination | dashboards service	| m3db	| kafka |
-|:--|---|---|---|
-| pg | dashboard, datasource | | |
-| opensearch | datasource | | |
-| m3db | dashboard, datasource | | |
-| m3agg | | m3agg | |
-| kmm | | | kafka_mirrormaker |
-| kc | | | kafka_connect |
+| source →<br>↓ destination | dashboards service	| kafka |
+|:--|---|---|
+| pg | dashboard, datasource | |
+| opensearch | datasource | |
+| kmm | | kafka_mirrormaker |
+| kc | | kafka_connect |
 
 ## Instructions
 
@@ -81,11 +79,6 @@ Define the `Integration type`{.action} and the `Destination service`{.action}:
 > First create a Public Cloud Database for your *Destination* service via your Control Panel or API.
 >
 
-> [!primary]
->
-> If you want to store the metrics of your *postgresql* cluster to *m3db*, select `m3dbMetrics` as `Integration type`{.action} and `m3db` as `Destination service`{.action}, as shown below.
->
-
 ![Create integration](images/databases_07_cross_service_integration-20220708155848940.png){.thumbnail}
 
 Your first integration is ready:
@@ -182,16 +175,6 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/kafkaMirrorMaker
 >> >
-> M3 Aggregator
->> > [!api]
->> >
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3aggregator
->> >
-> M3db
->> > [!api]
->> >
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3db
->> >
 > MySQL
 >> > [!api]
 >> >
@@ -240,14 +223,6 @@ Get integration capabilities related to your Public Cloud Databases service:
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/capabilities/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/capabilities/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3db/{clusterId}/capabilities/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/mysql/{clusterId}/capabilities/integration
@@ -294,14 +269,6 @@ For that, you need to create a new integration:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3db/{clusterId}/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/mysql/{clusterId}/integration
@@ -358,14 +325,6 @@ Then create a second integration from your *Destination* service name:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3db/{clusterId}/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/mysql/{clusterId}/integration
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-sg.md
index 6f4e2f3343f..7bfa2be3a37 100644
--- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-sg.md
+++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-sg.md
@@ -1,7 +1,7 @@
 ---
 title: Public Cloud Databases - How to setup a service integration
 excerpt: Find out how to use Cross Service Integration for Public Cloud Databases engines
-updated: 2023-05-25
+updated: 2025-04-15
 ---
 
 ## Objective
@@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs
 
 The Cross Service Integrations for Logs and Metrics allow you for example:
 
-- To send Caching or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
+- To send Caching or MySQL metrics or Cassandra metrics in PostgreSQL.
 - To send PostgreSQL or MySQL metrics to OpenSearch.
 - To show metrics in Dashboards service.
 
@@ -49,18 +49,16 @@ For that you need:
 ### Integration matrix
 
 - All services support logs to opensearch & kafka_logs to kafka.
-- All services except m3db & m3agg support metrics to pg & metrics to m3db.
+- All services support metrics to pg.
 
 Other integrations:
 
-| source →<br>↓ destination | dashboards service	| m3db	| kafka |
-|:--|---|---|---|
-| pg | dashboard, datasource | | |
-| opensearch | datasource | | |
-| m3db | dashboard, datasource | | |
-| m3agg | | m3agg | |
-| kmm | | | kafka_mirrormaker |
-| kc | | | kafka_connect |
+| source →<br>↓ destination | dashboards service	| kafka |
+|:--|---|---|
+| pg | dashboard, datasource | |
+| opensearch | datasource | |
+| kmm | | kafka_mirrormaker |
+| kc | | kafka_connect |
 
 ## Instructions
 
@@ -81,11 +79,6 @@ Define the `Integration type`{.action} and the `Destination service`{.action}:
 > First create a Public Cloud Database for your *Destination* service via your Control Panel or API.
 >
 
-> [!primary]
->
-> If you want to store the metrics of your *postgresql* cluster to *m3db*, select `m3dbMetrics` as `Integration type`{.action} and `m3db` as `Destination service`{.action}, as shown below.
->
-
 ![Create integration](images/databases_07_cross_service_integration-20220708155848940.png){.thumbnail}
 
 Your first integration is ready:
@@ -182,16 +175,6 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/kafkaMirrorMaker
 >> >
-> M3 Aggregator
->> > [!api]
->> >
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3aggregator
->> >
-> M3db
->> > [!api]
->> >
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3db
->> >
 > MySQL
 >> > [!api]
 >> >
@@ -240,14 +223,6 @@ Get integration capabilities related to your Public Cloud Databases service:
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/capabilities/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/capabilities/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3db/{clusterId}/capabilities/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/mysql/{clusterId}/capabilities/integration
@@ -294,14 +269,6 @@ For that, you need to create a new integration:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3db/{clusterId}/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/mysql/{clusterId}/integration
@@ -358,14 +325,6 @@ Then create a second integration from your *Destination* service name:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3db/{clusterId}/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/mysql/{clusterId}/integration
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-us.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-us.md
index 85759eb9964..f00dc6cfff8 100644
--- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-us.md
+++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.en-us.md
@@ -1,7 +1,7 @@
 ---
 title: Public Cloud Databases - How to setup a service integration
 excerpt: Find out how to use Cross Service Integration for Public Cloud Databases engines
-updated: 2023-05-25
+updated: 2025-04-15
 ---
 
 ## Objective
@@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs
 
 The Cross Service Integrations for Logs and Metrics allow you for example:
 
-- To send Caching or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
+- To send Caching or MySQL metrics or Cassandra metrics in PostgreSQL.
 - To send PostgreSQL or MySQL metrics to OpenSearch.
 - To show metrics in Dashboards service.
 
@@ -49,18 +49,16 @@ For that you need:
 ### Integration matrix
 
 - All services support logs to opensearch & kafka_logs to kafka.
-- All services except m3db & m3agg support metrics to pg & metrics to m3db.
+- All services support metrics to pg.
 
 Other integrations:
 
-| source →<br>↓ destination | dashboards service	| m3db	| kafka |
-|:--|---|---|---|
-| pg | dashboard, datasource | | |
-| opensearch | datasource | | |
-| m3db | dashboard, datasource | | |
-| m3agg | | m3agg | |
-| kmm | | | kafka_mirrormaker |
-| kc | | | kafka_connect |
+| source →<br>↓ destination | dashboards service	| kafka |
+|:--|---|---|
+| pg | dashboard, datasource | |
+| opensearch | datasource | |
+| kmm | | kafka_mirrormaker |
+| kc | | kafka_connect |
 
 ## Instructions
 
@@ -81,11 +79,6 @@ Define the `Integration type`{.action} and the `Destination service`{.action}:
 > First create a Public Cloud Database for your *Destination* service via your Control Panel or API.
 >
 
-> [!primary]
->
-> If you want to store the metrics of your *postgresql* cluster to *m3db*, select `m3dbMetrics` as `Integration type`{.action} and `m3db` as `Destination service`{.action}, as shown below.
->
-
 ![Create integration](images/databases_07_cross_service_integration-20220708155848940.png){.thumbnail}
 
 Your first integration is ready:
@@ -182,16 +175,6 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/kafkaMirrorMaker
 >> >
-> M3 Aggregator
->> > [!api]
->> >
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3aggregator
->> >
-> M3db
->> > [!api]
->> >
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3db
->> >
 > MySQL
 >> > [!api]
 >> >
@@ -240,14 +223,6 @@ Get integration capabilities related to your Public Cloud Databases service:
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/capabilities/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/capabilities/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3db/{clusterId}/capabilities/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/mysql/{clusterId}/capabilities/integration
@@ -294,14 +269,6 @@ For that, you need to create a new integration:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3db/{clusterId}/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/mysql/{clusterId}/integration
@@ -358,14 +325,6 @@ Then create a second integration from your *Destination* service name:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3db/{clusterId}/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/mysql/{clusterId}/integration
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.es-es.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.es-es.md
index e78760f6d65..f513a69a95a 100644
--- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.es-es.md
+++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.es-es.md
@@ -1,7 +1,7 @@
 ---
 title: Public Cloud Databases - How to setup a service integration
 excerpt: Find out how to use Cross Service Integration for Public Cloud Databases engines
-updated: 2023-05-25
+updated: 2025-04-15
 ---
 
 ## Objective
@@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs
 
 The Cross Service Integrations for Logs and Metrics allow you for example:
 
-- To send Caching or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
+- To send Caching or MySQL metrics or Cassandra metrics in PostgreSQL.
 - To send PostgreSQL or MySQL metrics to OpenSearch.
 - To show metrics in Dashboards service.
 
@@ -49,18 +49,16 @@ For that you need:
 ### Integration matrix
 
 - All services support logs to opensearch & kafka_logs to kafka.
-- All services except m3db & m3agg support metrics to pg & metrics to m3db.
+- All services support metrics to pg.
 
 Other integrations:
 
-| source →<br>↓ destination | dashboards service	| m3db	| kafka |
-|:--|---|---|---|
-| pg | dashboard, datasource | | |
-| opensearch | datasource | | |
-| m3db | dashboard, datasource | | |
-| m3agg | | m3agg | |
-| kmm | | | kafka_mirrormaker |
-| kc | | | kafka_connect |
+| source →<br>↓ destination | dashboards service	| kafka |
+|:--|---|---|
+| pg | dashboard, datasource | |
+| opensearch | datasource | |
+| kmm | | kafka_mirrormaker |
+| kc | | kafka_connect |
 
 ## Instructions
 
@@ -81,11 +79,6 @@ Define the `Integration type`{.action} and the `Destination service`{.action}:
 > First create a Public Cloud Database for your *Destination* service via your Control Panel or API.
 >
 
-> [!primary]
->
-> If you want to store the metrics of your *postgresql* cluster to *m3db*, select `m3dbMetrics` as `Integration type`{.action} and `m3db` as `Destination service`{.action}, as shown below.
->
-
 ![Create integration](images/databases_07_cross_service_integration-20220708155848940.png){.thumbnail}
 
 Your first integration is ready:
@@ -182,16 +175,6 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/kafkaMirrorMaker
 >> >
-> M3 Aggregator
->> > [!api]
->> >
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3aggregator
->> >
-> M3db
->> > [!api]
->> >
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3db
->> >
 > MySQL
 >> > [!api]
 >> >
@@ -240,14 +223,6 @@ Get integration capabilities related to your Public Cloud Databases service:
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/capabilities/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/capabilities/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3db/{clusterId}/capabilities/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/mysql/{clusterId}/capabilities/integration
@@ -294,14 +269,6 @@ For that, you need to create a new integration:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3db/{clusterId}/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/mysql/{clusterId}/integration
@@ -358,14 +325,6 @@ Then create a second integration from your *Destination* service name:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3db/{clusterId}/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/mysql/{clusterId}/integration
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.es-us.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.es-us.md
index 69fce2da287..038489e3e47 100644
--- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.es-us.md
+++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.es-us.md
@@ -1,7 +1,7 @@
 ---
 title: Public Cloud Databases - How to setup a service integration
 excerpt: Find out how to use Cross Service Integration for Public Cloud Databases engines
-updated: 2023-05-25
+updated: 2025-04-15
 ---
 
 ## Objective
@@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs
 
 The Cross Service Integrations for Logs and Metrics allow you for example:
 
-- To send Caching or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
+- To send Caching or MySQL metrics or Cassandra metrics in PostgreSQL.
 - To send PostgreSQL or MySQL metrics to OpenSearch.
 - To show metrics in Dashboards service.
 
@@ -49,18 +49,16 @@ For that you need:
 ### Integration matrix
 
 - All services support logs to opensearch & kafka_logs to kafka.
-- All services except m3db & m3agg support metrics to pg & metrics to m3db.
+- All services support metrics to pg.
 
 Other integrations:
 
-| source →<br>↓ destination | dashboards service	| m3db	| kafka |
-|:--|---|---|---|
-| pg | dashboard, datasource | | |
-| opensearch | datasource | | |
-| m3db | dashboard, datasource | | |
-| m3agg | | m3agg | |
-| kmm | | | kafka_mirrormaker |
-| kc | | | kafka_connect |
+| source →<br>↓ destination | dashboards service	| kafka |
+|:--|---|---|
+| pg | dashboard, datasource | |
+| opensearch | datasource | |
+| kmm | | kafka_mirrormaker |
+| kc | | kafka_connect |
 
 ## Instructions
 
@@ -81,11 +79,6 @@ Define the `Integration type`{.action} and the `Destination service`{.action}:
 > First create a Public Cloud Database for your *Destination* service via your Control Panel or API.
 >
 
-> [!primary]
->
-> If you want to store the metrics of your *postgresql* cluster to *m3db*, select `m3dbMetrics` as `Integration type`{.action} and `m3db` as `Destination service`{.action}, as shown below.
->
-
 ![Create integration](images/databases_07_cross_service_integration-20220708155848940.png){.thumbnail}
 
 Your first integration is ready:
@@ -182,16 +175,6 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/kafkaMirrorMaker
 >> >
-> M3 Aggregator
->> > [!api]
->> >
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3aggregator
->> >
-> M3db
->> > [!api]
->> >
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3db
->> >
 > MySQL
 >> > [!api]
 >> >
@@ -240,14 +223,6 @@ Get integration capabilities related to your Public Cloud Databases service:
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/capabilities/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/capabilities/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3db/{clusterId}/capabilities/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/mysql/{clusterId}/capabilities/integration
@@ -294,14 +269,6 @@ For that, you need to create a new integration:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3db/{clusterId}/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/mysql/{clusterId}/integration
@@ -358,14 +325,6 @@ Then create a second integration from your *Destination* service name:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3db/{clusterId}/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/mysql/{clusterId}/integration
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.fr-ca.md
index e8fc51b1787..cbbb572bbea 100644
--- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.fr-ca.md
+++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.fr-ca.md
@@ -1,7 +1,7 @@
 ---
 title: Public Cloud Databases - Comment mettre en place une intégration interservices (EN)
 excerpt: Find out how to use Cross Service Integration for Public Cloud Databases engines
-updated: 2023-05-25
+updated: 2025-04-15
 ---
 
 ## Objective
@@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs
 
 The Cross Service Integrations for Logs and Metrics allow you for example:
 
-- To send Caching or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
+- To send Caching or MySQL metrics or Cassandra metrics in PostgreSQL.
 - To send PostgreSQL or MySQL metrics to OpenSearch.
 - To show metrics in Dashboards service.
 
@@ -49,18 +49,16 @@ For that you need:
 ### Integration matrix
 
 - All services support logs to opensearch & kafka_logs to kafka.
-- All services except m3db & m3agg support metrics to pg & metrics to m3db.
+- All services support metrics to pg.
 
 Other integrations:
 
-| source →<br>↓ destination | dashboards service	| m3db	| kafka |
-|:--|---|---|---|
-| pg | dashboard, datasource | | |
-| opensearch | datasource | | |
-| m3db | dashboard, datasource | | |
-| m3agg | | m3agg | |
-| kmm | | | kafka_mirrormaker |
-| kc | | | kafka_connect |
+| source →<br>↓ destination | dashboards service	| kafka |
+|:--|---|---|
+| pg | dashboard, datasource | |
+| opensearch | datasource | |
+| kmm | | kafka_mirrormaker |
+| kc | | kafka_connect |
 
 ## Instructions
 
@@ -81,11 +79,6 @@ Define the `Integration type`{.action} and the `Destination service`{.action}:
 > First create a Public Cloud Database for your *Destination* service via your Control Panel or API.
 >
 
-> [!primary]
->
-> If you want to store the metrics of your *postgresql* cluster to *m3db*, select `m3dbMetrics` as `Integration type`{.action} and `m3db` as `Destination service`{.action}, as shown below.
->
-
 ![Create integration](images/databases_07_cross_service_integration-20220708155848940.png){.thumbnail}
 
 Your first integration is ready:
@@ -182,16 +175,6 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/kafkaMirrorMaker
 >> >
-> M3 Aggregator
->> > [!api]
->> >
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3aggregator
->> >
-> M3db
->> > [!api]
->> >
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3db
->> >
 > MySQL
 >> > [!api]
 >> >
@@ -240,14 +223,6 @@ Get integration capabilities related to your Public Cloud Databases service:
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/capabilities/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/capabilities/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3db/{clusterId}/capabilities/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/mysql/{clusterId}/capabilities/integration
@@ -294,14 +269,6 @@ For that, you need to create a new integration:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3db/{clusterId}/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/mysql/{clusterId}/integration
@@ -358,14 +325,6 @@ Then create a second integration from your *Destination* service name:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3db/{clusterId}/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/mysql/{clusterId}/integration
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.fr-fr.md
index 745cfaea97f..824321ca3ee 100644
--- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.fr-fr.md
+++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.fr-fr.md
@@ -1,7 +1,7 @@
 ---
 title: Public Cloud Databases - Comment mettre en place une intégration interservices (EN)
 excerpt: Find out how to use Cross Service Integration for Public Cloud Databases engines
-updated: 2023-05-25
+updated: 2025-04-15
 ---
 
 ## Objective
@@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs
 
 The Cross Service Integrations for Logs and Metrics allow you for example:
 
-- To send Caching or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
+- To send Caching or MySQL metrics or Cassandra metrics in PostgreSQL.
 - To send PostgreSQL or MySQL metrics to OpenSearch.
 - To show metrics in Dashboards service.
 
@@ -37,30 +37,28 @@ For that you need:
 - A source service
 - A destination service
 
-![Best practices](images/databases_07_cross_service_integration-20220708091945946.png){.thumbnail}
+![Best practices](images/databases_07_cross_service_integration_best_practice.png){.thumbnail}
 
 > [!warning]
 >
 > Although it is possible to define the same cluster as destination service and source service, this is a bad practice for multiple reasons (performance, security, resiliency, ...)
 >
 
-![Bad practices](images/databases_07_cross_service_integration-20220719203753927.png)
+![Bad practices](images/databases_07_cross_service_integration_bad_practice.png)
 
 ### Integration matrix
 
 - All services support logs to opensearch & kafka_logs to kafka.
-- All services except m3db & m3agg support metrics to pg & metrics to m3db.
+- All services support metrics to pg.
 
 Other integrations:
 
-| source →<br>↓ destination | dashboards service	| m3db	| kafka |
-|:--|---|---|---|
-| pg | dashboard, datasource | | |
-| opensearch | datasource | | |
-| m3db | dashboard, datasource | | |
-| m3agg | | m3agg | |
-| kmm | | | kafka_mirrormaker |
-| kc | | | kafka_connect |
+| source →<br>↓ destination | dashboards service	| kafka |
+|:--|---|---|
+| pg | dashboard, datasource | |
+| opensearch | datasource | |
+| kmm | | kafka_mirrormaker |
+| kc | | kafka_connect |
 
 ## Instructions
 
@@ -81,16 +79,11 @@ Define the `Integration type`{.action} and the `Destination service`{.action}:
 > First create a Public Cloud Database for your *Destination* service via your Control Panel or API.
 >
 
-> [!primary]
->
-> If you want to store the metrics of your *postgresql* cluster to *m3db*, select `m3dbMetrics` as `Integration type`{.action} and `m3db` as `Destination service`{.action}, as shown below.
->
-
-![Create integration](images/databases_07_cross_service_integration-20220708155848940.png){.thumbnail}
+![Create integration](images/databases_07_cross_service_integration_creation.png){.thumbnail}
 
 Your first integration is ready:
 
-![Result](images/databases_07_cross_service_integration-20220708160028574.png){.thumbnail}
+![Result](images/databases_07_cross_service_integration_list_example.png){.thumbnail}
 
 > [!primary]
 >
@@ -105,7 +98,7 @@ Your first integration is ready:
 
 Go to the `Service integration`{.action} tab of your `Destination service` service and click on `Add an integration`{.action}
 
-![Service integration](images/databases_07_cross_service_integration-20220708160203565.png){.thumbnail}
+![Service integration](images/databases_07_cross_service_integration_list_add.png){.thumbnail}
 
 > [!primary]
 >
@@ -114,11 +107,11 @@ Go to the `Service integration`{.action} tab of your `Destination service` servi
 
 Define `grafanaDashboard` as `Integration type`{.action} and the `Source service`{.action}:
 
-![Create integration](images/databases_07_cross_service_integration-20220708160400509.png){.thumbnail}
+![Create integration](images/databases_07_cross_service_integration_creation_grafana.png){.thumbnail}
 
 Your second integration is ready:
 
-![Result](images/databases_07_cross_service_integration-20220708160441618.png){.thumbnail}
+![Result](images/databases_07_cross_service_integration_list_example_2.png){.thumbnail}
 
 Connect to your Dashboards instance and browse the dashboards:
 
@@ -182,16 +175,6 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/kafkaMirrorMaker
 >> >
-> M3 Aggregator
->> > [!api]
->> >
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3aggregator
->> >
-> M3db
->> > [!api]
->> >
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3db
->> >
 > MySQL
 >> > [!api]
 >> >
@@ -240,14 +223,6 @@ Get integration capabilities related to your Public Cloud Databases service:
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/capabilities/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/capabilities/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3db/{clusterId}/capabilities/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/mysql/{clusterId}/capabilities/integration
@@ -265,7 +240,7 @@ Get integration capabilities related to your Public Cloud Databases service:
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/caching/{clusterId}/capabilities/integration
 >> >
 
-![Get Integration Capabilities](images/databases_07_cross_service_integration-20220708142931159.png){.thumbnail}
+![Get Integration Capabilities](images/databases_07_cross_service_integration_api_capa_integration.png){.thumbnail}
 
 #### Store yours logs or metrics
 
@@ -294,14 +269,6 @@ For that, you need to create a new integration:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3db/{clusterId}/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/mysql/{clusterId}/integration
@@ -321,7 +288,7 @@ For that, you need to create a new integration:
 
 Fill in the form with the information corresponding to the type of integration chosen.
 
-![Create a new integration](images/databases_07_cross_service_integration-2022070814275082.png){.thumbnail}
+![Create a new integration](images/databases_07_cross_service_integration_api_post_integration.png){.thumbnail}
 
 The `destionationServiceId` and the `sourceServiceId` correspond to the destination cluster ID and to the source cluster ID.
 
@@ -333,7 +300,7 @@ For that, first create a Public Cloud Database for Dashboards via our Control Pa
 
 Once done, get the `GrafanaDashboard` integration capability related to the destination service:
 
-![Get Dashboards integration capabilitie](images/databases_07_cross_service_integration-20220708141900814.png){.thumbnail}
+![Get Dashboards integration capabilitie](images/databases_07_cross_service_integration_api_capa_integration.png){.thumbnail}
 
 Then create a second integration from your *Destination* service name:
 
@@ -358,14 +325,6 @@ Then create a second integration from your *Destination* service name:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3db/{clusterId}/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/mysql/{clusterId}/integration
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.it-it.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.it-it.md
index 0e300ce6a71..ba4a203333a 100644
--- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.it-it.md
+++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.it-it.md
@@ -1,7 +1,7 @@
 ---
 title: Public Cloud Databases - How to setup a service integration
 excerpt: Find out how to use Cross Service Integration for Public Cloud Databases engines
-updated: 2023-05-25
+updated: 2025-04-15
 ---
 
 ## Objective
@@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs
 
 The Cross Service Integrations for Logs and Metrics allow you for example:
 
-- To send Caching or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
+- To send Caching or MySQL metrics or Cassandra metrics in PostgreSQL.
 - To send PostgreSQL or MySQL metrics to OpenSearch.
 - To show metrics in Dashboards service.
 
@@ -49,18 +49,16 @@ For that you need:
 ### Integration matrix
 
 - All services support logs to opensearch & kafka_logs to kafka.
-- All services except m3db & m3agg support metrics to pg & metrics to m3db.
+- All services support metrics to pg.
 
 Other integrations:
 
-| source →<br>↓ destination | dashboards service	| m3db	| kafka |
-|:--|---|---|---|
-| pg | dashboard, datasource | | |
-| opensearch | datasource | | |
-| m3db | dashboard, datasource | | |
-| m3agg | | m3agg | |
-| kmm | | | kafka_mirrormaker |
-| kc | | | kafka_connect |
+| source →<br>↓ destination | dashboards service	| kafka |
+|:--|---|---|
+| pg | dashboard, datasource | |
+| opensearch | datasource | |
+| kmm | | kafka_mirrormaker |
+| kc | | kafka_connect |
 
 ## Instructions
 
@@ -81,11 +79,6 @@ Define the `Integration type`{.action} and the `Destination service`{.action}:
 > First create a Public Cloud Database for your *Destination* service via your Control Panel or API.
 >
 
-> [!primary]
->
-> If you want to store the metrics of your *postgresql* cluster to *m3db*, select `m3dbMetrics` as `Integration type`{.action} and `m3db` as `Destination service`{.action}, as shown below.
->
-
 ![Create integration](images/databases_07_cross_service_integration-20220708155848940.png){.thumbnail}
 
 Your first integration is ready:
@@ -182,16 +175,6 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/kafkaMirrorMaker
 >> >
-> M3 Aggregator
->> > [!api]
->> >
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3aggregator
->> >
-> M3db
->> > [!api]
->> >
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3db
->> >
 > MySQL
 >> > [!api]
 >> >
@@ -240,14 +223,6 @@ Get integration capabilities related to your Public Cloud Databases service:
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/capabilities/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/capabilities/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3db/{clusterId}/capabilities/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/mysql/{clusterId}/capabilities/integration
@@ -294,14 +269,6 @@ For that, you need to create a new integration:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3db/{clusterId}/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/mysql/{clusterId}/integration
@@ -358,14 +325,6 @@ Then create a second integration from your *Destination* service name:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3db/{clusterId}/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/mysql/{clusterId}/integration
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.pl-pl.md
index 8493784a940..928a67a59ff 100644
--- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.pl-pl.md
+++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.pl-pl.md
@@ -1,7 +1,7 @@
 ---
 title: Public Cloud Databases - How to setup a service integration
 excerpt: Find out how to use Cross Service Integration for Public Cloud Databases engines
-updated: 2023-05-25
+updated: 2025-04-15
 ---
 
 ## Objective
@@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs
 
 The Cross Service Integrations for Logs and Metrics allow you for example:
 
-- To send Caching or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
+- To send Caching or MySQL metrics or Cassandra metrics in PostgreSQL.
 - To send PostgreSQL or MySQL metrics to OpenSearch.
 - To show metrics in Dashboards service.
 
@@ -49,18 +49,16 @@ For that you need:
 ### Integration matrix
 
 - All services support logs to opensearch & kafka_logs to kafka.
-- All services except m3db & m3agg support metrics to pg & metrics to m3db.
+- All services support metrics to pg.
 
 Other integrations:
 
-| source →<br>↓ destination | dashboards service	| m3db	| kafka |
-|:--|---|---|---|
-| pg | dashboard, datasource | | |
-| opensearch | datasource | | |
-| m3db | dashboard, datasource | | |
-| m3agg | | m3agg | |
-| kmm | | | kafka_mirrormaker |
-| kc | | | kafka_connect |
+| source →<br>↓ destination | dashboards service	| kafka |
+|:--|---|---|
+| pg | dashboard, datasource | |
+| opensearch | datasource | |
+| kmm | | kafka_mirrormaker |
+| kc | | kafka_connect |
 
 ## Instructions
 
@@ -81,11 +79,6 @@ Define the `Integration type`{.action} and the `Destination service`{.action}:
 > First create a Public Cloud Database for your *Destination* service via your Control Panel or API.
 >
 
-> [!primary]
->
-> If you want to store the metrics of your *postgresql* cluster to *m3db*, select `m3dbMetrics` as `Integration type`{.action} and `m3db` as `Destination service`{.action}, as shown below.
->
-
 ![Create integration](images/databases_07_cross_service_integration-20220708155848940.png){.thumbnail}
 
 Your first integration is ready:
@@ -182,16 +175,6 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/kafkaMirrorMaker
 >> >
-> M3 Aggregator
->> > [!api]
->> >
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3aggregator
->> >
-> M3db
->> > [!api]
->> >
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3db
->> >
 > MySQL
 >> > [!api]
 >> >
@@ -240,14 +223,6 @@ Get integration capabilities related to your Public Cloud Databases service:
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/capabilities/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/capabilities/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3db/{clusterId}/capabilities/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/mysql/{clusterId}/capabilities/integration
@@ -294,14 +269,6 @@ For that, you need to create a new integration:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3db/{clusterId}/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/mysql/{clusterId}/integration
@@ -358,14 +325,6 @@ Then create a second integration from your *Destination* service name:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3db/{clusterId}/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/mysql/{clusterId}/integration
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.pt-pt.md
index 7c84fc50667..7bb00024197 100644
--- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.pt-pt.md
+++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/guide.pt-pt.md
@@ -1,7 +1,7 @@
 ---
 title: Public Cloud Databases - How to setup a service integration
 excerpt: Find out how to use Cross Service Integration for Public Cloud Databases engines
-updated: 2023-05-25
+updated: 2025-04-15
 ---
 
 ## Objective
@@ -28,7 +28,7 @@ Cross Service Integration allows you to expose your Public Cloud Databases Logs
 
 The Cross Service Integrations for Logs and Metrics allow you for example:
 
-- To send Caching or MySQL metrics or Cassandra metrics in M3db or PostgreSQL.
+- To send Caching or MySQL metrics or Cassandra metrics in PostgreSQL.
 - To send PostgreSQL or MySQL metrics to OpenSearch.
 - To show metrics in Dashboards service.
 
@@ -49,18 +49,16 @@ For that you need:
 ### Integration matrix
 
 - All services support logs to opensearch & kafka_logs to kafka.
-- All services except m3db & m3agg support metrics to pg & metrics to m3db.
+- All services support metrics to pg.
 
 Other integrations:
 
-| source →<br>↓ destination | dashboards service	| m3db	| kafka |
-|:--|---|---|---|
-| pg | dashboard, datasource | | |
-| opensearch | datasource | | |
-| m3db | dashboard, datasource | | |
-| m3agg | | m3agg | |
-| kmm | | | kafka_mirrormaker |
-| kc | | | kafka_connect |
+| source →<br>↓ destination | dashboards service	| kafka |
+|:--|---|---|
+| pg | dashboard, datasource | |
+| opensearch | datasource | |
+| kmm | | kafka_mirrormaker |
+| kc | | kafka_connect |
 
 ## Instructions
 
@@ -81,11 +79,6 @@ Define the `Integration type`{.action} and the `Destination service`{.action}:
 > First create a Public Cloud Database for your *Destination* service via your Control Panel or API.
 >
 
-> [!primary]
->
-> If you want to store the metrics of your *postgresql* cluster to *m3db*, select `m3dbMetrics` as `Integration type`{.action} and `m3db` as `Destination service`{.action}, as shown below.
->
-
 ![Create integration](images/databases_07_cross_service_integration-20220708155848940.png){.thumbnail}
 
 Your first integration is ready:
@@ -182,16 +175,6 @@ Open the following API call, paste your service ID into the `serviceName` input
 >> >
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/kafkaMirrorMaker
 >> >
-> M3 Aggregator
->> > [!api]
->> >
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3aggregator
->> >
-> M3db
->> > [!api]
->> >
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3db
->> >
 > MySQL
 >> > [!api]
 >> >
@@ -240,14 +223,6 @@ Get integration capabilities related to your Public Cloud Databases service:
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/capabilities/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/capabilities/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/m3db/{clusterId}/capabilities/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud GET /cloud/project/{serviceName}/database/mysql/{clusterId}/capabilities/integration
@@ -294,14 +269,6 @@ For that, you need to create a new integration:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3db/{clusterId}/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/mysql/{clusterId}/integration
@@ -358,14 +325,6 @@ Then create a second integration from your *Destination* service name:
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/kafkaMirrorMaker/{clusterId}/integration
 >> >
-> M3 Aggregator
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3aggregator/{clusterId}/integration
->> >
-> M3db
->> > [!api]
->> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/m3db/{clusterId}/integration
->> >
 > MySQL
 >> > [!api]
 >> > @api {v1} /cloud POST /cloud/project/{serviceName}/database/mysql/{clusterId}/integration
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration-20220708091945946.png b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration-20220708091945946.png
deleted file mode 100644
index 667b735ac68..00000000000
Binary files a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration-20220708091945946.png and /dev/null differ
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration-20220708104820460.png b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration-20220708104820460.png
deleted file mode 100644
index db71aa2aa9e..00000000000
Binary files a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration-20220708104820460.png and /dev/null differ
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration-20220708141900814.png b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration-20220708141900814.png
deleted file mode 100644
index 82096ff7e86..00000000000
Binary files a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration-20220708141900814.png and /dev/null differ
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration-2022070814275082.png b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration-2022070814275082.png
deleted file mode 100644
index 5549c64935d..00000000000
Binary files a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration-2022070814275082.png and /dev/null differ
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration-20220708142931159.png b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration-20220708142931159.png
deleted file mode 100644
index 5bc58ae84f5..00000000000
Binary files a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration-20220708142931159.png and /dev/null differ
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration-20220708155848940.png b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration-20220708155848940.png
deleted file mode 100644
index d92d6306865..00000000000
Binary files a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration-20220708155848940.png and /dev/null differ
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration-20220708160028574.png b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration-20220708160028574.png
deleted file mode 100644
index 4ac468b74bd..00000000000
Binary files a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration-20220708160028574.png and /dev/null differ
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration-20220708160203565.png b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration-20220708160203565.png
deleted file mode 100644
index ccbc4e4630b..00000000000
Binary files a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration-20220708160203565.png and /dev/null differ
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration-20220708160400509.png b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration-20220708160400509.png
deleted file mode 100644
index 5795baa37c5..00000000000
Binary files a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration-20220708160400509.png and /dev/null differ
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration-20220708160441618.png b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration-20220708160441618.png
deleted file mode 100644
index aad014fb485..00000000000
Binary files a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration-20220708160441618.png and /dev/null differ
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration-20220719203753927.png b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration-20220719203753927.png
deleted file mode 100644
index ca2cbf37d59..00000000000
Binary files a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration-20220719203753927.png and /dev/null differ
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration_api.png b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration_api.png
new file mode 100644
index 00000000000..0606ebb830e
Binary files /dev/null and b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration_api.png differ
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration_api_capa_integration.png b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration_api_capa_integration.png
new file mode 100644
index 00000000000..aa435ea79cf
Binary files /dev/null and b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration_api_capa_integration.png differ
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration_api_post_integration.png b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration_api_post_integration.png
new file mode 100644
index 00000000000..cc7b8e438a9
Binary files /dev/null and b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration_api_post_integration.png differ
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration_api_post_integration_postregsql.png b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration_api_post_integration_postregsql.png
new file mode 100644
index 00000000000..d69a9a40772
Binary files /dev/null and b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration_api_post_integration_postregsql.png differ
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration_bad_practice.png b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration_bad_practice.png
new file mode 100644
index 00000000000..b204f1d254f
Binary files /dev/null and b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration_bad_practice.png differ
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration_best_practice.png b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration_best_practice.png
new file mode 100644
index 00000000000..868da2826de
Binary files /dev/null and b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration_best_practice.png differ
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration_creation.png b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration_creation.png
new file mode 100644
index 00000000000..6e450ce801a
Binary files /dev/null and b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration_creation.png differ
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration_creation_grafana.png b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration_creation_grafana.png
new file mode 100644
index 00000000000..76c6401fe1e
Binary files /dev/null and b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration_creation_grafana.png differ
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration_list_add.png b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration_list_add.png
new file mode 100644
index 00000000000..202eac19590
Binary files /dev/null and b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration_list_add.png differ
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration_list_example.png b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration_list_example.png
new file mode 100644
index 00000000000..b1756280a1e
Binary files /dev/null and b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration_list_example.png differ
diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration_list_example_2.png b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration_list_example_2.png
new file mode 100644
index 00000000000..4cf4c9a1921
Binary files /dev/null and b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/images/databases_07_cross_service_integration_list_example_2.png differ
diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.de-de.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.de-de.md
index 09b444748dd..7ff95ef0857 100644
--- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.de-de.md
+++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.de-de.md
@@ -33,8 +33,8 @@ When the disk usage increases even more and reaches a critical level (depending
 
 Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions:
 
-- `Caching` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
-- `Cassandra` and `M3DB` turn to read-only.
+- `Caching` does not store any user data on disk. Thus, it will not fill up the underlying disk storage.
+- `Cassandra` turns to read-only.
 - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write.
 - `MongoDB` forbids writes but allows deletes.
 
@@ -46,10 +46,6 @@ It may be that your usage simply requires more storage. You can then increase th
 
 It may be that you have reached the full disk situation because of a runaway application filling up your database, or that you are storing some old obsolete data. In these cases, stop whatever process which is unduly filling up your storage, then remove unwanted data.
 
-##### **M3DB**
-
-You can reclaim disk space by deleting a `M3DB` namespace.
-
 ##### **MongoDB**
 
 `MongoDB` refuses any query that inserts data, but allows queries deleting data. You can thus execute any `MongoDB` command that allows to reclaim disk space.
diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-asia.md
index 09b444748dd..7ff95ef0857 100644
--- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-asia.md
+++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-asia.md
@@ -33,8 +33,8 @@ When the disk usage increases even more and reaches a critical level (depending
 
 Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions:
 
-- `Caching` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
-- `Cassandra` and `M3DB` turn to read-only.
+- `Caching` does not store any user data on disk. Thus, it will not fill up the underlying disk storage.
+- `Cassandra` turns to read-only.
 - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write.
 - `MongoDB` forbids writes but allows deletes.
 
@@ -46,10 +46,6 @@ It may be that your usage simply requires more storage. You can then increase th
 
 It may be that you have reached the full disk situation because of a runaway application filling up your database, or that you are storing some old obsolete data. In these cases, stop whatever process which is unduly filling up your storage, then remove unwanted data.
 
-##### **M3DB**
-
-You can reclaim disk space by deleting a `M3DB` namespace.
-
 ##### **MongoDB**
 
 `MongoDB` refuses any query that inserts data, but allows queries deleting data. You can thus execute any `MongoDB` command that allows to reclaim disk space.
diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-au.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-au.md
index 09b444748dd..7ff95ef0857 100644
--- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-au.md
+++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-au.md
@@ -33,8 +33,8 @@ When the disk usage increases even more and reaches a critical level (depending
 
 Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions:
 
-- `Caching` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
-- `Cassandra` and `M3DB` turn to read-only.
+- `Caching` does not store any user data on disk. Thus, it will not fill up the underlying disk storage.
+- `Cassandra` turns to read-only.
 - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write.
 - `MongoDB` forbids writes but allows deletes.
 
@@ -46,10 +46,6 @@ It may be that your usage simply requires more storage. You can then increase th
 
 It may be that you have reached the full disk situation because of a runaway application filling up your database, or that you are storing some old obsolete data. In these cases, stop whatever process which is unduly filling up your storage, then remove unwanted data.
 
-##### **M3DB**
-
-You can reclaim disk space by deleting a `M3DB` namespace.
-
 ##### **MongoDB**
 
 `MongoDB` refuses any query that inserts data, but allows queries deleting data. You can thus execute any `MongoDB` command that allows to reclaim disk space.
diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-ca.md
index 09b444748dd..7ff95ef0857 100644
--- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-ca.md
+++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-ca.md
@@ -33,8 +33,8 @@ When the disk usage increases even more and reaches a critical level (depending
 
 Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions:
 
-- `Caching` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
-- `Cassandra` and `M3DB` turn to read-only.
+- `Caching` does not store any user data on disk. Thus, it will not fill up the underlying disk storage.
+- `Cassandra` turns to read-only.
 - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write.
 - `MongoDB` forbids writes but allows deletes.
 
@@ -46,10 +46,6 @@ It may be that your usage simply requires more storage. You can then increase th
 
 It may be that you have reached the full disk situation because of a runaway application filling up your database, or that you are storing some old obsolete data. In these cases, stop whatever process which is unduly filling up your storage, then remove unwanted data.
 
-##### **M3DB**
-
-You can reclaim disk space by deleting a `M3DB` namespace.
-
 ##### **MongoDB**
 
 `MongoDB` refuses any query that inserts data, but allows queries deleting data. You can thus execute any `MongoDB` command that allows to reclaim disk space.
diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-gb.md
index 09b444748dd..7ff95ef0857 100644
--- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-gb.md
+++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-gb.md
@@ -33,8 +33,8 @@ When the disk usage increases even more and reaches a critical level (depending
 
 Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions:
 
-- `Caching` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
-- `Cassandra` and `M3DB` turn to read-only.
+- `Caching` does not store any user data on disk. Thus, it will not fill up the underlying disk storage.
+- `Cassandra` turns to read-only.
 - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write.
 - `MongoDB` forbids writes but allows deletes.
 
@@ -46,10 +46,6 @@ It may be that your usage simply requires more storage. You can then increase th
 
 It may be that you have reached the full disk situation because of a runaway application filling up your database, or that you are storing some old obsolete data. In these cases, stop whatever process which is unduly filling up your storage, then remove unwanted data.
 
-##### **M3DB**
-
-You can reclaim disk space by deleting a `M3DB` namespace.
-
 ##### **MongoDB**
 
 `MongoDB` refuses any query that inserts data, but allows queries deleting data. You can thus execute any `MongoDB` command that allows to reclaim disk space.
diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-ie.md
index 09b444748dd..7ff95ef0857 100644
--- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-ie.md
+++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-ie.md
@@ -33,8 +33,8 @@ When the disk usage increases even more and reaches a critical level (depending
 
 Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions:
 
-- `Caching` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
-- `Cassandra` and `M3DB` turn to read-only.
+- `Caching` does not store any user data on disk. Thus, it will not fill up the underlying disk storage.
+- `Cassandra` turns to read-only.
 - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write.
 - `MongoDB` forbids writes but allows deletes.
 
@@ -46,10 +46,6 @@ It may be that your usage simply requires more storage. You can then increase th
 
 It may be that you have reached the full disk situation because of a runaway application filling up your database, or that you are storing some old obsolete data. In these cases, stop whatever process which is unduly filling up your storage, then remove unwanted data.
 
-##### **M3DB**
-
-You can reclaim disk space by deleting a `M3DB` namespace.
-
 ##### **MongoDB**
 
 `MongoDB` refuses any query that inserts data, but allows queries deleting data. You can thus execute any `MongoDB` command that allows to reclaim disk space.
diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-sg.md
index 09b444748dd..7ff95ef0857 100644
--- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-sg.md
+++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-sg.md
@@ -33,8 +33,8 @@ When the disk usage increases even more and reaches a critical level (depending
 
 Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions:
 
-- `Caching` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
-- `Cassandra` and `M3DB` turn to read-only.
+- `Caching` does not store any user data on disk. Thus, it will not fill up the underlying disk storage.
+- `Cassandra` turns to read-only.
 - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write.
 - `MongoDB` forbids writes but allows deletes.
 
@@ -46,10 +46,6 @@ It may be that your usage simply requires more storage. You can then increase th
 
 It may be that you have reached the full disk situation because of a runaway application filling up your database, or that you are storing some old obsolete data. In these cases, stop whatever process which is unduly filling up your storage, then remove unwanted data.
 
-##### **M3DB**
-
-You can reclaim disk space by deleting a `M3DB` namespace.
-
 ##### **MongoDB**
 
 `MongoDB` refuses any query that inserts data, but allows queries deleting data. You can thus execute any `MongoDB` command that allows to reclaim disk space.
diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-us.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-us.md
index 09b444748dd..7ff95ef0857 100644
--- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-us.md
+++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.en-us.md
@@ -33,8 +33,8 @@ When the disk usage increases even more and reaches a critical level (depending
 
 Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions:
 
-- `Caching` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
-- `Cassandra` and `M3DB` turn to read-only.
+- `Caching` does not store any user data on disk. Thus, it will not fill up the underlying disk storage.
+- `Cassandra` turns to read-only.
 - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write.
 - `MongoDB` forbids writes but allows deletes.
 
@@ -46,10 +46,6 @@ It may be that your usage simply requires more storage. You can then increase th
 
 It may be that you have reached the full disk situation because of a runaway application filling up your database, or that you are storing some old obsolete data. In these cases, stop whatever process which is unduly filling up your storage, then remove unwanted data.
 
-##### **M3DB**
-
-You can reclaim disk space by deleting a `M3DB` namespace.
-
 ##### **MongoDB**
 
 `MongoDB` refuses any query that inserts data, but allows queries deleting data. You can thus execute any `MongoDB` command that allows to reclaim disk space.
diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.es-es.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.es-es.md
index 09b444748dd..7ff95ef0857 100644
--- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.es-es.md
+++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.es-es.md
@@ -33,8 +33,8 @@ When the disk usage increases even more and reaches a critical level (depending
 
 Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions:
 
-- `Caching` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
-- `Cassandra` and `M3DB` turn to read-only.
+- `Caching` does not store any user data on disk. Thus, it will not fill up the underlying disk storage.
+- `Cassandra` turns to read-only.
 - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write.
 - `MongoDB` forbids writes but allows deletes.
 
@@ -46,10 +46,6 @@ It may be that your usage simply requires more storage. You can then increase th
 
 It may be that you have reached the full disk situation because of a runaway application filling up your database, or that you are storing some old obsolete data. In these cases, stop whatever process which is unduly filling up your storage, then remove unwanted data.
 
-##### **M3DB**
-
-You can reclaim disk space by deleting a `M3DB` namespace.
-
 ##### **MongoDB**
 
 `MongoDB` refuses any query that inserts data, but allows queries deleting data. You can thus execute any `MongoDB` command that allows to reclaim disk space.
diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.es-us.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.es-us.md
index 09b444748dd..7ff95ef0857 100644
--- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.es-us.md
+++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.es-us.md
@@ -33,8 +33,8 @@ When the disk usage increases even more and reaches a critical level (depending
 
 Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions:
 
-- `Caching` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
-- `Cassandra` and `M3DB` turn to read-only.
+- `Caching` does not store any user data on disk. Thus, it will not fill up the underlying disk storage.
+- `Cassandra` turns to read-only.
 - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write.
 - `MongoDB` forbids writes but allows deletes.
 
@@ -46,10 +46,6 @@ It may be that your usage simply requires more storage. You can then increase th
 
 It may be that you have reached the full disk situation because of a runaway application filling up your database, or that you are storing some old obsolete data. In these cases, stop whatever process which is unduly filling up your storage, then remove unwanted data.
 
-##### **M3DB**
-
-You can reclaim disk space by deleting a `M3DB` namespace.
-
 ##### **MongoDB**
 
 `MongoDB` refuses any query that inserts data, but allows queries deleting data. You can thus execute any `MongoDB` command that allows to reclaim disk space.
diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.fr-ca.md
index 288c94fdc7f..7765cfb65ed 100644
--- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.fr-ca.md
+++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.fr-ca.md
@@ -33,8 +33,8 @@ When the disk usage increases even more and reaches a critical level (depending
 
 Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions:
 
-- `Caching` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
-- `Cassandra` and `M3DB` turn to read-only.
+- `Caching` does not store any user data on disk. Thus, it will not fill up the underlying disk storage.
+- `Cassandra` turns to read-only.
 - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write.
 - `MongoDB` forbids writes but allows deletes.
 
@@ -46,10 +46,6 @@ It may be that your usage simply requires more storage. You can then increase th
 
 It may be that you have reached the full disk situation because of a runaway application filling up your database, or that you are storing some old obsolete data. In these cases, stop whatever process which is unduly filling up your storage, then remove unwanted data.
 
-##### **M3DB**
-
-You can reclaim disk space by deleting a `M3DB` namespace.
-
 ##### **MongoDB**
 
 `MongoDB` refuses any query that inserts data, but allows queries deleting data. You can thus execute any `MongoDB` command that allows to reclaim disk space.
diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.fr-fr.md
index 288c94fdc7f..7765cfb65ed 100644
--- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.fr-fr.md
+++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.fr-fr.md
@@ -33,8 +33,8 @@ When the disk usage increases even more and reaches a critical level (depending
 
 Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions:
 
-- `Caching` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
-- `Cassandra` and `M3DB` turn to read-only.
+- `Caching` does not store any user data on disk. Thus, it will not fill up the underlying disk storage.
+- `Cassandra` turns to read-only.
 - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write.
 - `MongoDB` forbids writes but allows deletes.
 
@@ -46,10 +46,6 @@ It may be that your usage simply requires more storage. You can then increase th
 
 It may be that you have reached the full disk situation because of a runaway application filling up your database, or that you are storing some old obsolete data. In these cases, stop whatever process which is unduly filling up your storage, then remove unwanted data.
 
-##### **M3DB**
-
-You can reclaim disk space by deleting a `M3DB` namespace.
-
 ##### **MongoDB**
 
 `MongoDB` refuses any query that inserts data, but allows queries deleting data. You can thus execute any `MongoDB` command that allows to reclaim disk space.
diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.it-it.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.it-it.md
index 09b444748dd..7ff95ef0857 100644
--- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.it-it.md
+++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.it-it.md
@@ -33,8 +33,8 @@ When the disk usage increases even more and reaches a critical level (depending
 
 Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions:
 
-- `Caching` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
-- `Cassandra` and `M3DB` turn to read-only.
+- `Caching` does not store any user data on disk. Thus, it will not fill up the underlying disk storage.
+- `Cassandra` turns to read-only.
 - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write.
 - `MongoDB` forbids writes but allows deletes.
 
@@ -46,10 +46,6 @@ It may be that your usage simply requires more storage. You can then increase th
 
 It may be that you have reached the full disk situation because of a runaway application filling up your database, or that you are storing some old obsolete data. In these cases, stop whatever process which is unduly filling up your storage, then remove unwanted data.
 
-##### **M3DB**
-
-You can reclaim disk space by deleting a `M3DB` namespace.
-
 ##### **MongoDB**
 
 `MongoDB` refuses any query that inserts data, but allows queries deleting data. You can thus execute any `MongoDB` command that allows to reclaim disk space.
diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.pl-pl.md
index 09b444748dd..7ff95ef0857 100644
--- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.pl-pl.md
+++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.pl-pl.md
@@ -33,8 +33,8 @@ When the disk usage increases even more and reaches a critical level (depending
 
 Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions:
 
-- `Caching` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
-- `Cassandra` and `M3DB` turn to read-only.
+- `Caching` does not store any user data on disk. Thus, it will not fill up the underlying disk storage.
+- `Cassandra` turns to read-only.
 - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write.
 - `MongoDB` forbids writes but allows deletes.
 
@@ -46,10 +46,6 @@ It may be that your usage simply requires more storage. You can then increase th
 
 It may be that you have reached the full disk situation because of a runaway application filling up your database, or that you are storing some old obsolete data. In these cases, stop whatever process which is unduly filling up your storage, then remove unwanted data.
 
-##### **M3DB**
-
-You can reclaim disk space by deleting a `M3DB` namespace.
-
 ##### **MongoDB**
 
 `MongoDB` refuses any query that inserts data, but allows queries deleting data. You can thus execute any `MongoDB` command that allows to reclaim disk space.
diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.pt-pt.md
index 09b444748dd..7ff95ef0857 100644
--- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.pt-pt.md
+++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/guide.pt-pt.md
@@ -33,8 +33,8 @@ When the disk usage increases even more and reaches a critical level (depending
 
 Different engines react in different ways, thus Public Cloud Databases services react differently when facing disk full conditions:
 
-- `Caching` and `M3 Aggregator` do not store any user data on disk. Thus they will not fill up the underlying disk storage.
-- `Cassandra` and `M3DB` turn to read-only.
+- `Caching` does not store any user data on disk. Thus, it will not fill up the underlying disk storage.
+- `Cassandra` turns to read-only.
 - `MySQL` and `PostgreSQL` turn to read-only with a way to temporarily revert to read-write.
 - `MongoDB` forbids writes but allows deletes.
 
@@ -46,10 +46,6 @@ It may be that your usage simply requires more storage. You can then increase th
 
 It may be that you have reached the full disk situation because of a runaway application filling up your database, or that you are storing some old obsolete data. In these cases, stop whatever process which is unduly filling up your storage, then remove unwanted data.
 
-##### **M3DB**
-
-You can reclaim disk space by deleting a `M3DB` namespace.
-
 ##### **MongoDB**
 
 `MongoDB` refuses any query that inserts data, but allows queries deleting data. You can thus execute any `MongoDB` command that allows to reclaim disk space.
diff --git a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.de-de.md b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.de-de.md
index aad84df8dd4..44129779d24 100644
--- a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.de-de.md
+++ b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.de-de.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, or Cassandra cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-asia.md
index 68cc3427814..19e27619314 100644
--- a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-asia.md
+++ b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-asia.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, or Cassandra cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-au.md b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-au.md
index 14d6e399a78..713768fb5de 100644
--- a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-au.md
+++ b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-au.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, or Cassandra cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-ca.md
index a8a9b3e7df9..2aa66207ca4 100644
--- a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-ca.md
+++ b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-ca.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, or Cassandra cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-gb.md
index 39b4adfc7f2..1b67d7f4fce 100644
--- a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-gb.md
+++ b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-gb.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, or Cassandra cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-ie.md
index 4ae7f859fd2..ecfb75480e1 100644
--- a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-ie.md
+++ b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-ie.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, or Cassandra cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-sg.md
index 4be0ffc0715..357997ada56 100644
--- a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-sg.md
+++ b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-sg.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, or Cassandra cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-us.md b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-us.md
index ea56e9a0ede..4a04ba5a2a9 100644
--- a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-us.md
+++ b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.en-us.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, or Cassandra cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.es-es.md b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.es-es.md
index 6afb4c75e6d..690ffecc56f 100644
--- a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.es-es.md
+++ b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.es-es.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, or Cassandra cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.es-us.md b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.es-us.md
index 3777e619c0f..3634a343a37 100644
--- a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.es-us.md
+++ b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.es-us.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, or Cassandra cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.fr-ca.md
index 1eac8ac585b..4c3e8ac0cc3 100644
--- a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.fr-ca.md
+++ b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.fr-ca.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, or Cassandra cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.fr-fr.md
index 355d770114e..6fd783cb073 100644
--- a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.fr-fr.md
+++ b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.fr-fr.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, or Cassandra cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.it-it.md b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.it-it.md
index ee21ae861f7..eaccb8d6193 100644
--- a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.it-it.md
+++ b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.it-it.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, or Cassandra cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.pl-pl.md
index 302ac7baec5..d2d933c4b5f 100644
--- a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.pl-pl.md
+++ b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.pl-pl.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, or Cassandra cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.pt-pt.md
index b554b761ea5..a1375ae9260 100644
--- a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.pt-pt.md
+++ b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/guide.pt-pt.md
@@ -18,7 +18,7 @@ This shared model can help relieve the customer’s operational burden.
 | C: Is consulted during the process |
 | I: Is informed of the results of the process |
 
-For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, Cassandra, or M3 cluster.
+For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Caching, Kafka, or Cassandra cluster.
 
 ### 1. Before subscription
 
diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.de-de.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.de-de.md
index e18ed100197..23853795275 100644
--- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.de-de.md
+++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.de-de.md
@@ -1,7 +1,7 @@
 ---
 title: Public Cloud Databases - Capabilities and Limitations (EN)
 excerpt: Discover the capabilities and limitations of Public Cloud Databases
-updated: 2024-06-12
+updated: 2025-04-15
 ---
 
 ## Public Cloud Databases
@@ -35,11 +35,6 @@ See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_
 Caching is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
 See our [Caching Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
 
-### M3db
-
-M3db is a fully managed distributed time series database. It's scalable and offers high-availability, which is ideal for your monitoring environment and time series applications.<br>
-See our [M3db Capabilities and limitations](/pages/public_cloud/public_cloud_databases/m3db_01_capabilities) guide.
-
 ### Cassandra
 
 Apache Cassandra is an open-source fully managed NoSQL database. It's highly fault-tolerant with asynchronous replication.<br>
@@ -47,15 +42,15 @@ See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_clou
 
 ## Feature Availability
 
-| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | M3db | Cassandra |
-|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|------------|-----------|
-| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Read-only nodes                                                                                              | ✓     | ✓          | ✓                |       |            |           |
-| Point in Time Recovery                                                                                       | ✓     | ✓          | ✓ <sup>(1)</sup> |       |            |           |
-| Database forking                                                                                             | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Private network connectivity (vRack)                                                                         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
+| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | Cassandra |
+|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|-----------|
+| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Read-only nodes                                                                                              | ✓     | ✓          | ✓                |       |           |
+| Point in Time Recovery                                                                                       | ✓     | ✓          | ✓ <sup>(1)</sup> |       |           |
+| Database forking                                                                                             | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Private network connectivity (vRack)                                                                         | ✓     | ✓          | ✓                | ✓     | ✓         |
 
 (1) depends on the plan
 
diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-asia.md
index e09cbfc7970..b8c81019274 100644
--- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-asia.md
+++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-asia.md
@@ -1,7 +1,7 @@
 ---
 title: Public Cloud Databases - Capabilities and Limitations
 excerpt: Discover the capabilities and limitations of Public Cloud Databases
-updated: 2024-06-12
+updated: 2025-04-15
 ---
 
 ## Public Cloud Databases
@@ -35,11 +35,6 @@ See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_
 Caching is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
 See our [Caching Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
 
-### M3db
-
-M3db is a fully managed distributed time series database. It's scalable and offers high-availability, which is ideal for your monitoring environment and time series applications.<br>
-See our [M3db Capabilities and limitations](/pages/public_cloud/public_cloud_databases/m3db_01_capabilities) guide.
-
 ### Cassandra
 
 Apache Cassandra is an open-source fully managed NoSQL database. It's highly fault-tolerant with asynchronous replication.<br>
@@ -47,15 +42,15 @@ See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_clou
 
 ## Feature Availability
 
-| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | M3db | Cassandra |
-|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|------------|-----------|
-| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Read-only nodes                                                                                              | ✓     | ✓          | ✓                |       |            |           |
-| Point in Time Recovery                                                                                       | ✓     | ✓          | ✓ <sup>(1)</sup> |       |            |           |
-| Database forking                                                                                             | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Private network connectivity (vRack)                                                                         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
+| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | Cassandra |
+|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|-----------|
+| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Read-only nodes                                                                                              | ✓     | ✓          | ✓                |       |           |
+| Point in Time Recovery                                                                                       | ✓     | ✓          | ✓ <sup>(1)</sup> |       |           |
+| Database forking                                                                                             | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Private network connectivity (vRack)                                                                         | ✓     | ✓          | ✓                | ✓     | ✓         |
 
 (1) depends on the plan
 
diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-au.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-au.md
index e09cbfc7970..b8c81019274 100644
--- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-au.md
+++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-au.md
@@ -1,7 +1,7 @@
 ---
 title: Public Cloud Databases - Capabilities and Limitations
 excerpt: Discover the capabilities and limitations of Public Cloud Databases
-updated: 2024-06-12
+updated: 2025-04-15
 ---
 
 ## Public Cloud Databases
@@ -35,11 +35,6 @@ See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_
 Caching is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
 See our [Caching Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
 
-### M3db
-
-M3db is a fully managed distributed time series database. It's scalable and offers high-availability, which is ideal for your monitoring environment and time series applications.<br>
-See our [M3db Capabilities and limitations](/pages/public_cloud/public_cloud_databases/m3db_01_capabilities) guide.
-
 ### Cassandra
 
 Apache Cassandra is an open-source fully managed NoSQL database. It's highly fault-tolerant with asynchronous replication.<br>
@@ -47,15 +42,15 @@ See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_clou
 
 ## Feature Availability
 
-| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | M3db | Cassandra |
-|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|------------|-----------|
-| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Read-only nodes                                                                                              | ✓     | ✓          | ✓                |       |            |           |
-| Point in Time Recovery                                                                                       | ✓     | ✓          | ✓ <sup>(1)</sup> |       |            |           |
-| Database forking                                                                                             | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Private network connectivity (vRack)                                                                         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
+| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | Cassandra |
+|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|-----------|
+| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Read-only nodes                                                                                              | ✓     | ✓          | ✓                |       |           |
+| Point in Time Recovery                                                                                       | ✓     | ✓          | ✓ <sup>(1)</sup> |       |           |
+| Database forking                                                                                             | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Private network connectivity (vRack)                                                                         | ✓     | ✓          | ✓                | ✓     | ✓         |
 
 (1) depends on the plan
 
diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-ca.md
index e09cbfc7970..b8c81019274 100644
--- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-ca.md
+++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-ca.md
@@ -1,7 +1,7 @@
 ---
 title: Public Cloud Databases - Capabilities and Limitations
 excerpt: Discover the capabilities and limitations of Public Cloud Databases
-updated: 2024-06-12
+updated: 2025-04-15
 ---
 
 ## Public Cloud Databases
@@ -35,11 +35,6 @@ See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_
 Caching is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
 See our [Caching Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
 
-### M3db
-
-M3db is a fully managed distributed time series database. It's scalable and offers high-availability, which is ideal for your monitoring environment and time series applications.<br>
-See our [M3db Capabilities and limitations](/pages/public_cloud/public_cloud_databases/m3db_01_capabilities) guide.
-
 ### Cassandra
 
 Apache Cassandra is an open-source fully managed NoSQL database. It's highly fault-tolerant with asynchronous replication.<br>
@@ -47,15 +42,15 @@ See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_clou
 
 ## Feature Availability
 
-| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | M3db | Cassandra |
-|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|------------|-----------|
-| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Read-only nodes                                                                                              | ✓     | ✓          | ✓                |       |            |           |
-| Point in Time Recovery                                                                                       | ✓     | ✓          | ✓ <sup>(1)</sup> |       |            |           |
-| Database forking                                                                                             | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Private network connectivity (vRack)                                                                         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
+| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | Cassandra |
+|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|-----------|
+| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Read-only nodes                                                                                              | ✓     | ✓          | ✓                |       |           |
+| Point in Time Recovery                                                                                       | ✓     | ✓          | ✓ <sup>(1)</sup> |       |           |
+| Database forking                                                                                             | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Private network connectivity (vRack)                                                                         | ✓     | ✓          | ✓                | ✓     | ✓         |
 
 (1) depends on the plan
 
diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-gb.md
index e09cbfc7970..b8c81019274 100644
--- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-gb.md
+++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-gb.md
@@ -1,7 +1,7 @@
 ---
 title: Public Cloud Databases - Capabilities and Limitations
 excerpt: Discover the capabilities and limitations of Public Cloud Databases
-updated: 2024-06-12
+updated: 2025-04-15
 ---
 
 ## Public Cloud Databases
@@ -35,11 +35,6 @@ See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_
 Caching is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
 See our [Caching Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
 
-### M3db
-
-M3db is a fully managed distributed time series database. It's scalable and offers high-availability, which is ideal for your monitoring environment and time series applications.<br>
-See our [M3db Capabilities and limitations](/pages/public_cloud/public_cloud_databases/m3db_01_capabilities) guide.
-
 ### Cassandra
 
 Apache Cassandra is an open-source fully managed NoSQL database. It's highly fault-tolerant with asynchronous replication.<br>
@@ -47,15 +42,15 @@ See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_clou
 
 ## Feature Availability
 
-| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | M3db | Cassandra |
-|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|------------|-----------|
-| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Read-only nodes                                                                                              | ✓     | ✓          | ✓                |       |            |           |
-| Point in Time Recovery                                                                                       | ✓     | ✓          | ✓ <sup>(1)</sup> |       |            |           |
-| Database forking                                                                                             | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Private network connectivity (vRack)                                                                         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
+| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | Cassandra |
+|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|-----------|
+| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Read-only nodes                                                                                              | ✓     | ✓          | ✓                |       |           |
+| Point in Time Recovery                                                                                       | ✓     | ✓          | ✓ <sup>(1)</sup> |       |           |
+| Database forking                                                                                             | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Private network connectivity (vRack)                                                                         | ✓     | ✓          | ✓                | ✓     | ✓         |
 
 (1) depends on the plan
 
diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-ie.md
index e09cbfc7970..b8c81019274 100644
--- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-ie.md
+++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-ie.md
@@ -1,7 +1,7 @@
 ---
 title: Public Cloud Databases - Capabilities and Limitations
 excerpt: Discover the capabilities and limitations of Public Cloud Databases
-updated: 2024-06-12
+updated: 2025-04-15
 ---
 
 ## Public Cloud Databases
@@ -35,11 +35,6 @@ See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_
 Caching is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
 See our [Caching Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
 
-### M3db
-
-M3db is a fully managed distributed time series database. It's scalable and offers high-availability, which is ideal for your monitoring environment and time series applications.<br>
-See our [M3db Capabilities and limitations](/pages/public_cloud/public_cloud_databases/m3db_01_capabilities) guide.
-
 ### Cassandra
 
 Apache Cassandra is an open-source fully managed NoSQL database. It's highly fault-tolerant with asynchronous replication.<br>
@@ -47,15 +42,15 @@ See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_clou
 
 ## Feature Availability
 
-| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | M3db | Cassandra |
-|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|------------|-----------|
-| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Read-only nodes                                                                                              | ✓     | ✓          | ✓                |       |            |           |
-| Point in Time Recovery                                                                                       | ✓     | ✓          | ✓ <sup>(1)</sup> |       |            |           |
-| Database forking                                                                                             | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Private network connectivity (vRack)                                                                         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
+| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | Cassandra |
+|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|-----------|
+| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Read-only nodes                                                                                              | ✓     | ✓          | ✓                |       |           |
+| Point in Time Recovery                                                                                       | ✓     | ✓          | ✓ <sup>(1)</sup> |       |           |
+| Database forking                                                                                             | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Private network connectivity (vRack)                                                                         | ✓     | ✓          | ✓                | ✓     | ✓         |
 
 (1) depends on the plan
 
diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-sg.md
index e09cbfc7970..b8c81019274 100644
--- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-sg.md
+++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-sg.md
@@ -1,7 +1,7 @@
 ---
 title: Public Cloud Databases - Capabilities and Limitations
 excerpt: Discover the capabilities and limitations of Public Cloud Databases
-updated: 2024-06-12
+updated: 2025-04-15
 ---
 
 ## Public Cloud Databases
@@ -35,11 +35,6 @@ See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_
 Caching is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
 See our [Caching Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
 
-### M3db
-
-M3db is a fully managed distributed time series database. It's scalable and offers high-availability, which is ideal for your monitoring environment and time series applications.<br>
-See our [M3db Capabilities and limitations](/pages/public_cloud/public_cloud_databases/m3db_01_capabilities) guide.
-
 ### Cassandra
 
 Apache Cassandra is an open-source fully managed NoSQL database. It's highly fault-tolerant with asynchronous replication.<br>
@@ -47,15 +42,15 @@ See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_clou
 
 ## Feature Availability
 
-| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | M3db | Cassandra |
-|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|------------|-----------|
-| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Read-only nodes                                                                                              | ✓     | ✓          | ✓                |       |            |           |
-| Point in Time Recovery                                                                                       | ✓     | ✓          | ✓ <sup>(1)</sup> |       |            |           |
-| Database forking                                                                                             | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Private network connectivity (vRack)                                                                         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
+| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | Cassandra |
+|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|-----------|
+| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Read-only nodes                                                                                              | ✓     | ✓          | ✓                |       |           |
+| Point in Time Recovery                                                                                       | ✓     | ✓          | ✓ <sup>(1)</sup> |       |           |
+| Database forking                                                                                             | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Private network connectivity (vRack)                                                                         | ✓     | ✓          | ✓                | ✓     | ✓         |
 
 (1) depends on the plan
 
diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-us.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-us.md
index e09cbfc7970..b8c81019274 100644
--- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-us.md
+++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.en-us.md
@@ -1,7 +1,7 @@
 ---
 title: Public Cloud Databases - Capabilities and Limitations
 excerpt: Discover the capabilities and limitations of Public Cloud Databases
-updated: 2024-06-12
+updated: 2025-04-15
 ---
 
 ## Public Cloud Databases
@@ -35,11 +35,6 @@ See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_
 Caching is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
 See our [Caching Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
 
-### M3db
-
-M3db is a fully managed distributed time series database. It's scalable and offers high-availability, which is ideal for your monitoring environment and time series applications.<br>
-See our [M3db Capabilities and limitations](/pages/public_cloud/public_cloud_databases/m3db_01_capabilities) guide.
-
 ### Cassandra
 
 Apache Cassandra is an open-source fully managed NoSQL database. It's highly fault-tolerant with asynchronous replication.<br>
@@ -47,15 +42,15 @@ See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_clou
 
 ## Feature Availability
 
-| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | M3db | Cassandra |
-|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|------------|-----------|
-| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Read-only nodes                                                                                              | ✓     | ✓          | ✓                |       |            |           |
-| Point in Time Recovery                                                                                       | ✓     | ✓          | ✓ <sup>(1)</sup> |       |            |           |
-| Database forking                                                                                             | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Private network connectivity (vRack)                                                                         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
+| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | Cassandra |
+|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|-----------|
+| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Read-only nodes                                                                                              | ✓     | ✓          | ✓                |       |           |
+| Point in Time Recovery                                                                                       | ✓     | ✓          | ✓ <sup>(1)</sup> |       |           |
+| Database forking                                                                                             | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Private network connectivity (vRack)                                                                         | ✓     | ✓          | ✓                | ✓     | ✓         |
 
 (1) depends on the plan
 
diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.es-es.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.es-es.md
index e18ed100197..23853795275 100644
--- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.es-es.md
+++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.es-es.md
@@ -1,7 +1,7 @@
 ---
 title: Public Cloud Databases - Capabilities and Limitations (EN)
 excerpt: Discover the capabilities and limitations of Public Cloud Databases
-updated: 2024-06-12
+updated: 2025-04-15
 ---
 
 ## Public Cloud Databases
@@ -35,11 +35,6 @@ See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_
 Caching is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
 See our [Caching Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
 
-### M3db
-
-M3db is a fully managed distributed time series database. It's scalable and offers high-availability, which is ideal for your monitoring environment and time series applications.<br>
-See our [M3db Capabilities and limitations](/pages/public_cloud/public_cloud_databases/m3db_01_capabilities) guide.
-
 ### Cassandra
 
 Apache Cassandra is an open-source fully managed NoSQL database. It's highly fault-tolerant with asynchronous replication.<br>
@@ -47,15 +42,15 @@ See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_clou
 
 ## Feature Availability
 
-| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | M3db | Cassandra |
-|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|------------|-----------|
-| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Read-only nodes                                                                                              | ✓     | ✓          | ✓                |       |            |           |
-| Point in Time Recovery                                                                                       | ✓     | ✓          | ✓ <sup>(1)</sup> |       |            |           |
-| Database forking                                                                                             | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Private network connectivity (vRack)                                                                         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
+| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | Cassandra |
+|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|-----------|
+| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Read-only nodes                                                                                              | ✓     | ✓          | ✓                |       |           |
+| Point in Time Recovery                                                                                       | ✓     | ✓          | ✓ <sup>(1)</sup> |       |           |
+| Database forking                                                                                             | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Private network connectivity (vRack)                                                                         | ✓     | ✓          | ✓                | ✓     | ✓         |
 
 (1) depends on the plan
 
diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.es-us.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.es-us.md
index e18ed100197..23853795275 100644
--- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.es-us.md
+++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.es-us.md
@@ -1,7 +1,7 @@
 ---
 title: Public Cloud Databases - Capabilities and Limitations (EN)
 excerpt: Discover the capabilities and limitations of Public Cloud Databases
-updated: 2024-06-12
+updated: 2025-04-15
 ---
 
 ## Public Cloud Databases
@@ -35,11 +35,6 @@ See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_
 Caching is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
 See our [Caching Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
 
-### M3db
-
-M3db is a fully managed distributed time series database. It's scalable and offers high-availability, which is ideal for your monitoring environment and time series applications.<br>
-See our [M3db Capabilities and limitations](/pages/public_cloud/public_cloud_databases/m3db_01_capabilities) guide.
-
 ### Cassandra
 
 Apache Cassandra is an open-source fully managed NoSQL database. It's highly fault-tolerant with asynchronous replication.<br>
@@ -47,15 +42,15 @@ See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_clou
 
 ## Feature Availability
 
-| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | M3db | Cassandra |
-|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|------------|-----------|
-| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Read-only nodes                                                                                              | ✓     | ✓          | ✓                |       |            |           |
-| Point in Time Recovery                                                                                       | ✓     | ✓          | ✓ <sup>(1)</sup> |       |            |           |
-| Database forking                                                                                             | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Private network connectivity (vRack)                                                                         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
+| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | Cassandra |
+|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|-----------|
+| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Read-only nodes                                                                                              | ✓     | ✓          | ✓                |       |           |
+| Point in Time Recovery                                                                                       | ✓     | ✓          | ✓ <sup>(1)</sup> |       |           |
+| Database forking                                                                                             | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Private network connectivity (vRack)                                                                         | ✓     | ✓          | ✓                | ✓     | ✓         |
 
 (1) depends on the plan
 
diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.fr-ca.md
index 99b04fa14bc..80e635ec6d1 100644
--- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.fr-ca.md
+++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.fr-ca.md
@@ -1,7 +1,7 @@
 ---
 title: Public Cloud Databases - Capacités et Limitations (EN)
 excerpt: Discover the capabilities and limitations of Public Cloud Databases
-updated: 2024-06-12
+updated: 2025-04-15
 ---
 
 ## Public Cloud Databases
@@ -35,11 +35,6 @@ See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_
 Caching is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
 See our [Caching Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
 
-### M3db
-
-M3db is a fully managed distributed time series database. It's scalable and offers high-availability, which is ideal for your monitoring environment and time series applications.<br>
-See our [M3db Capabilities and limitations](/pages/public_cloud/public_cloud_databases/m3db_01_capabilities) guide.
-
 ### Cassandra
 
 Apache Cassandra is an open-source fully managed NoSQL database. It's highly fault-tolerant with asynchronous replication.<br>
@@ -47,15 +42,15 @@ See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_clou
 
 ## Feature Availability
 
-| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | M3db | Cassandra |
-|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|------------|-----------|
-| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Read-only nodes                                                                                              | ✓     | ✓          | ✓                |       |            |           |
-| Point in Time Recovery                                                                                       | ✓     | ✓          | ✓ <sup>(1)</sup> |       |            |           |
-| Database forking                                                                                             | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Private network connectivity (vRack)                                                                         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
+| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | Cassandra |
+|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|-----------|
+| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Read-only nodes                                                                                              | ✓     | ✓          | ✓                |       |           |
+| Point in Time Recovery                                                                                       | ✓     | ✓          | ✓ <sup>(1)</sup> |       |           |
+| Database forking                                                                                             | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Private network connectivity (vRack)                                                                         | ✓     | ✓          | ✓                | ✓     | ✓         |
 
 (1) depends on the plan
 
diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.fr-fr.md
index 99b04fa14bc..80e635ec6d1 100644
--- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.fr-fr.md
+++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.fr-fr.md
@@ -1,7 +1,7 @@
 ---
 title: Public Cloud Databases - Capacités et Limitations (EN)
 excerpt: Discover the capabilities and limitations of Public Cloud Databases
-updated: 2024-06-12
+updated: 2025-04-15
 ---
 
 ## Public Cloud Databases
@@ -35,11 +35,6 @@ See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_
 Caching is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
 See our [Caching Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
 
-### M3db
-
-M3db is a fully managed distributed time series database. It's scalable and offers high-availability, which is ideal for your monitoring environment and time series applications.<br>
-See our [M3db Capabilities and limitations](/pages/public_cloud/public_cloud_databases/m3db_01_capabilities) guide.
-
 ### Cassandra
 
 Apache Cassandra is an open-source fully managed NoSQL database. It's highly fault-tolerant with asynchronous replication.<br>
@@ -47,15 +42,15 @@ See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_clou
 
 ## Feature Availability
 
-| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | M3db | Cassandra |
-|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|------------|-----------|
-| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Read-only nodes                                                                                              | ✓     | ✓          | ✓                |       |            |           |
-| Point in Time Recovery                                                                                       | ✓     | ✓          | ✓ <sup>(1)</sup> |       |            |           |
-| Database forking                                                                                             | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Private network connectivity (vRack)                                                                         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
+| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | Cassandra |
+|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|-----------|
+| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Read-only nodes                                                                                              | ✓     | ✓          | ✓                |       |           |
+| Point in Time Recovery                                                                                       | ✓     | ✓          | ✓ <sup>(1)</sup> |       |           |
+| Database forking                                                                                             | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Private network connectivity (vRack)                                                                         | ✓     | ✓          | ✓                | ✓     | ✓         |
 
 (1) depends on the plan
 
diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.it-it.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.it-it.md
index e18ed100197..23853795275 100644
--- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.it-it.md
+++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.it-it.md
@@ -1,7 +1,7 @@
 ---
 title: Public Cloud Databases - Capabilities and Limitations (EN)
 excerpt: Discover the capabilities and limitations of Public Cloud Databases
-updated: 2024-06-12
+updated: 2025-04-15
 ---
 
 ## Public Cloud Databases
@@ -35,11 +35,6 @@ See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_
 Caching is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
 See our [Caching Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
 
-### M3db
-
-M3db is a fully managed distributed time series database. It's scalable and offers high-availability, which is ideal for your monitoring environment and time series applications.<br>
-See our [M3db Capabilities and limitations](/pages/public_cloud/public_cloud_databases/m3db_01_capabilities) guide.
-
 ### Cassandra
 
 Apache Cassandra is an open-source fully managed NoSQL database. It's highly fault-tolerant with asynchronous replication.<br>
@@ -47,15 +42,15 @@ See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_clou
 
 ## Feature Availability
 
-| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | M3db | Cassandra |
-|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|------------|-----------|
-| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Read-only nodes                                                                                              | ✓     | ✓          | ✓                |       |            |           |
-| Point in Time Recovery                                                                                       | ✓     | ✓          | ✓ <sup>(1)</sup> |       |            |           |
-| Database forking                                                                                             | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Private network connectivity (vRack)                                                                         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
+| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | Cassandra |
+|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|-----------|
+| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Read-only nodes                                                                                              | ✓     | ✓          | ✓                |       |           |
+| Point in Time Recovery                                                                                       | ✓     | ✓          | ✓ <sup>(1)</sup> |       |           |
+| Database forking                                                                                             | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Private network connectivity (vRack)                                                                         | ✓     | ✓          | ✓                | ✓     | ✓         |
 
 (1) depends on the plan
 
diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.pl-pl.md
index e18ed100197..23853795275 100644
--- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.pl-pl.md
+++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.pl-pl.md
@@ -1,7 +1,7 @@
 ---
 title: Public Cloud Databases - Capabilities and Limitations (EN)
 excerpt: Discover the capabilities and limitations of Public Cloud Databases
-updated: 2024-06-12
+updated: 2025-04-15
 ---
 
 ## Public Cloud Databases
@@ -35,11 +35,6 @@ See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_
 Caching is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
 See our [Caching Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
 
-### M3db
-
-M3db is a fully managed distributed time series database. It's scalable and offers high-availability, which is ideal for your monitoring environment and time series applications.<br>
-See our [M3db Capabilities and limitations](/pages/public_cloud/public_cloud_databases/m3db_01_capabilities) guide.
-
 ### Cassandra
 
 Apache Cassandra is an open-source fully managed NoSQL database. It's highly fault-tolerant with asynchronous replication.<br>
@@ -47,15 +42,15 @@ See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_clou
 
 ## Feature Availability
 
-| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | M3db | Cassandra |
-|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|------------|-----------|
-| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Read-only nodes                                                                                              | ✓     | ✓          | ✓                |       |            |           |
-| Point in Time Recovery                                                                                       | ✓     | ✓          | ✓ <sup>(1)</sup> |       |            |           |
-| Database forking                                                                                             | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Private network connectivity (vRack)                                                                         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
+| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | Cassandra |
+|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|-----------|
+| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Read-only nodes                                                                                              | ✓     | ✓          | ✓                |       |           |
+| Point in Time Recovery                                                                                       | ✓     | ✓          | ✓ <sup>(1)</sup> |       |           |
+| Database forking                                                                                             | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Private network connectivity (vRack)                                                                         | ✓     | ✓          | ✓                | ✓     | ✓         |
 
 (1) depends on the plan
 
diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.pt-pt.md
index e18ed100197..23853795275 100644
--- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.pt-pt.md
+++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/guide.pt-pt.md
@@ -1,7 +1,7 @@
 ---
 title: Public Cloud Databases - Capabilities and Limitations (EN)
 excerpt: Discover the capabilities and limitations of Public Cloud Databases
-updated: 2024-06-12
+updated: 2025-04-15
 ---
 
 ## Public Cloud Databases
@@ -35,11 +35,6 @@ See our [MongoDB Capabilities and limitations](/pages/public_cloud/public_cloud_
 Caching is fully managed in-memory NoSQL database based on the Redis® open source software. It helps you store and access data quickly and efficiently.<br>
 See our [Caching Capabilities and limitations](/pages/public_cloud/public_cloud_databases/redis_01_capabilities) guide.
 
-### M3db
-
-M3db is a fully managed distributed time series database. It's scalable and offers high-availability, which is ideal for your monitoring environment and time series applications.<br>
-See our [M3db Capabilities and limitations](/pages/public_cloud/public_cloud_databases/m3db_01_capabilities) guide.
-
 ### Cassandra
 
 Apache Cassandra is an open-source fully managed NoSQL database. It's highly fault-tolerant with asynchronous replication.<br>
@@ -47,15 +42,15 @@ See our [Cassandra Capabilities and limitations](/pages/public_cloud/public_clou
 
 ## Feature Availability
 
-| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | M3db | Cassandra |
-|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|------------|-----------|
-| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Read-only nodes                                                                                              | ✓     | ✓          | ✓                |       |            |           |
-| Point in Time Recovery                                                                                       | ✓     | ✓          | ✓ <sup>(1)</sup> |       |            |           |
-| Database forking                                                                                             | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
-| Private network connectivity (vRack)                                                                         | ✓     | ✓          | ✓                | ✓     | ✓          | ✓         |
+| Feature                                                                                                      | MySQL | PostgreSQL | MongoDB          | Caching | Cassandra |
+|--------------------------------------------------------------------------------------------------------------|-------|------------|------------------|-------|-----------|
+| End-to-end security ([more information](/pages/public_cloud/public_cloud_databases/information_01_security_overview))         | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Automatic updates and one click upgrade                                                                      | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Read-only nodes                                                                                              | ✓     | ✓          | ✓                |       |           |
+| Point in Time Recovery                                                                                       | ✓     | ✓          | ✓ <sup>(1)</sup> |       |           |
+| Database forking                                                                                             | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Terraform Provider support ([more information](https://registry.terraform.io/providers/ovh/ovh/latest/docs)) | ✓     | ✓          | ✓                | ✓     | ✓         |
+| Private network connectivity (vRack)                                                                         | ✓     | ✓          | ✓                | ✓     | ✓         |
 
 (1) depends on the plan
 
diff --git a/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.de-de.md b/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.de-de.md
index 0cc60dfa2b5..cd28f79080e 100644
--- a/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.de-de.md
+++ b/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.de-de.md
@@ -174,7 +174,7 @@ Kafka is a streaming tool. We don't backup Kafka data.
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
+Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.en-asia.md
index 3415b7ab7f5..2d096378e81 100644
--- a/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.en-asia.md
+++ b/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.en-asia.md
@@ -174,7 +174,7 @@ Kafka is a streaming tool. We don't backup Kafka data.
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
+Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.en-au.md b/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.en-au.md
index adc6f40782b..2f0622bb175 100644
--- a/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.en-au.md
+++ b/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.en-au.md
@@ -174,7 +174,7 @@ Kafka is a streaming tool. We don't backup Kafka data.
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
+Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.en-ca.md
index 1ff76651b4d..11c6549c091 100644
--- a/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.en-ca.md
+++ b/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.en-ca.md
@@ -174,7 +174,7 @@ Kafka is a streaming tool. We don't backup Kafka data.
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
+Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.en-gb.md
index 0e2b6bd66f9..e6f9f449536 100644
--- a/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.en-gb.md
+++ b/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.en-gb.md
@@ -174,7 +174,7 @@ Kafka is a streaming tool. We don't backup Kafka data.
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
+Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.en-ie.md
index 7bf0833b0be..6be2cb8a8b8 100644
--- a/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.en-ie.md
+++ b/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.en-ie.md
@@ -174,7 +174,7 @@ Kafka is a streaming tool. We don't backup Kafka data.
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
+Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.en-sg.md
index 798b96d0a77..79af5954809 100644
--- a/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.en-sg.md
+++ b/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.en-sg.md
@@ -174,7 +174,7 @@ Kafka is a streaming tool. We don't backup Kafka data.
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
+Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.en-us.md b/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.en-us.md
index 565e462c17c..286cdea7a98 100644
--- a/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.en-us.md
+++ b/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.en-us.md
@@ -174,7 +174,7 @@ Kafka is a streaming tool. We don't backup Kafka data.
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
+Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.es-es.md b/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.es-es.md
index 313d45d10ed..5966d02ad90 100644
--- a/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.es-es.md
+++ b/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.es-es.md
@@ -174,7 +174,7 @@ Kafka is a streaming tool. We don't backup Kafka data.
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
+Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.es-us.md b/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.es-us.md
index 9029e56e7d1..ed6d802016d 100644
--- a/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.es-us.md
+++ b/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.es-us.md
@@ -174,7 +174,7 @@ Kafka is a streaming tool. We don't backup Kafka data.
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
+Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.fr-ca.md
index f2e02a8f920..52ab56c423e 100644
--- a/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.fr-ca.md
+++ b/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.fr-ca.md
@@ -174,7 +174,7 @@ Kafka is a streaming tool. We don't backup Kafka data.
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
+Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.fr-fr.md
index 54c4a378fe9..778f97e9ce6 100644
--- a/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.fr-fr.md
+++ b/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.fr-fr.md
@@ -174,7 +174,7 @@ Kafka is a streaming tool. We don't backup Kafka data.
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
+Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.it-it.md b/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.it-it.md
index 69f43d6479c..9d1564b207b 100644
--- a/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.it-it.md
+++ b/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.it-it.md
@@ -174,7 +174,7 @@ Kafka is a streaming tool. We don't backup Kafka data.
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
+Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.pl-pl.md
index 628ff28e552..e89c4e9a8f7 100644
--- a/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.pl-pl.md
+++ b/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.pl-pl.md
@@ -174,7 +174,7 @@ Kafka is a streaming tool. We don't backup Kafka data.
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
+Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.pt-pt.md
index caf812203f1..a59a67248e8 100644
--- a/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.pt-pt.md
+++ b/pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.pt-pt.md
@@ -174,7 +174,7 @@ Kafka is a streaming tool. We don't backup Kafka data.
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
+Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.de-de.md b/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.de-de.md
index b607d1e9333..ef7af9e4d9f 100644
--- a/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.de-de.md
+++ b/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.de-de.md
@@ -87,7 +87,7 @@ You can further customise your Kafka Connect by using advanced parameters. See t
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka Connect logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
+Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka Connect logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.en-asia.md
index 7b35e7a5607..28159be4c1d 100644
--- a/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.en-asia.md
+++ b/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.en-asia.md
@@ -87,7 +87,7 @@ You can further customise your Kafka Connect by using advanced parameters. See t
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka Connect logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
+Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka Connect logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.en-au.md b/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.en-au.md
index c2cf4f33050..56dc1739e72 100644
--- a/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.en-au.md
+++ b/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.en-au.md
@@ -87,7 +87,7 @@ You can further customise your Kafka Connect by using advanced parameters. See t
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka Connect logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
+Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka Connect logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.en-ca.md
index 369986e55c2..7913f39bdb4 100644
--- a/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.en-ca.md
+++ b/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.en-ca.md
@@ -87,7 +87,7 @@ You can further customise your Kafka Connect by using advanced parameters. See t
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka Connect logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
+Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka Connect logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.en-gb.md
index f161c7e8ec6..cc2a67462be 100644
--- a/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.en-gb.md
+++ b/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.en-gb.md
@@ -87,7 +87,7 @@ You can further customise your Kafka Connect by using advanced parameters. See t
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka Connect logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
+Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka Connect logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.en-ie.md
index 34c8dc2ed9e..d50506e1c94 100644
--- a/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.en-ie.md
+++ b/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.en-ie.md
@@ -87,7 +87,7 @@ You can further customise your Kafka Connect by using advanced parameters. See t
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka Connect logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
+Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka Connect logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.en-sg.md
index 3be332a4643..cf78588c5c9 100644
--- a/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.en-sg.md
+++ b/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.en-sg.md
@@ -87,7 +87,7 @@ You can further customise your Kafka Connect by using advanced parameters. See t
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka Connect logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
+Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka Connect logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.en-us.md b/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.en-us.md
index 6723e3b34c0..1288fbfd0f6 100644
--- a/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.en-us.md
+++ b/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.en-us.md
@@ -87,7 +87,7 @@ You can further customise your Kafka Connect by using advanced parameters. See t
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka Connect logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
+Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka Connect logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.es-es.md b/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.es-es.md
index 6322de1a909..bae9b2bc01d 100644
--- a/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.es-es.md
+++ b/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.es-es.md
@@ -87,7 +87,7 @@ You can further customise your Kafka Connect by using advanced parameters. See t
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka Connect logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
+Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka Connect logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.es-us.md b/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.es-us.md
index a7a746b19aa..44220128ead 100644
--- a/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.es-us.md
+++ b/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.es-us.md
@@ -87,7 +87,7 @@ You can further customise your Kafka Connect by using advanced parameters. See t
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka Connect logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
+Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka Connect logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.fr-ca.md
index 8d4b269d521..1077c1e411a 100644
--- a/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.fr-ca.md
+++ b/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.fr-ca.md
@@ -87,7 +87,7 @@ You can further customise your Kafka Connect by using advanced parameters. See t
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka Connect logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
+Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka Connect logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.fr-fr.md
index b704e550a9d..8c8461c1065 100644
--- a/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.fr-fr.md
+++ b/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.fr-fr.md
@@ -87,7 +87,7 @@ You can further customise your Kafka Connect by using advanced parameters. See t
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka Connect logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
+Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka Connect logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.it-it.md b/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.it-it.md
index 4c6bd7ecb45..f739177162e 100644
--- a/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.it-it.md
+++ b/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.it-it.md
@@ -87,7 +87,7 @@ You can further customise your Kafka Connect by using advanced parameters. See t
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka Connect logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
+Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka Connect logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.pl-pl.md
index 0331e9e37f7..537903f672d 100644
--- a/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.pl-pl.md
+++ b/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.pl-pl.md
@@ -87,7 +87,7 @@ You can further customise your Kafka Connect by using advanced parameters. See t
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka Connect logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
+Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka Connect logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.pt-pt.md
index 0c26d7d0862..8efd6dea21c 100644
--- a/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.pt-pt.md
+++ b/pages/public_cloud/public_cloud_databases/kafkaconnect_01_capabilities/guide.pt-pt.md
@@ -87,7 +87,7 @@ You can further customise your Kafka Connect by using advanced parameters. See t
 
 #### Logs and metrics
 
-Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka Connect logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL or M3db). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
+Logs and metrics are available through the Control Panel and the API. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your Kafka Connect logs in Opensearch and metrics in Dashboards service (metrics have to be exported first in a time series compatible engine such as PostgreSQL). See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information.
 
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
diff --git a/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.de-de.md b/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.de-de.md
deleted file mode 100644
index 2a3ada615e1..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.de-de.md
+++ /dev/null
@@ -1,108 +0,0 @@
----
-title: M3 Aggregator - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for M3 Aggregator
-updated: 2025-02-19
----
-
-## Objective
-
-This page provides the technical capabilities and limitations of the Public Cloud Databases' M3 Aggregator offer.
-
-We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
-
-## Capabilities and limitations
-
-### Supported regions and multi-AZ
-
-The Public Cloud Databases offer is available in the following regions:
-
-- `BHS` (Beauharnois, Canada)
-- `DE` (Frankfurt, Germany)
-- `GRA` (Gravelines, France)
-- `SBG` (Strasbourg, France)
-- `SGP` (Singapore, Singapore)
-- `UK` (London, United Kingdom)
-- `WAW` (Warsaw, Poland)
-
-The entire database instances must be in the same region. Multi-AZ is currently not supported.
-
-### M3 Aggregator versions
-
-The Public Cloud Databases offer supports M3 Aggregator version 1.5.
-
-Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions.
-
-### Plans
-
-Two plans are available:
-
-- *Business*
-- *Enterprise*
-
-Here is an overview of the various plans' capabilities:
-
-| Plan         | Number of nodes by default | Additional nodes  |
-| ------------ | -------------------------- | ----------------  |
-| *Business*   | 3                          | No                |
-| *Enterprise* | 6                          | No                |
-
-Your choice of plan affects the number of nodes your cluster can run.
-
-> [!primary]
-> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
-
-#### Nodes and replicas
-
-- **Business**: the cluster is delivered with 3 nodes by default.
-- **Enterprise**: the cluster is delivered with 6 nodes by default.
-
-#### License type
-
-Each cluster is provided with the M3 Aggregator Community (GPL) license.
-
-Where applicable, the cost of the license is included in the service plans. It is not possible to bring your own licenses.
-
-### Hardware resources
-
-For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/de/public-cloud/prices/#9745).
-
-### Features
-
-#### Network
-
-Public as well as private networking (vRack) can be used for all the offers.
-
-Ingress and Egress traffic are included in the service plans and unmetered.
-
-The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
-
-##### Private network considerations
-
-Here are some considerations to take into account when using private network:
-
-- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
-- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
-- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
-- OpenStack subnets routes announcement will not be applied to your services.
-- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
-
-##### Authorised IPs
-
-Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable.
-
-#### Logs and metrics
-
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your M3 Aggregator logs in Opensearch. See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
-
-- **Logs retention**: 1000 lines of logs
-- **Metrics retention**: 1 calendar month
-
-Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
-
-## We want your feedback!
-
-We would love to help answer questions and appreciate any feedback you may have.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/de/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
diff --git a/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.en-asia.md
deleted file mode 100644
index 737aa92a862..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.en-asia.md
+++ /dev/null
@@ -1,108 +0,0 @@
----
-title: M3 Aggregator - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for M3 Aggregator
-updated: 2025-02-19
----
-
-## Objective
-
-This page provides the technical capabilities and limitations of the Public Cloud Databases' M3 Aggregator offer.
-
-We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
-
-## Capabilities and limitations
-
-### Supported regions and multi-AZ
-
-The Public Cloud Databases offer is available in the following regions:
-
-- `BHS` (Beauharnois, Canada)
-- `DE` (Frankfurt, Germany)
-- `GRA` (Gravelines, France)
-- `SBG` (Strasbourg, France)
-- `SGP` (Singapore, Singapore)
-- `UK` (London, United Kingdom)
-- `WAW` (Warsaw, Poland)
-
-The entire database instances must be in the same region. Multi-AZ is currently not supported.
-
-### M3 Aggregator versions
-
-The Public Cloud Databases offer supports M3 Aggregator version 1.5.
-
-Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions.
-
-### Plans
-
-Two plans are available:
-
-- *Business*
-- *Enterprise*
-
-Here is an overview of the various plans' capabilities:
-
-| Plan         | Number of nodes by default | Additional nodes  |
-| ------------ | -------------------------- | ----------------  |
-| *Business*   | 3                          | No                |
-| *Enterprise* | 6                          | No                |
-
-Your choice of plan affects the number of nodes your cluster can run.
-
-> [!primary]
-> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
-
-#### Nodes and replicas
-
-- **Business**: the cluster is delivered with 3 nodes by default.
-- **Enterprise**: the cluster is delivered with 6 nodes by default.
-
-#### License type
-
-Each cluster is provided with the M3 Aggregator Community (GPL) license.
-
-Where applicable, the cost of the license is included in the service plans. It is not possible to bring your own licenses.
-
-### Hardware resources
-
-For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/asia/public-cloud/prices/#9745).
-
-### Features
-
-#### Network
-
-Public as well as private networking (vRack) can be used for all the offers.
-
-Ingress and Egress traffic are included in the service plans and unmetered.
-
-The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
-
-##### Private network considerations
-
-Here are some considerations to take into account when using private network:
-
-- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
-- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
-- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
-- OpenStack subnets routes announcement will not be applied to your services.
-- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
-
-##### Authorised IPs
-
-Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable.
-
-#### Logs and metrics
-
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your M3 Aggregator logs in Opensearch. See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
-
-- **Logs retention**: 1000 lines of logs
-- **Metrics retention**: 1 calendar month
-
-Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
-
-## We want your feedback!
-
-We would love to help answer questions and appreciate any feedback you may have.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/asia/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
diff --git a/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.en-au.md b/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.en-au.md
deleted file mode 100644
index 157f47bd72e..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.en-au.md
+++ /dev/null
@@ -1,108 +0,0 @@
----
-title: M3 Aggregator - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for M3 Aggregator
-updated: 2025-02-19
----
-
-## Objective
-
-This page provides the technical capabilities and limitations of the Public Cloud Databases' M3 Aggregator offer.
-
-We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
-
-## Capabilities and limitations
-
-### Supported regions and multi-AZ
-
-The Public Cloud Databases offer is available in the following regions:
-
-- `BHS` (Beauharnois, Canada)
-- `DE` (Frankfurt, Germany)
-- `GRA` (Gravelines, France)
-- `SBG` (Strasbourg, France)
-- `SGP` (Singapore, Singapore)
-- `UK` (London, United Kingdom)
-- `WAW` (Warsaw, Poland)
-
-The entire database instances must be in the same region. Multi-AZ is currently not supported.
-
-### M3 Aggregator versions
-
-The Public Cloud Databases offer supports M3 Aggregator version 1.5.
-
-Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions.
-
-### Plans
-
-Two plans are available:
-
-- *Business*
-- *Enterprise*
-
-Here is an overview of the various plans' capabilities:
-
-| Plan         | Number of nodes by default | Additional nodes  |
-| ------------ | -------------------------- | ----------------  |
-| *Business*   | 3                          | No                |
-| *Enterprise* | 6                          | No                |
-
-Your choice of plan affects the number of nodes your cluster can run.
-
-> [!primary]
-> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
-
-#### Nodes and replicas
-
-- **Business**: the cluster is delivered with 3 nodes by default.
-- **Enterprise**: the cluster is delivered with 6 nodes by default.
-
-#### License type
-
-Each cluster is provided with the M3 Aggregator Community (GPL) license.
-
-Where applicable, the cost of the license is included in the service plans. It is not possible to bring your own licenses.
-
-### Hardware resources
-
-For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/en-au/public-cloud/prices/#9745).
-
-### Features
-
-#### Network
-
-Public as well as private networking (vRack) can be used for all the offers.
-
-Ingress and Egress traffic are included in the service plans and unmetered.
-
-The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
-
-##### Private network considerations
-
-Here are some considerations to take into account when using private network:
-
-- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
-- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
-- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
-- OpenStack subnets routes announcement will not be applied to your services.
-- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
-
-##### Authorised IPs
-
-Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable.
-
-#### Logs and metrics
-
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your M3 Aggregator logs in Opensearch. See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
-
-- **Logs retention**: 1000 lines of logs
-- **Metrics retention**: 1 calendar month
-
-Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
-
-## We want your feedback!
-
-We would love to help answer questions and appreciate any feedback you may have.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/en-au/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
diff --git a/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.en-ca.md
deleted file mode 100644
index fb1026ed77b..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.en-ca.md
+++ /dev/null
@@ -1,108 +0,0 @@
----
-title: M3 Aggregator - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for M3 Aggregator
-updated: 2025-02-19
----
-
-## Objective
-
-This page provides the technical capabilities and limitations of the Public Cloud Databases' M3 Aggregator offer.
-
-We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
-
-## Capabilities and limitations
-
-### Supported regions and multi-AZ
-
-The Public Cloud Databases offer is available in the following regions:
-
-- `BHS` (Beauharnois, Canada)
-- `DE` (Frankfurt, Germany)
-- `GRA` (Gravelines, France)
-- `SBG` (Strasbourg, France)
-- `SGP` (Singapore, Singapore)
-- `UK` (London, United Kingdom)
-- `WAW` (Warsaw, Poland)
-
-The entire database instances must be in the same region. Multi-AZ is currently not supported.
-
-### M3 Aggregator versions
-
-The Public Cloud Databases offer supports M3 Aggregator version 1.5.
-
-Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions.
-
-### Plans
-
-Two plans are available:
-
-- *Business*
-- *Enterprise*
-
-Here is an overview of the various plans' capabilities:
-
-| Plan         | Number of nodes by default | Additional nodes  |
-| ------------ | -------------------------- | ----------------  |
-| *Business*   | 3                          | No                |
-| *Enterprise* | 6                          | No                |
-
-Your choice of plan affects the number of nodes your cluster can run.
-
-> [!primary]
-> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
-
-#### Nodes and replicas
-
-- **Business**: the cluster is delivered with 3 nodes by default.
-- **Enterprise**: the cluster is delivered with 6 nodes by default.
-
-#### License type
-
-Each cluster is provided with the M3 Aggregator Community (GPL) license.
-
-Where applicable, the cost of the license is included in the service plans. It is not possible to bring your own licenses.
-
-### Hardware resources
-
-For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/en-ca/public-cloud/prices/#9745).
-
-### Features
-
-#### Network
-
-Public as well as private networking (vRack) can be used for all the offers.
-
-Ingress and Egress traffic are included in the service plans and unmetered.
-
-The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
-
-##### Private network considerations
-
-Here are some considerations to take into account when using private network:
-
-- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
-- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
-- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
-- OpenStack subnets routes announcement will not be applied to your services.
-- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
-
-##### Authorised IPs
-
-Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable.
-
-#### Logs and metrics
-
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your M3 Aggregator logs in Opensearch. See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
-
-- **Logs retention**: 1000 lines of logs
-- **Metrics retention**: 1 calendar month
-
-Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
-
-## We want your feedback!
-
-We would love to help answer questions and appreciate any feedback you may have.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/en-ca/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
diff --git a/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.en-gb.md
deleted file mode 100644
index d777d89a398..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.en-gb.md
+++ /dev/null
@@ -1,108 +0,0 @@
----
-title: M3 Aggregator - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for M3 Aggregator
-updated: 2025-02-19
----
-
-## Objective
-
-This page provides the technical capabilities and limitations of the Public Cloud Databases' M3 Aggregator offer.
-
-We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
-
-## Capabilities and limitations
-
-### Supported regions and multi-AZ
-
-The Public Cloud Databases offer is available in the following regions:
-
-- `BHS` (Beauharnois, Canada)
-- `DE` (Frankfurt, Germany)
-- `GRA` (Gravelines, France)
-- `SBG` (Strasbourg, France)
-- `SGP` (Singapore, Singapore)
-- `UK` (London, United Kingdom)
-- `WAW` (Warsaw, Poland)
-
-The entire database instances must be in the same region. Multi-AZ is currently not supported.
-
-### M3 Aggregator versions
-
-The Public Cloud Databases offer supports M3 Aggregator version 1.5.
-
-Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions.
-
-### Plans
-
-Two plans are available:
-
-- *Business*
-- *Enterprise*
-
-Here is an overview of the various plans' capabilities:
-
-| Plan         | Number of nodes by default | Additional nodes  |
-| ------------ | -------------------------- | ----------------  |
-| *Business*   | 3                          | No                |
-| *Enterprise* | 6                          | No                |
-
-Your choice of plan affects the number of nodes your cluster can run.
-
-> [!primary]
-> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
-
-#### Nodes and replicas
-
-- **Business**: the cluster is delivered with 3 nodes by default.
-- **Enterprise**: the cluster is delivered with 6 nodes by default.
-
-#### License type
-
-Each cluster is provided with the M3 Aggregator Community (GPL) license.
-
-Where applicable, the cost of the license is included in the service plans. It is not possible to bring your own licenses.
-
-### Hardware resources
-
-For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/en-gb/public-cloud/prices/#9745).
-
-### Features
-
-#### Network
-
-Public as well as private networking (vRack) can be used for all the offers.
-
-Ingress and Egress traffic are included in the service plans and unmetered.
-
-The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
-
-##### Private network considerations
-
-Here are some considerations to take into account when using private network:
-
-- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
-- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
-- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
-- OpenStack subnets routes announcement will not be applied to your services.
-- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
-
-##### Authorised IPs
-
-Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable.
-
-#### Logs and metrics
-
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your M3 Aggregator logs in Opensearch. See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
-
-- **Logs retention**: 1000 lines of logs
-- **Metrics retention**: 1 calendar month
-
-Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
-
-## We want your feedback!
-
-We would love to help answer questions and appreciate any feedback you may have.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/en-gb/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
diff --git a/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.en-ie.md
deleted file mode 100644
index 6143ea19a14..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.en-ie.md
+++ /dev/null
@@ -1,108 +0,0 @@
----
-title: M3 Aggregator - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for M3 Aggregator
-updated: 2025-02-19
----
-
-## Objective
-
-This page provides the technical capabilities and limitations of the Public Cloud Databases' M3 Aggregator offer.
-
-We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
-
-## Capabilities and limitations
-
-### Supported regions and multi-AZ
-
-The Public Cloud Databases offer is available in the following regions:
-
-- `BHS` (Beauharnois, Canada)
-- `DE` (Frankfurt, Germany)
-- `GRA` (Gravelines, France)
-- `SBG` (Strasbourg, France)
-- `SGP` (Singapore, Singapore)
-- `UK` (London, United Kingdom)
-- `WAW` (Warsaw, Poland)
-
-The entire database instances must be in the same region. Multi-AZ is currently not supported.
-
-### M3 Aggregator versions
-
-The Public Cloud Databases offer supports M3 Aggregator version 1.5.
-
-Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions.
-
-### Plans
-
-Two plans are available:
-
-- *Business*
-- *Enterprise*
-
-Here is an overview of the various plans' capabilities:
-
-| Plan         | Number of nodes by default | Additional nodes  |
-| ------------ | -------------------------- | ----------------  |
-| *Business*   | 3                          | No                |
-| *Enterprise* | 6                          | No                |
-
-Your choice of plan affects the number of nodes your cluster can run.
-
-> [!primary]
-> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
-
-#### Nodes and replicas
-
-- **Business**: the cluster is delivered with 3 nodes by default.
-- **Enterprise**: the cluster is delivered with 6 nodes by default.
-
-#### License type
-
-Each cluster is provided with the M3 Aggregator Community (GPL) license.
-
-Where applicable, the cost of the license is included in the service plans. It is not possible to bring your own licenses.
-
-### Hardware resources
-
-For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/en-ie/public-cloud/prices/#9745).
-
-### Features
-
-#### Network
-
-Public as well as private networking (vRack) can be used for all the offers.
-
-Ingress and Egress traffic are included in the service plans and unmetered.
-
-The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
-
-##### Private network considerations
-
-Here are some considerations to take into account when using private network:
-
-- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
-- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
-- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
-- OpenStack subnets routes announcement will not be applied to your services.
-- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
-
-##### Authorised IPs
-
-Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable.
-
-#### Logs and metrics
-
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your M3 Aggregator logs in Opensearch. See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
-
-- **Logs retention**: 1000 lines of logs
-- **Metrics retention**: 1 calendar month
-
-Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
-
-## We want your feedback!
-
-We would love to help answer questions and appreciate any feedback you may have.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/en-ie/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
diff --git a/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.en-sg.md
deleted file mode 100644
index e6fe0a25533..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.en-sg.md
+++ /dev/null
@@ -1,108 +0,0 @@
----
-title: M3 Aggregator - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for M3 Aggregator
-updated: 2025-02-19
----
-
-## Objective
-
-This page provides the technical capabilities and limitations of the Public Cloud Databases' M3 Aggregator offer.
-
-We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
-
-## Capabilities and limitations
-
-### Supported regions and multi-AZ
-
-The Public Cloud Databases offer is available in the following regions:
-
-- `BHS` (Beauharnois, Canada)
-- `DE` (Frankfurt, Germany)
-- `GRA` (Gravelines, France)
-- `SBG` (Strasbourg, France)
-- `SGP` (Singapore, Singapore)
-- `UK` (London, United Kingdom)
-- `WAW` (Warsaw, Poland)
-
-The entire database instances must be in the same region. Multi-AZ is currently not supported.
-
-### M3 Aggregator versions
-
-The Public Cloud Databases offer supports M3 Aggregator version 1.5.
-
-Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions.
-
-### Plans
-
-Two plans are available:
-
-- *Business*
-- *Enterprise*
-
-Here is an overview of the various plans' capabilities:
-
-| Plan         | Number of nodes by default | Additional nodes  |
-| ------------ | -------------------------- | ----------------  |
-| *Business*   | 3                          | No                |
-| *Enterprise* | 6                          | No                |
-
-Your choice of plan affects the number of nodes your cluster can run.
-
-> [!primary]
-> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
-
-#### Nodes and replicas
-
-- **Business**: the cluster is delivered with 3 nodes by default.
-- **Enterprise**: the cluster is delivered with 6 nodes by default.
-
-#### License type
-
-Each cluster is provided with the M3 Aggregator Community (GPL) license.
-
-Where applicable, the cost of the license is included in the service plans. It is not possible to bring your own licenses.
-
-### Hardware resources
-
-For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/en-sg/public-cloud/prices/#9745).
-
-### Features
-
-#### Network
-
-Public as well as private networking (vRack) can be used for all the offers.
-
-Ingress and Egress traffic are included in the service plans and unmetered.
-
-The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
-
-##### Private network considerations
-
-Here are some considerations to take into account when using private network:
-
-- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
-- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
-- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
-- OpenStack subnets routes announcement will not be applied to your services.
-- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
-
-##### Authorised IPs
-
-Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable.
-
-#### Logs and metrics
-
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your M3 Aggregator logs in Opensearch. See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
-
-- **Logs retention**: 1000 lines of logs
-- **Metrics retention**: 1 calendar month
-
-Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
-
-## We want your feedback!
-
-We would love to help answer questions and appreciate any feedback you may have.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/en-sg/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
diff --git a/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.en-us.md b/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.en-us.md
deleted file mode 100644
index a8e68bf6a60..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.en-us.md
+++ /dev/null
@@ -1,108 +0,0 @@
----
-title: M3 Aggregator - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for M3 Aggregator
-updated: 2025-02-19
----
-
-## Objective
-
-This page provides the technical capabilities and limitations of the Public Cloud Databases' M3 Aggregator offer.
-
-We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
-
-## Capabilities and limitations
-
-### Supported regions and multi-AZ
-
-The Public Cloud Databases offer is available in the following regions:
-
-- `BHS` (Beauharnois, Canada)
-- `DE` (Frankfurt, Germany)
-- `GRA` (Gravelines, France)
-- `SBG` (Strasbourg, France)
-- `SGP` (Singapore, Singapore)
-- `UK` (London, United Kingdom)
-- `WAW` (Warsaw, Poland)
-
-The entire database instances must be in the same region. Multi-AZ is currently not supported.
-
-### M3 Aggregator versions
-
-The Public Cloud Databases offer supports M3 Aggregator version 1.5.
-
-Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions.
-
-### Plans
-
-Two plans are available:
-
-- *Business*
-- *Enterprise*
-
-Here is an overview of the various plans' capabilities:
-
-| Plan         | Number of nodes by default | Additional nodes  |
-| ------------ | -------------------------- | ----------------  |
-| *Business*   | 3                          | No                |
-| *Enterprise* | 6                          | No                |
-
-Your choice of plan affects the number of nodes your cluster can run.
-
-> [!primary]
-> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
-
-#### Nodes and replicas
-
-- **Business**: the cluster is delivered with 3 nodes by default.
-- **Enterprise**: the cluster is delivered with 6 nodes by default.
-
-#### License type
-
-Each cluster is provided with the M3 Aggregator Community (GPL) license.
-
-Where applicable, the cost of the license is included in the service plans. It is not possible to bring your own licenses.
-
-### Hardware resources
-
-For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/en/public-cloud/prices/#9745).
-
-### Features
-
-#### Network
-
-Public as well as private networking (vRack) can be used for all the offers.
-
-Ingress and Egress traffic are included in the service plans and unmetered.
-
-The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
-
-##### Private network considerations
-
-Here are some considerations to take into account when using private network:
-
-- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
-- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
-- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
-- OpenStack subnets routes announcement will not be applied to your services.
-- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
-
-##### Authorised IPs
-
-Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable.
-
-#### Logs and metrics
-
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your M3 Aggregator logs in Opensearch. See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
-
-- **Logs retention**: 1000 lines of logs
-- **Metrics retention**: 1 calendar month
-
-Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
-
-## We want your feedback!
-
-We would love to help answer questions and appreciate any feedback you may have.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/en/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
diff --git a/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.es-es.md b/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.es-es.md
deleted file mode 100644
index ed870146c6a..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.es-es.md
+++ /dev/null
@@ -1,108 +0,0 @@
----
-title: M3 Aggregator - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for M3 Aggregator
-updated: 2025-02-19
----
-
-## Objective
-
-This page provides the technical capabilities and limitations of the Public Cloud Databases' M3 Aggregator offer.
-
-We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
-
-## Capabilities and limitations
-
-### Supported regions and multi-AZ
-
-The Public Cloud Databases offer is available in the following regions:
-
-- `BHS` (Beauharnois, Canada)
-- `DE` (Frankfurt, Germany)
-- `GRA` (Gravelines, France)
-- `SBG` (Strasbourg, France)
-- `SGP` (Singapore, Singapore)
-- `UK` (London, United Kingdom)
-- `WAW` (Warsaw, Poland)
-
-The entire database instances must be in the same region. Multi-AZ is currently not supported.
-
-### M3 Aggregator versions
-
-The Public Cloud Databases offer supports M3 Aggregator version 1.5.
-
-Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions.
-
-### Plans
-
-Two plans are available:
-
-- *Business*
-- *Enterprise*
-
-Here is an overview of the various plans' capabilities:
-
-| Plan         | Number of nodes by default | Additional nodes  |
-| ------------ | -------------------------- | ----------------  |
-| *Business*   | 3                          | No                |
-| *Enterprise* | 6                          | No                |
-
-Your choice of plan affects the number of nodes your cluster can run.
-
-> [!primary]
-> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
-
-#### Nodes and replicas
-
-- **Business**: the cluster is delivered with 3 nodes by default.
-- **Enterprise**: the cluster is delivered with 6 nodes by default.
-
-#### License type
-
-Each cluster is provided with the M3 Aggregator Community (GPL) license.
-
-Where applicable, the cost of the license is included in the service plans. It is not possible to bring your own licenses.
-
-### Hardware resources
-
-For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/es-es/public-cloud/prices/#9745).
-
-### Features
-
-#### Network
-
-Public as well as private networking (vRack) can be used for all the offers.
-
-Ingress and Egress traffic are included in the service plans and unmetered.
-
-The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
-
-##### Private network considerations
-
-Here are some considerations to take into account when using private network:
-
-- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
-- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
-- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
-- OpenStack subnets routes announcement will not be applied to your services.
-- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
-
-##### Authorised IPs
-
-Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable.
-
-#### Logs and metrics
-
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your M3 Aggregator logs in Opensearch. See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
-
-- **Logs retention**: 1000 lines of logs
-- **Metrics retention**: 1 calendar month
-
-Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
-
-## We want your feedback!
-
-We would love to help answer questions and appreciate any feedback you may have.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/es-es/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
diff --git a/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.es-us.md b/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.es-us.md
deleted file mode 100644
index e2bb25ad56f..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.es-us.md
+++ /dev/null
@@ -1,108 +0,0 @@
----
-title: M3 Aggregator - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for M3 Aggregator
-updated: 2025-02-19
----
-
-## Objective
-
-This page provides the technical capabilities and limitations of the Public Cloud Databases' M3 Aggregator offer.
-
-We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
-
-## Capabilities and limitations
-
-### Supported regions and multi-AZ
-
-The Public Cloud Databases offer is available in the following regions:
-
-- `BHS` (Beauharnois, Canada)
-- `DE` (Frankfurt, Germany)
-- `GRA` (Gravelines, France)
-- `SBG` (Strasbourg, France)
-- `SGP` (Singapore, Singapore)
-- `UK` (London, United Kingdom)
-- `WAW` (Warsaw, Poland)
-
-The entire database instances must be in the same region. Multi-AZ is currently not supported.
-
-### M3 Aggregator versions
-
-The Public Cloud Databases offer supports M3 Aggregator version 1.5.
-
-Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions.
-
-### Plans
-
-Two plans are available:
-
-- *Business*
-- *Enterprise*
-
-Here is an overview of the various plans' capabilities:
-
-| Plan         | Number of nodes by default | Additional nodes  |
-| ------------ | -------------------------- | ----------------  |
-| *Business*   | 3                          | No                |
-| *Enterprise* | 6                          | No                |
-
-Your choice of plan affects the number of nodes your cluster can run.
-
-> [!primary]
-> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
-
-#### Nodes and replicas
-
-- **Business**: the cluster is delivered with 3 nodes by default.
-- **Enterprise**: the cluster is delivered with 6 nodes by default.
-
-#### License type
-
-Each cluster is provided with the M3 Aggregator Community (GPL) license.
-
-Where applicable, the cost of the license is included in the service plans. It is not possible to bring your own licenses.
-
-### Hardware resources
-
-For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/es/public-cloud/prices/#9745).
-
-### Features
-
-#### Network
-
-Public as well as private networking (vRack) can be used for all the offers.
-
-Ingress and Egress traffic are included in the service plans and unmetered.
-
-The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
-
-##### Private network considerations
-
-Here are some considerations to take into account when using private network:
-
-- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
-- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
-- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
-- OpenStack subnets routes announcement will not be applied to your services.
-- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
-
-##### Authorised IPs
-
-Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable.
-
-#### Logs and metrics
-
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your M3 Aggregator logs in Opensearch. See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
-
-- **Logs retention**: 1000 lines of logs
-- **Metrics retention**: 1 calendar month
-
-Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
-
-## We want your feedback!
-
-We would love to help answer questions and appreciate any feedback you may have.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/es/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
diff --git a/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.fr-ca.md
deleted file mode 100644
index 14f40fe3fab..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.fr-ca.md
+++ /dev/null
@@ -1,108 +0,0 @@
----
-title: M3 Aggregator - Capacités et limitations (EN)
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for M3 Aggregator
-updated: 2025-02-19
----
-
-## Objective
-
-This page provides the technical capabilities and limitations of the Public Cloud Databases' M3 Aggregator offer.
-
-We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
-
-## Capabilities and limitations
-
-### Supported regions and multi-AZ
-
-The Public Cloud Databases offer is available in the following regions:
-
-- `BHS` (Beauharnois, Canada)
-- `DE` (Frankfurt, Germany)
-- `GRA` (Gravelines, France)
-- `SBG` (Strasbourg, France)
-- `SGP` (Singapore, Singapore)
-- `UK` (London, United Kingdom)
-- `WAW` (Warsaw, Poland)
-
-The entire database instances must be in the same region. Multi-AZ is currently not supported.
-
-### M3 Aggregator versions
-
-The Public Cloud Databases offer supports M3 Aggregator version 1.5.
-
-Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions.
-
-### Plans
-
-Two plans are available:
-
-- *Business*
-- *Enterprise*
-
-Here is an overview of the various plans' capabilities:
-
-| Plan         | Number of nodes by default | Additional nodes  |
-| ------------ | -------------------------- | ----------------  |
-| *Business*   | 3                          | No                |
-| *Enterprise* | 6                          | No                |
-
-Your choice of plan affects the number of nodes your cluster can run.
-
-> [!primary]
-> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
-
-#### Nodes and replicas
-
-- **Business**: the cluster is delivered with 3 nodes by default.
-- **Enterprise**: the cluster is delivered with 6 nodes by default.
-
-#### License type
-
-Each cluster is provided with the M3 Aggregator Community (GPL) license.
-
-Where applicable, the cost of the license is included in the service plans. It is not possible to bring your own licenses.
-
-### Hardware resources
-
-For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/fr-ca/public-cloud/prices/#9745).
-
-### Features
-
-#### Network
-
-Public as well as private networking (vRack) can be used for all the offers.
-
-Ingress and Egress traffic are included in the service plans and unmetered.
-
-The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
-
-##### Private network considerations
-
-Here are some considerations to take into account when using private network:
-
-- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
-- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
-- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
-- OpenStack subnets routes announcement will not be applied to your services.
-- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
-
-##### Authorised IPs
-
-Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable.
-
-#### Logs and metrics
-
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your M3 Aggregator logs in Opensearch. See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
-
-- **Logs retention**: 1000 lines of logs
-- **Metrics retention**: 1 calendar month
-
-Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
-
-## We want your feedback!
-
-We would love to help answer questions and appreciate any feedback you may have.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/fr-ca/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
diff --git a/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.fr-fr.md
deleted file mode 100644
index 72ba8c72182..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.fr-fr.md
+++ /dev/null
@@ -1,108 +0,0 @@
----
-title: M3 Aggregator - Capacités et limitations (EN)
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for M3 Aggregator
-updated: 2025-02-19
----
-
-## Objective
-
-This page provides the technical capabilities and limitations of the Public Cloud Databases' M3 Aggregator offer.
-
-We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
-
-## Capabilities and limitations
-
-### Supported regions and multi-AZ
-
-The Public Cloud Databases offer is available in the following regions:
-
-- `BHS` (Beauharnois, Canada)
-- `DE` (Frankfurt, Germany)
-- `GRA` (Gravelines, France)
-- `SBG` (Strasbourg, France)
-- `SGP` (Singapore, Singapore)
-- `UK` (London, United Kingdom)
-- `WAW` (Warsaw, Poland)
-
-The entire database instances must be in the same region. Multi-AZ is currently not supported.
-
-### M3 Aggregator versions
-
-The Public Cloud Databases offer supports M3 Aggregator version 1.5.
-
-Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions.
-
-### Plans
-
-Two plans are available:
-
-- *Business*
-- *Enterprise*
-
-Here is an overview of the various plans' capabilities:
-
-| Plan         | Number of nodes by default | Additional nodes  |
-| ------------ | -------------------------- | ----------------  |
-| *Business*   | 3                          | No                |
-| *Enterprise* | 6                          | No                |
-
-Your choice of plan affects the number of nodes your cluster can run.
-
-> [!primary]
-> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
-
-#### Nodes and replicas
-
-- **Business**: the cluster is delivered with 3 nodes by default.
-- **Enterprise**: the cluster is delivered with 6 nodes by default.
-
-#### License type
-
-Each cluster is provided with the M3 Aggregator Community (GPL) license.
-
-Where applicable, the cost of the license is included in the service plans. It is not possible to bring your own licenses.
-
-### Hardware resources
-
-For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/fr/public-cloud/prices/#9745).
-
-### Features
-
-#### Network
-
-Public as well as private networking (vRack) can be used for all the offers.
-
-Ingress and Egress traffic are included in the service plans and unmetered.
-
-The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
-
-##### Private network considerations
-
-Here are some considerations to take into account when using private network:
-
-- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
-- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
-- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
-- OpenStack subnets routes announcement will not be applied to your services.
-- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
-
-##### Authorised IPs
-
-Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable.
-
-#### Logs and metrics
-
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your M3 Aggregator logs in Opensearch. See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
-
-- **Logs retention**: 1000 lines of logs
-- **Metrics retention**: 1 calendar month
-
-Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
-
-## We want your feedback!
-
-We would love to help answer questions and appreciate any feedback you may have.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/fr/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
diff --git a/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.it-it.md b/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.it-it.md
deleted file mode 100644
index 11186fc6293..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.it-it.md
+++ /dev/null
@@ -1,108 +0,0 @@
----
-title: M3 Aggregator - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for M3 Aggregator
-updated: 2025-02-19
----
-
-## Objective
-
-This page provides the technical capabilities and limitations of the Public Cloud Databases' M3 Aggregator offer.
-
-We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
-
-## Capabilities and limitations
-
-### Supported regions and multi-AZ
-
-The Public Cloud Databases offer is available in the following regions:
-
-- `BHS` (Beauharnois, Canada)
-- `DE` (Frankfurt, Germany)
-- `GRA` (Gravelines, France)
-- `SBG` (Strasbourg, France)
-- `SGP` (Singapore, Singapore)
-- `UK` (London, United Kingdom)
-- `WAW` (Warsaw, Poland)
-
-The entire database instances must be in the same region. Multi-AZ is currently not supported.
-
-### M3 Aggregator versions
-
-The Public Cloud Databases offer supports M3 Aggregator version 1.5.
-
-Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions.
-
-### Plans
-
-Two plans are available:
-
-- *Business*
-- *Enterprise*
-
-Here is an overview of the various plans' capabilities:
-
-| Plan         | Number of nodes by default | Additional nodes  |
-| ------------ | -------------------------- | ----------------  |
-| *Business*   | 3                          | No                |
-| *Enterprise* | 6                          | No                |
-
-Your choice of plan affects the number of nodes your cluster can run.
-
-> [!primary]
-> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
-
-#### Nodes and replicas
-
-- **Business**: the cluster is delivered with 3 nodes by default.
-- **Enterprise**: the cluster is delivered with 6 nodes by default.
-
-#### License type
-
-Each cluster is provided with the M3 Aggregator Community (GPL) license.
-
-Where applicable, the cost of the license is included in the service plans. It is not possible to bring your own licenses.
-
-### Hardware resources
-
-For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/it/public-cloud/prices/#9745).
-
-### Features
-
-#### Network
-
-Public as well as private networking (vRack) can be used for all the offers.
-
-Ingress and Egress traffic are included in the service plans and unmetered.
-
-The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
-
-##### Private network considerations
-
-Here are some considerations to take into account when using private network:
-
-- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
-- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
-- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
-- OpenStack subnets routes announcement will not be applied to your services.
-- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
-
-##### Authorised IPs
-
-Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable.
-
-#### Logs and metrics
-
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your M3 Aggregator logs in Opensearch. See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
-
-- **Logs retention**: 1000 lines of logs
-- **Metrics retention**: 1 calendar month
-
-Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
-
-## We want your feedback!
-
-We would love to help answer questions and appreciate any feedback you may have.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/it/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
diff --git a/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.pl-pl.md
deleted file mode 100644
index 3898c14301a..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.pl-pl.md
+++ /dev/null
@@ -1,108 +0,0 @@
----
-title: M3 Aggregator - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for M3 Aggregator
-updated: 2025-02-19
----
-
-## Objective
-
-This page provides the technical capabilities and limitations of the Public Cloud Databases' M3 Aggregator offer.
-
-We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
-
-## Capabilities and limitations
-
-### Supported regions and multi-AZ
-
-The Public Cloud Databases offer is available in the following regions:
-
-- `BHS` (Beauharnois, Canada)
-- `DE` (Frankfurt, Germany)
-- `GRA` (Gravelines, France)
-- `SBG` (Strasbourg, France)
-- `SGP` (Singapore, Singapore)
-- `UK` (London, United Kingdom)
-- `WAW` (Warsaw, Poland)
-
-The entire database instances must be in the same region. Multi-AZ is currently not supported.
-
-### M3 Aggregator versions
-
-The Public Cloud Databases offer supports M3 Aggregator version 1.5.
-
-Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions.
-
-### Plans
-
-Two plans are available:
-
-- *Business*
-- *Enterprise*
-
-Here is an overview of the various plans' capabilities:
-
-| Plan         | Number of nodes by default | Additional nodes  |
-| ------------ | -------------------------- | ----------------  |
-| *Business*   | 3                          | No                |
-| *Enterprise* | 6                          | No                |
-
-Your choice of plan affects the number of nodes your cluster can run.
-
-> [!primary]
-> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
-
-#### Nodes and replicas
-
-- **Business**: the cluster is delivered with 3 nodes by default.
-- **Enterprise**: the cluster is delivered with 6 nodes by default.
-
-#### License type
-
-Each cluster is provided with the M3 Aggregator Community (GPL) license.
-
-Where applicable, the cost of the license is included in the service plans. It is not possible to bring your own licenses.
-
-### Hardware resources
-
-For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/pl/public-cloud/prices/#9745).
-
-### Features
-
-#### Network
-
-Public as well as private networking (vRack) can be used for all the offers.
-
-Ingress and Egress traffic are included in the service plans and unmetered.
-
-The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
-
-##### Private network considerations
-
-Here are some considerations to take into account when using private network:
-
-- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
-- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
-- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
-- OpenStack subnets routes announcement will not be applied to your services.
-- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
-
-##### Authorised IPs
-
-Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable.
-
-#### Logs and metrics
-
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your M3 Aggregator logs in Opensearch. See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
-
-- **Logs retention**: 1000 lines of logs
-- **Metrics retention**: 1 calendar month
-
-Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
-
-## We want your feedback!
-
-We would love to help answer questions and appreciate any feedback you may have.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/pl/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
diff --git a/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.pt-pt.md
deleted file mode 100644
index 3fcdccecce0..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/guide.pt-pt.md
+++ /dev/null
@@ -1,108 +0,0 @@
----
-title: M3 Aggregator - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for M3 Aggregator
-updated: 2025-02-19
----
-
-## Objective
-
-This page provides the technical capabilities and limitations of the Public Cloud Databases' M3 Aggregator offer.
-
-We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
-
-## Capabilities and limitations
-
-### Supported regions and multi-AZ
-
-The Public Cloud Databases offer is available in the following regions:
-
-- `BHS` (Beauharnois, Canada)
-- `DE` (Frankfurt, Germany)
-- `GRA` (Gravelines, France)
-- `SBG` (Strasbourg, France)
-- `SGP` (Singapore, Singapore)
-- `UK` (London, United Kingdom)
-- `WAW` (Warsaw, Poland)
-
-The entire database instances must be in the same region. Multi-AZ is currently not supported.
-
-### M3 Aggregator versions
-
-The Public Cloud Databases offer supports M3 Aggregator version 1.5.
-
-Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions.
-
-### Plans
-
-Two plans are available:
-
-- *Business*
-- *Enterprise*
-
-Here is an overview of the various plans' capabilities:
-
-| Plan         | Number of nodes by default | Additional nodes  |
-| ------------ | -------------------------- | ----------------  |
-| *Business*   | 3                          | No                |
-| *Enterprise* | 6                          | No                |
-
-Your choice of plan affects the number of nodes your cluster can run.
-
-> [!primary]
-> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
-
-#### Nodes and replicas
-
-- **Business**: the cluster is delivered with 3 nodes by default.
-- **Enterprise**: the cluster is delivered with 6 nodes by default.
-
-#### License type
-
-Each cluster is provided with the M3 Aggregator Community (GPL) license.
-
-Where applicable, the cost of the license is included in the service plans. It is not possible to bring your own licenses.
-
-### Hardware resources
-
-For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/pt/public-cloud/prices/#9745).
-
-### Features
-
-#### Network
-
-Public as well as private networking (vRack) can be used for all the offers.
-
-Ingress and Egress traffic are included in the service plans and unmetered.
-
-The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
-
-##### Private network considerations
-
-Here are some considerations to take into account when using private network:
-
-- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
-- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
-- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
-- OpenStack subnets routes announcement will not be applied to your services.
-- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
-
-##### Authorised IPs
-
-Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable.
-
-#### Logs and metrics
-
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your M3 Aggregator logs in Opensearch. See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
-
-- **Logs retention**: 1000 lines of logs
-- **Metrics retention**: 1 calendar month
-
-Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
-
-## We want your feedback!
-
-We would love to help answer questions and appreciate any feedback you may have.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/pt/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
diff --git a/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/meta.yaml b/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/meta.yaml
deleted file mode 100755
index 4b2e1b36d2c..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3aggregator_01_capabilities/meta.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-id: 6b0074b1-43f7-4258-b837-725084e33c88
-full_slug: public-cloud-databases-m3aggregator-capabilities
-engine: m3aggregator
-section: dashboard
-reference_category: public-cloud-databases-m3-aggregator-guides
\ No newline at end of file
diff --git a/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.de-de.md b/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.de-de.md
deleted file mode 100644
index 987b324cfdc..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.de-de.md
+++ /dev/null
@@ -1,121 +0,0 @@
----
-title: M3db - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for M3db
-updated: 2025-02-19
----
-
-## Objective
-
-This page provides the technical capabilities and limitations of the Public Cloud Databases M3db offer.
-
-We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
-
-## Capabilities and limitations
-
-### Supported regions and multi-AZ
-
-The Public Cloud Databases offer is available in the following regions:
-
-- `BHS` (Beauharnois, Canada)
-- `DE` (Frankfurt, Germany)
-- `GRA` (Gravelines, France)
-- `SBG` (Strasbourg, France)
-- `SGP` (Singapore, Singapore)
-- `UK` (London, United Kingdom)
-- `WAW` (Warsaw, Poland)
-
-Entire database instances have to be in the same region. Multi-AZ is currently not supported.
-
-### M3db versions
-
-The Public Cloud Databases offer supports M3db version 1.5.
-
-Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. M3db recommends always installing and using the latest stable version.
-
-### Plans
-
-Three plans are available:
-
-- *Essential*
-- *Business*
-- *Enterprise*
-
-Here is an overview of the various plans' capabilities:
-
-| Plan         | Number of nodes by default | Read replicas  |
-| ------------ | -------------------------- | -------------  |
-| *Essential*  | 1                          | No             |
-| *Business*   | 3                          | Planned        |
-| *Enterprise* | 6                          | Planned        |
-
-Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention.
-
-> [!primary]
-> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
-
-#### Nodes and replicas
-
-- **Essential**: the cluster can support at most one node.
-- **Business**: the cluster is delivered with 3 nodes by default. Adding read replicas is planned.
-- **Enterprise**: the cluster is delivered with 6 nodes by default. Adding read replicas is planned.
-
-#### License type
-
-Each cluster is provided with the M3db Community (GPL) license.
-
-If any, license cost is included inside the service plans. You can't bring your own licenses.
-
-### Hardware resources
-
-For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/de/public-cloud/prices/#9718).
-
-### Features
-
-#### Network
-
-Public as well as private networking (vRack) can be used for all the offers.
-
-Ingress and Egress traffic are included in the service plans and unmetered.
-
-The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
-
-##### Private network considerations
-
-Here are some considerations to take into account when using private network:
-
-- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
-- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
-- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
-- OpenStack subnets routes announcement will not be applied to your services.
-- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
-
-##### Authorised IPs
-
-Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable.
-
-#### Backups
-
-*Essential* plan clusters are automatically backed up daily. Backup retention is 1 day.
-
-*Business* plan clusters are automatically backed up daily. Backup retention is 6 days.
-
-*Enterprise* plan clusters are automatically backed up daily. Backup retention is 13 days.
-
-See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/databases_05_automated_backups) for more information.
-
-#### Logs and metrics
-
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your M3db logs in Opensearch and metrics in Dashboards service. See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
-
-- **Logs retention**: 1000 lines of logs
-- **Metrics retention**: 1 calendar month
-
-Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
-
-## We want your feedback!
-
-We would love to help answer questions and appreciate any feedback you may have.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/de/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
diff --git a/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.en-asia.md
deleted file mode 100644
index 7c8aba90019..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.en-asia.md
+++ /dev/null
@@ -1,121 +0,0 @@
----
-title: M3db - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for M3db
-updated: 2025-02-19
----
-
-## Objective
-
-This page provides the technical capabilities and limitations of the Public Cloud Databases M3db offer.
-
-We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
-
-## Capabilities and limitations
-
-### Supported regions and multi-AZ
-
-The Public Cloud Databases offer is available in the following regions:
-
-- `BHS` (Beauharnois, Canada)
-- `DE` (Frankfurt, Germany)
-- `GRA` (Gravelines, France)
-- `SBG` (Strasbourg, France)
-- `SGP` (Singapore, Singapore)
-- `UK` (London, United Kingdom)
-- `WAW` (Warsaw, Poland)
-
-Entire database instances have to be in the same region. Multi-AZ is currently not supported.
-
-### M3db versions
-
-The Public Cloud Databases offer supports M3db version 1.5.
-
-Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. M3db recommends always installing and using the latest stable version.
-
-### Plans
-
-Three plans are available:
-
-- *Essential*
-- *Business*
-- *Enterprise*
-
-Here is an overview of the various plans' capabilities:
-
-| Plan         | Number of nodes by default | Read replicas  |
-| ------------ | -------------------------- | -------------  |
-| *Essential*  | 1                          | No             |
-| *Business*   | 3                          | Planned        |
-| *Enterprise* | 6                          | Planned        |
-
-Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention.
-
-> [!primary]
-> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
-
-#### Nodes and replicas
-
-- **Essential**: the cluster can support at most one node.
-- **Business**: the cluster is delivered with 3 nodes by default. Adding read replicas is planned.
-- **Enterprise**: the cluster is delivered with 6 nodes by default. Adding read replicas is planned.
-
-#### License type
-
-Each cluster is provided with the M3db Community (GPL) license.
-
-If any, license cost is included inside the service plans. You can't bring your own licenses.
-
-### Hardware resources
-
-For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/asia/public-cloud/prices/#9718).
-
-### Features
-
-#### Network
-
-Public as well as private networking (vRack) can be used for all the offers.
-
-Ingress and Egress traffic are included in the service plans and unmetered.
-
-The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
-
-##### Private network considerations
-
-Here are some considerations to take into account when using private network:
-
-- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
-- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
-- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
-- OpenStack subnets routes announcement will not be applied to your services.
-- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
-
-##### Authorised IPs
-
-Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable.
-
-#### Backups
-
-*Essential* plan clusters are automatically backed up daily. Backup retention is 1 day.
-
-*Business* plan clusters are automatically backed up daily. Backup retention is 6 days.
-
-*Enterprise* plan clusters are automatically backed up daily. Backup retention is 13 days.
-
-See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/databases_05_automated_backups) for more information.
-
-#### Logs and metrics
-
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your M3db logs in Opensearch and metrics in Dashboards service. See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
-
-- **Logs retention**: 1000 lines of logs
-- **Metrics retention**: 1 calendar month
-
-Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
-
-## We want your feedback!
-
-We would love to help answer questions and appreciate any feedback you may have.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/asia/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
diff --git a/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.en-au.md b/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.en-au.md
deleted file mode 100644
index bffe0f6902e..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.en-au.md
+++ /dev/null
@@ -1,121 +0,0 @@
----
-title: M3db - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for M3db
-updated: 2025-02-19
----
-
-## Objective
-
-This page provides the technical capabilities and limitations of the Public Cloud Databases M3db offer.
-
-We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
-
-## Capabilities and limitations
-
-### Supported regions and multi-AZ
-
-The Public Cloud Databases offer is available in the following regions:
-
-- `BHS` (Beauharnois, Canada)
-- `DE` (Frankfurt, Germany)
-- `GRA` (Gravelines, France)
-- `SBG` (Strasbourg, France)
-- `SGP` (Singapore, Singapore)
-- `UK` (London, United Kingdom)
-- `WAW` (Warsaw, Poland)
-
-Entire database instances have to be in the same region. Multi-AZ is currently not supported.
-
-### M3db versions
-
-The Public Cloud Databases offer supports M3db version 1.5.
-
-Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. M3db recommends always installing and using the latest stable version.
-
-### Plans
-
-Three plans are available:
-
-- *Essential*
-- *Business*
-- *Enterprise*
-
-Here is an overview of the various plans' capabilities:
-
-| Plan         | Number of nodes by default | Read replicas  |
-| ------------ | -------------------------- | -------------  |
-| *Essential*  | 1                          | No             |
-| *Business*   | 3                          | Planned        |
-| *Enterprise* | 6                          | Planned        |
-
-Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention.
-
-> [!primary]
-> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
-
-#### Nodes and replicas
-
-- **Essential**: the cluster can support at most one node.
-- **Business**: the cluster is delivered with 3 nodes by default. Adding read replicas is planned.
-- **Enterprise**: the cluster is delivered with 6 nodes by default. Adding read replicas is planned.
-
-#### License type
-
-Each cluster is provided with the M3db Community (GPL) license.
-
-If any, license cost is included inside the service plans. You can't bring your own licenses.
-
-### Hardware resources
-
-For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/en-au/public-cloud/prices/#9718).
-
-### Features
-
-#### Network
-
-Public as well as private networking (vRack) can be used for all the offers.
-
-Ingress and Egress traffic are included in the service plans and unmetered.
-
-The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
-
-##### Private network considerations
-
-Here are some considerations to take into account when using private network:
-
-- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
-- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
-- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
-- OpenStack subnets routes announcement will not be applied to your services.
-- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
-
-##### Authorised IPs
-
-Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable.
-
-#### Backups
-
-*Essential* plan clusters are automatically backed up daily. Backup retention is 1 day.
-
-*Business* plan clusters are automatically backed up daily. Backup retention is 6 days.
-
-*Enterprise* plan clusters are automatically backed up daily. Backup retention is 13 days.
-
-See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/databases_05_automated_backups) for more information.
-
-#### Logs and metrics
-
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your M3db logs in Opensearch and metrics in Dashboards service. See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
-
-- **Logs retention**: 1000 lines of logs
-- **Metrics retention**: 1 calendar month
-
-Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
-
-## We want your feedback!
-
-We would love to help answer questions and appreciate any feedback you may have.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/en-au/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
diff --git a/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.en-ca.md
deleted file mode 100644
index 3411c5ef81b..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.en-ca.md
+++ /dev/null
@@ -1,121 +0,0 @@
----
-title: M3db - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for M3db
-updated: 2025-02-19
----
-
-## Objective
-
-This page provides the technical capabilities and limitations of the Public Cloud Databases M3db offer.
-
-We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
-
-## Capabilities and limitations
-
-### Supported regions and multi-AZ
-
-The Public Cloud Databases offer is available in the following regions:
-
-- `BHS` (Beauharnois, Canada)
-- `DE` (Frankfurt, Germany)
-- `GRA` (Gravelines, France)
-- `SBG` (Strasbourg, France)
-- `SGP` (Singapore, Singapore)
-- `UK` (London, United Kingdom)
-- `WAW` (Warsaw, Poland)
-
-Entire database instances have to be in the same region. Multi-AZ is currently not supported.
-
-### M3db versions
-
-The Public Cloud Databases offer supports M3db version 1.5.
-
-Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. M3db recommends always installing and using the latest stable version.
-
-### Plans
-
-Three plans are available:
-
-- *Essential*
-- *Business*
-- *Enterprise*
-
-Here is an overview of the various plans' capabilities:
-
-| Plan         | Number of nodes by default | Read replicas  |
-| ------------ | -------------------------- | -------------  |
-| *Essential*  | 1                          | No             |
-| *Business*   | 3                          | Planned        |
-| *Enterprise* | 6                          | Planned        |
-
-Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention.
-
-> [!primary]
-> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
-
-#### Nodes and replicas
-
-- **Essential**: the cluster can support at most one node.
-- **Business**: the cluster is delivered with 3 nodes by default. Adding read replicas is planned.
-- **Enterprise**: the cluster is delivered with 6 nodes by default. Adding read replicas is planned.
-
-#### License type
-
-Each cluster is provided with the M3db Community (GPL) license.
-
-If any, license cost is included inside the service plans. You can't bring your own licenses.
-
-### Hardware resources
-
-For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/en-ca/public-cloud/prices/#9718).
-
-### Features
-
-#### Network
-
-Public as well as private networking (vRack) can be used for all the offers.
-
-Ingress and Egress traffic are included in the service plans and unmetered.
-
-The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
-
-##### Private network considerations
-
-Here are some considerations to take into account when using private network:
-
-- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
-- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
-- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
-- OpenStack subnets routes announcement will not be applied to your services.
-- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
-
-##### Authorised IPs
-
-Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable.
-
-#### Backups
-
-*Essential* plan clusters are automatically backed up daily. Backup retention is 1 day.
-
-*Business* plan clusters are automatically backed up daily. Backup retention is 6 days.
-
-*Enterprise* plan clusters are automatically backed up daily. Backup retention is 13 days.
-
-See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/databases_05_automated_backups) for more information.
-
-#### Logs and metrics
-
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your M3db logs in Opensearch and metrics in Dashboards service. See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
-
-- **Logs retention**: 1000 lines of logs
-- **Metrics retention**: 1 calendar month
-
-Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
-
-## We want your feedback!
-
-We would love to help answer questions and appreciate any feedback you may have.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/en-ca/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
diff --git a/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.en-gb.md
deleted file mode 100644
index ff88e310d6c..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.en-gb.md
+++ /dev/null
@@ -1,121 +0,0 @@
----
-title: M3db - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for M3db
-updated: 2025-02-19
----
-
-## Objective
-
-This page provides the technical capabilities and limitations of the Public Cloud Databases M3db offer.
-
-We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
-
-## Capabilities and limitations
-
-### Supported regions and multi-AZ
-
-The Public Cloud Databases offer is available in the following regions:
-
-- `BHS` (Beauharnois, Canada)
-- `DE` (Frankfurt, Germany)
-- `GRA` (Gravelines, France)
-- `SBG` (Strasbourg, France)
-- `SGP` (Singapore, Singapore)
-- `UK` (London, United Kingdom)
-- `WAW` (Warsaw, Poland)
-
-Entire database instances have to be in the same region. Multi-AZ is currently not supported.
-
-### M3db versions
-
-The Public Cloud Databases offer supports M3db version 1.5.
-
-Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. M3db recommends always installing and using the latest stable version.
-
-### Plans
-
-Three plans are available:
-
-- *Essential*
-- *Business*
-- *Enterprise*
-
-Here is an overview of the various plans' capabilities:
-
-| Plan         | Number of nodes by default | Read replicas  |
-| ------------ | -------------------------- | -------------  |
-| *Essential*  | 1                          | No             |
-| *Business*   | 3                          | Planned        |
-| *Enterprise* | 6                          | Planned        |
-
-Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention.
-
-> [!primary]
-> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
-
-#### Nodes and replicas
-
-- **Essential**: the cluster can support at most one node.
-- **Business**: the cluster is delivered with 3 nodes by default. Adding read replicas is planned.
-- **Enterprise**: the cluster is delivered with 6 nodes by default. Adding read replicas is planned.
-
-#### License type
-
-Each cluster is provided with the M3db Community (GPL) license.
-
-If any, license cost is included inside the service plans. You can't bring your own licenses.
-
-### Hardware resources
-
-For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/en-gb/public-cloud/prices/#9718).
-
-### Features
-
-#### Network
-
-Public as well as private networking (vRack) can be used for all the offers.
-
-Ingress and Egress traffic are included in the service plans and unmetered.
-
-The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
-
-##### Private network considerations
-
-Here are some considerations to take into account when using private network:
-
-- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
-- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
-- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
-- OpenStack subnets routes announcement will not be applied to your services.
-- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
-
-##### Authorised IPs
-
-Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable.
-
-#### Backups
-
-*Essential* plan clusters are automatically backed up daily. Backup retention is 1 day.
-
-*Business* plan clusters are automatically backed up daily. Backup retention is 6 days.
-
-*Enterprise* plan clusters are automatically backed up daily. Backup retention is 13 days.
-
-See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/databases_05_automated_backups) for more information.
-
-#### Logs and metrics
-
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your M3db logs in Opensearch and metrics in Dashboards service. See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
-
-- **Logs retention**: 1000 lines of logs
-- **Metrics retention**: 1 calendar month
-
-Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
-
-## We want your feedback!
-
-We would love to help answer questions and appreciate any feedback you may have.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/en-gb/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
diff --git a/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.en-ie.md
deleted file mode 100644
index 74d2fed38cc..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.en-ie.md
+++ /dev/null
@@ -1,121 +0,0 @@
----
-title: M3db - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for M3db
-updated: 2025-02-19
----
-
-## Objective
-
-This page provides the technical capabilities and limitations of the Public Cloud Databases M3db offer.
-
-We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
-
-## Capabilities and limitations
-
-### Supported regions and multi-AZ
-
-The Public Cloud Databases offer is available in the following regions:
-
-- `BHS` (Beauharnois, Canada)
-- `DE` (Frankfurt, Germany)
-- `GRA` (Gravelines, France)
-- `SBG` (Strasbourg, France)
-- `SGP` (Singapore, Singapore)
-- `UK` (London, United Kingdom)
-- `WAW` (Warsaw, Poland)
-
-Entire database instances have to be in the same region. Multi-AZ is currently not supported.
-
-### M3db versions
-
-The Public Cloud Databases offer supports M3db version 1.5.
-
-Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. M3db recommends always installing and using the latest stable version.
-
-### Plans
-
-Three plans are available:
-
-- *Essential*
-- *Business*
-- *Enterprise*
-
-Here is an overview of the various plans' capabilities:
-
-| Plan         | Number of nodes by default | Read replicas  |
-| ------------ | -------------------------- | -------------  |
-| *Essential*  | 1                          | No             |
-| *Business*   | 3                          | Planned        |
-| *Enterprise* | 6                          | Planned        |
-
-Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention.
-
-> [!primary]
-> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
-
-#### Nodes and replicas
-
-- **Essential**: the cluster can support at most one node.
-- **Business**: the cluster is delivered with 3 nodes by default. Adding read replicas is planned.
-- **Enterprise**: the cluster is delivered with 6 nodes by default. Adding read replicas is planned.
-
-#### License type
-
-Each cluster is provided with the M3db Community (GPL) license.
-
-If any, license cost is included inside the service plans. You can't bring your own licenses.
-
-### Hardware resources
-
-For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/en-ie/public-cloud/prices/#9718).
-
-### Features
-
-#### Network
-
-Public as well as private networking (vRack) can be used for all the offers.
-
-Ingress and Egress traffic are included in the service plans and unmetered.
-
-The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
-
-##### Private network considerations
-
-Here are some considerations to take into account when using private network:
-
-- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
-- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
-- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
-- OpenStack subnets routes announcement will not be applied to your services.
-- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
-
-##### Authorised IPs
-
-Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable.
-
-#### Backups
-
-*Essential* plan clusters are automatically backed up daily. Backup retention is 1 day.
-
-*Business* plan clusters are automatically backed up daily. Backup retention is 6 days.
-
-*Enterprise* plan clusters are automatically backed up daily. Backup retention is 13 days.
-
-See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/databases_05_automated_backups) for more information.
-
-#### Logs and metrics
-
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your M3db logs in Opensearch and metrics in Dashboards service. See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
-
-- **Logs retention**: 1000 lines of logs
-- **Metrics retention**: 1 calendar month
-
-Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
-
-## We want your feedback!
-
-We would love to help answer questions and appreciate any feedback you may have.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/en-ie/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
diff --git a/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.en-sg.md
deleted file mode 100644
index 44203843b8e..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.en-sg.md
+++ /dev/null
@@ -1,121 +0,0 @@
----
-title: M3db - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for M3db
-updated: 2025-02-19
----
-
-## Objective
-
-This page provides the technical capabilities and limitations of the Public Cloud Databases M3db offer.
-
-We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
-
-## Capabilities and limitations
-
-### Supported regions and multi-AZ
-
-The Public Cloud Databases offer is available in the following regions:
-
-- `BHS` (Beauharnois, Canada)
-- `DE` (Frankfurt, Germany)
-- `GRA` (Gravelines, France)
-- `SBG` (Strasbourg, France)
-- `SGP` (Singapore, Singapore)
-- `UK` (London, United Kingdom)
-- `WAW` (Warsaw, Poland)
-
-Entire database instances have to be in the same region. Multi-AZ is currently not supported.
-
-### M3db versions
-
-The Public Cloud Databases offer supports M3db version 1.5.
-
-Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. M3db recommends always installing and using the latest stable version.
-
-### Plans
-
-Three plans are available:
-
-- *Essential*
-- *Business*
-- *Enterprise*
-
-Here is an overview of the various plans' capabilities:
-
-| Plan         | Number of nodes by default | Read replicas  |
-| ------------ | -------------------------- | -------------  |
-| *Essential*  | 1                          | No             |
-| *Business*   | 3                          | Planned        |
-| *Enterprise* | 6                          | Planned        |
-
-Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention.
-
-> [!primary]
-> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
-
-#### Nodes and replicas
-
-- **Essential**: the cluster can support at most one node.
-- **Business**: the cluster is delivered with 3 nodes by default. Adding read replicas is planned.
-- **Enterprise**: the cluster is delivered with 6 nodes by default. Adding read replicas is planned.
-
-#### License type
-
-Each cluster is provided with the M3db Community (GPL) license.
-
-If any, license cost is included inside the service plans. You can't bring your own licenses.
-
-### Hardware resources
-
-For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/en-sg/public-cloud/prices/#9718).
-
-### Features
-
-#### Network
-
-Public as well as private networking (vRack) can be used for all the offers.
-
-Ingress and Egress traffic are included in the service plans and unmetered.
-
-The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
-
-##### Private network considerations
-
-Here are some considerations to take into account when using private network:
-
-- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
-- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
-- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
-- OpenStack subnets routes announcement will not be applied to your services.
-- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
-
-##### Authorised IPs
-
-Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable.
-
-#### Backups
-
-*Essential* plan clusters are automatically backed up daily. Backup retention is 1 day.
-
-*Business* plan clusters are automatically backed up daily. Backup retention is 6 days.
-
-*Enterprise* plan clusters are automatically backed up daily. Backup retention is 13 days.
-
-See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/databases_05_automated_backups) for more information.
-
-#### Logs and metrics
-
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your M3db logs in Opensearch and metrics in Dashboards service. See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
-
-- **Logs retention**: 1000 lines of logs
-- **Metrics retention**: 1 calendar month
-
-Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
-
-## We want your feedback!
-
-We would love to help answer questions and appreciate any feedback you may have.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/en-sg/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
diff --git a/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.en-us.md b/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.en-us.md
deleted file mode 100644
index ecaa9d6f92e..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.en-us.md
+++ /dev/null
@@ -1,121 +0,0 @@
----
-title: M3db - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for M3db
-updated: 2025-02-19
----
-
-## Objective
-
-This page provides the technical capabilities and limitations of the Public Cloud Databases M3db offer.
-
-We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
-
-## Capabilities and limitations
-
-### Supported regions and multi-AZ
-
-The Public Cloud Databases offer is available in the following regions:
-
-- `BHS` (Beauharnois, Canada)
-- `DE` (Frankfurt, Germany)
-- `GRA` (Gravelines, France)
-- `SBG` (Strasbourg, France)
-- `SGP` (Singapore, Singapore)
-- `UK` (London, United Kingdom)
-- `WAW` (Warsaw, Poland)
-
-Entire database instances have to be in the same region. Multi-AZ is currently not supported.
-
-### M3db versions
-
-The Public Cloud Databases offer supports M3db version 1.5.
-
-Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. M3db recommends always installing and using the latest stable version.
-
-### Plans
-
-Three plans are available:
-
-- *Essential*
-- *Business*
-- *Enterprise*
-
-Here is an overview of the various plans' capabilities:
-
-| Plan         | Number of nodes by default | Read replicas  |
-| ------------ | -------------------------- | -------------  |
-| *Essential*  | 1                          | No             |
-| *Business*   | 3                          | Planned        |
-| *Enterprise* | 6                          | Planned        |
-
-Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention.
-
-> [!primary]
-> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
-
-#### Nodes and replicas
-
-- **Essential**: the cluster can support at most one node.
-- **Business**: the cluster is delivered with 3 nodes by default. Adding read replicas is planned.
-- **Enterprise**: the cluster is delivered with 6 nodes by default. Adding read replicas is planned.
-
-#### License type
-
-Each cluster is provided with the M3db Community (GPL) license.
-
-If any, license cost is included inside the service plans. You can't bring your own licenses.
-
-### Hardware resources
-
-For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/en/public-cloud/prices/#9718).
-
-### Features
-
-#### Network
-
-Public as well as private networking (vRack) can be used for all the offers.
-
-Ingress and Egress traffic are included in the service plans and unmetered.
-
-The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
-
-##### Private network considerations
-
-Here are some considerations to take into account when using private network:
-
-- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
-- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
-- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
-- OpenStack subnets routes announcement will not be applied to your services.
-- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
-
-##### Authorised IPs
-
-Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable.
-
-#### Backups
-
-*Essential* plan clusters are automatically backed up daily. Backup retention is 1 day.
-
-*Business* plan clusters are automatically backed up daily. Backup retention is 6 days.
-
-*Enterprise* plan clusters are automatically backed up daily. Backup retention is 13 days.
-
-See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/databases_05_automated_backups) for more information.
-
-#### Logs and metrics
-
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your M3db logs in Opensearch and metrics in Dashboards service. See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
-
-- **Logs retention**: 1000 lines of logs
-- **Metrics retention**: 1 calendar month
-
-Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
-
-## We want your feedback!
-
-We would love to help answer questions and appreciate any feedback you may have.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/en/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
diff --git a/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.es-es.md b/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.es-es.md
deleted file mode 100644
index ec42b012538..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.es-es.md
+++ /dev/null
@@ -1,121 +0,0 @@
----
-title: M3db - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for M3db
-updated: 2025-02-19
----
-
-## Objective
-
-This page provides the technical capabilities and limitations of the Public Cloud Databases M3db offer.
-
-We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
-
-## Capabilities and limitations
-
-### Supported regions and multi-AZ
-
-The Public Cloud Databases offer is available in the following regions:
-
-- `BHS` (Beauharnois, Canada)
-- `DE` (Frankfurt, Germany)
-- `GRA` (Gravelines, France)
-- `SBG` (Strasbourg, France)
-- `SGP` (Singapore, Singapore)
-- `UK` (London, United Kingdom)
-- `WAW` (Warsaw, Poland)
-
-Entire database instances have to be in the same region. Multi-AZ is currently not supported.
-
-### M3db versions
-
-The Public Cloud Databases offer supports M3db version 1.5.
-
-Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. M3db recommends always installing and using the latest stable version.
-
-### Plans
-
-Three plans are available:
-
-- *Essential*
-- *Business*
-- *Enterprise*
-
-Here is an overview of the various plans' capabilities:
-
-| Plan         | Number of nodes by default | Read replicas  |
-| ------------ | -------------------------- | -------------  |
-| *Essential*  | 1                          | No             |
-| *Business*   | 3                          | Planned        |
-| *Enterprise* | 6                          | Planned        |
-
-Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention.
-
-> [!primary]
-> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
-
-#### Nodes and replicas
-
-- **Essential**: the cluster can support at most one node.
-- **Business**: the cluster is delivered with 3 nodes by default. Adding read replicas is planned.
-- **Enterprise**: the cluster is delivered with 6 nodes by default. Adding read replicas is planned.
-
-#### License type
-
-Each cluster is provided with the M3db Community (GPL) license.
-
-If any, license cost is included inside the service plans. You can't bring your own licenses.
-
-### Hardware resources
-
-For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/es-es/public-cloud/prices/#9718).
-
-### Features
-
-#### Network
-
-Public as well as private networking (vRack) can be used for all the offers.
-
-Ingress and Egress traffic are included in the service plans and unmetered.
-
-The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
-
-##### Private network considerations
-
-Here are some considerations to take into account when using private network:
-
-- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
-- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
-- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
-- OpenStack subnets routes announcement will not be applied to your services.
-- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
-
-##### Authorised IPs
-
-Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable.
-
-#### Backups
-
-*Essential* plan clusters are automatically backed up daily. Backup retention is 1 day.
-
-*Business* plan clusters are automatically backed up daily. Backup retention is 6 days.
-
-*Enterprise* plan clusters are automatically backed up daily. Backup retention is 13 days.
-
-See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/databases_05_automated_backups) for more information.
-
-#### Logs and metrics
-
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your M3db logs in Opensearch and metrics in Dashboards service. See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
-
-- **Logs retention**: 1000 lines of logs
-- **Metrics retention**: 1 calendar month
-
-Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
-
-## We want your feedback!
-
-We would love to help answer questions and appreciate any feedback you may have.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/es-es/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
diff --git a/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.es-us.md b/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.es-us.md
deleted file mode 100644
index 15c357c2eb5..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.es-us.md
+++ /dev/null
@@ -1,121 +0,0 @@
----
-title: M3db - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for M3db
-updated: 2025-02-19
----
-
-## Objective
-
-This page provides the technical capabilities and limitations of the Public Cloud Databases M3db offer.
-
-We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
-
-## Capabilities and limitations
-
-### Supported regions and multi-AZ
-
-The Public Cloud Databases offer is available in the following regions:
-
-- `BHS` (Beauharnois, Canada)
-- `DE` (Frankfurt, Germany)
-- `GRA` (Gravelines, France)
-- `SBG` (Strasbourg, France)
-- `SGP` (Singapore, Singapore)
-- `UK` (London, United Kingdom)
-- `WAW` (Warsaw, Poland)
-
-Entire database instances have to be in the same region. Multi-AZ is currently not supported.
-
-### M3db versions
-
-The Public Cloud Databases offer supports M3db version 1.5.
-
-Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. M3db recommends always installing and using the latest stable version.
-
-### Plans
-
-Three plans are available:
-
-- *Essential*
-- *Business*
-- *Enterprise*
-
-Here is an overview of the various plans' capabilities:
-
-| Plan         | Number of nodes by default | Read replicas  |
-| ------------ | -------------------------- | -------------  |
-| *Essential*  | 1                          | No             |
-| *Business*   | 3                          | Planned        |
-| *Enterprise* | 6                          | Planned        |
-
-Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention.
-
-> [!primary]
-> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
-
-#### Nodes and replicas
-
-- **Essential**: the cluster can support at most one node.
-- **Business**: the cluster is delivered with 3 nodes by default. Adding read replicas is planned.
-- **Enterprise**: the cluster is delivered with 6 nodes by default. Adding read replicas is planned.
-
-#### License type
-
-Each cluster is provided with the M3db Community (GPL) license.
-
-If any, license cost is included inside the service plans. You can't bring your own licenses.
-
-### Hardware resources
-
-For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/es/public-cloud/prices/#9718).
-
-### Features
-
-#### Network
-
-Public as well as private networking (vRack) can be used for all the offers.
-
-Ingress and Egress traffic are included in the service plans and unmetered.
-
-The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
-
-##### Private network considerations
-
-Here are some considerations to take into account when using private network:
-
-- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
-- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
-- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
-- OpenStack subnets routes announcement will not be applied to your services.
-- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
-
-##### Authorised IPs
-
-Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable.
-
-#### Backups
-
-*Essential* plan clusters are automatically backed up daily. Backup retention is 1 day.
-
-*Business* plan clusters are automatically backed up daily. Backup retention is 6 days.
-
-*Enterprise* plan clusters are automatically backed up daily. Backup retention is 13 days.
-
-See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/databases_05_automated_backups) for more information.
-
-#### Logs and metrics
-
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your M3db logs in Opensearch and metrics in Dashboards service. See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
-
-- **Logs retention**: 1000 lines of logs
-- **Metrics retention**: 1 calendar month
-
-Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
-
-## We want your feedback!
-
-We would love to help answer questions and appreciate any feedback you may have.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/es/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
diff --git a/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.fr-ca.md
deleted file mode 100644
index 0f21c1a59ea..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.fr-ca.md
+++ /dev/null
@@ -1,121 +0,0 @@
----
-title: M3db - Capacités et limitations (EN)
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for M3db
-updated: 2025-02-19
----
-
-## Objective
-
-This page provides the technical capabilities and limitations of the Public Cloud Databases M3db offer.
-
-We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
-
-## Capabilities and limitations
-
-### Supported regions and multi-AZ
-
-The Public Cloud Databases offer is available in the following regions:
-
-- `BHS` (Beauharnois, Canada)
-- `DE` (Frankfurt, Germany)
-- `GRA` (Gravelines, France)
-- `SBG` (Strasbourg, France)
-- `SGP` (Singapore, Singapore)
-- `UK` (London, United Kingdom)
-- `WAW` (Warsaw, Poland)
-
-Entire database instances have to be in the same region. Multi-AZ is currently not supported.
-
-### M3db versions
-
-The Public Cloud Databases offer supports M3db version 1.5.
-
-Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. M3db recommends always installing and using the latest stable version.
-
-### Plans
-
-Three plans are available:
-
-- *Essential*
-- *Business*
-- *Enterprise*
-
-Here is an overview of the various plans' capabilities:
-
-| Plan         | Number of nodes by default | Read replicas  |
-| ------------ | -------------------------- | -------------  |
-| *Essential*  | 1                          | No             |
-| *Business*   | 3                          | Planned        |
-| *Enterprise* | 6                          | Planned        |
-
-Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention.
-
-> [!primary]
-> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
-
-#### Nodes and replicas
-
-- **Essential**: the cluster can support at most one node.
-- **Business**: the cluster is delivered with 3 nodes by default. Adding read replicas is planned.
-- **Enterprise**: the cluster is delivered with 6 nodes by default. Adding read replicas is planned.
-
-#### License type
-
-Each cluster is provided with the M3db Community (GPL) license.
-
-If any, license cost is included inside the service plans. You can't bring your own licenses.
-
-### Hardware resources
-
-For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/fr-ca/public-cloud/prices/#9718).
-
-### Features
-
-#### Network
-
-Public as well as private networking (vRack) can be used for all the offers.
-
-Ingress and Egress traffic are included in the service plans and unmetered.
-
-The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
-
-##### Private network considerations
-
-Here are some considerations to take into account when using private network:
-
-- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
-- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
-- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
-- OpenStack subnets routes announcement will not be applied to your services.
-- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
-
-##### Authorised IPs
-
-Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable.
-
-#### Backups
-
-*Essential* plan clusters are automatically backed up daily. Backup retention is 1 day.
-
-*Business* plan clusters are automatically backed up daily. Backup retention is 6 days.
-
-*Enterprise* plan clusters are automatically backed up daily. Backup retention is 13 days.
-
-See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/databases_05_automated_backups) for more information.
-
-#### Logs and metrics
-
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your M3db logs in Opensearch and metrics in Dashboards service. See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
-
-- **Logs retention**: 1000 lines of logs
-- **Metrics retention**: 1 calendar month
-
-Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
-
-## We want your feedback!
-
-We would love to help answer questions and appreciate any feedback you may have.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/fr-ca/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
diff --git a/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.fr-fr.md
deleted file mode 100644
index f109473809d..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.fr-fr.md
+++ /dev/null
@@ -1,121 +0,0 @@
----
-title: M3db - Capacités et limitations (EN)
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for M3db
-updated: 2025-02-19
----
-
-## Objective
-
-This page provides the technical capabilities and limitations of the Public Cloud Databases M3db offer.
-
-We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
-
-## Capabilities and limitations
-
-### Supported regions and multi-AZ
-
-The Public Cloud Databases offer is available in the following regions:
-
-- `BHS` (Beauharnois, Canada)
-- `DE` (Frankfurt, Germany)
-- `GRA` (Gravelines, France)
-- `SBG` (Strasbourg, France)
-- `SGP` (Singapore, Singapore)
-- `UK` (London, United Kingdom)
-- `WAW` (Warsaw, Poland)
-
-Entire database instances have to be in the same region. Multi-AZ is currently not supported.
-
-### M3db versions
-
-The Public Cloud Databases offer supports M3db version 1.5.
-
-Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. M3db recommends always installing and using the latest stable version.
-
-### Plans
-
-Three plans are available:
-
-- *Essential*
-- *Business*
-- *Enterprise*
-
-Here is an overview of the various plans' capabilities:
-
-| Plan         | Number of nodes by default | Read replicas  |
-| ------------ | -------------------------- | -------------  |
-| *Essential*  | 1                          | No             |
-| *Business*   | 3                          | Planned        |
-| *Enterprise* | 6                          | Planned        |
-
-Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention.
-
-> [!primary]
-> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
-
-#### Nodes and replicas
-
-- **Essential**: the cluster can support at most one node.
-- **Business**: the cluster is delivered with 3 nodes by default. Adding read replicas is planned.
-- **Enterprise**: the cluster is delivered with 6 nodes by default. Adding read replicas is planned.
-
-#### License type
-
-Each cluster is provided with the M3db Community (GPL) license.
-
-If any, license cost is included inside the service plans. You can't bring your own licenses.
-
-### Hardware resources
-
-For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/fr/public-cloud/prices/#9718).
-
-### Features
-
-#### Network
-
-Public as well as private networking (vRack) can be used for all the offers.
-
-Ingress and Egress traffic are included in the service plans and unmetered.
-
-The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
-
-##### Private network considerations
-
-Here are some considerations to take into account when using private network:
-
-- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
-- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
-- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
-- OpenStack subnets routes announcement will not be applied to your services.
-- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
-
-##### Authorised IPs
-
-Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable.
-
-#### Backups
-
-*Essential* plan clusters are automatically backed up daily. Backup retention is 1 day.
-
-*Business* plan clusters are automatically backed up daily. Backup retention is 6 days.
-
-*Enterprise* plan clusters are automatically backed up daily. Backup retention is 13 days.
-
-See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/databases_05_automated_backups) for more information.
-
-#### Logs and metrics
-
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your M3db logs in Opensearch and metrics in Dashboards service. See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
-
-- **Logs retention**: 1000 lines of logs
-- **Metrics retention**: 1 calendar month
-
-Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
-
-## We want your feedback!
-
-We would love to help answer questions and appreciate any feedback you may have.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/fr/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
diff --git a/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.it-it.md b/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.it-it.md
deleted file mode 100644
index 08a5a028e1e..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.it-it.md
+++ /dev/null
@@ -1,121 +0,0 @@
----
-title: M3db - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for M3db
-updated: 2025-02-19
----
-
-## Objective
-
-This page provides the technical capabilities and limitations of the Public Cloud Databases M3db offer.
-
-We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
-
-## Capabilities and limitations
-
-### Supported regions and multi-AZ
-
-The Public Cloud Databases offer is available in the following regions:
-
-- `BHS` (Beauharnois, Canada)
-- `DE` (Frankfurt, Germany)
-- `GRA` (Gravelines, France)
-- `SBG` (Strasbourg, France)
-- `SGP` (Singapore, Singapore)
-- `UK` (London, United Kingdom)
-- `WAW` (Warsaw, Poland)
-
-Entire database instances have to be in the same region. Multi-AZ is currently not supported.
-
-### M3db versions
-
-The Public Cloud Databases offer supports M3db version 1.5.
-
-Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. M3db recommends always installing and using the latest stable version.
-
-### Plans
-
-Three plans are available:
-
-- *Essential*
-- *Business*
-- *Enterprise*
-
-Here is an overview of the various plans' capabilities:
-
-| Plan         | Number of nodes by default | Read replicas  |
-| ------------ | -------------------------- | -------------  |
-| *Essential*  | 1                          | No             |
-| *Business*   | 3                          | Planned        |
-| *Enterprise* | 6                          | Planned        |
-
-Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention.
-
-> [!primary]
-> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
-
-#### Nodes and replicas
-
-- **Essential**: the cluster can support at most one node.
-- **Business**: the cluster is delivered with 3 nodes by default. Adding read replicas is planned.
-- **Enterprise**: the cluster is delivered with 6 nodes by default. Adding read replicas is planned.
-
-#### License type
-
-Each cluster is provided with the M3db Community (GPL) license.
-
-If any, license cost is included inside the service plans. You can't bring your own licenses.
-
-### Hardware resources
-
-For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/it/public-cloud/prices/#9718).
-
-### Features
-
-#### Network
-
-Public as well as private networking (vRack) can be used for all the offers.
-
-Ingress and Egress traffic are included in the service plans and unmetered.
-
-The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
-
-##### Private network considerations
-
-Here are some considerations to take into account when using private network:
-
-- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
-- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
-- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
-- OpenStack subnets routes announcement will not be applied to your services.
-- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
-
-##### Authorised IPs
-
-Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable.
-
-#### Backups
-
-*Essential* plan clusters are automatically backed up daily. Backup retention is 1 day.
-
-*Business* plan clusters are automatically backed up daily. Backup retention is 6 days.
-
-*Enterprise* plan clusters are automatically backed up daily. Backup retention is 13 days.
-
-See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/databases_05_automated_backups) for more information.
-
-#### Logs and metrics
-
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your M3db logs in Opensearch and metrics in Dashboards service. See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
-
-- **Logs retention**: 1000 lines of logs
-- **Metrics retention**: 1 calendar month
-
-Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
-
-## We want your feedback!
-
-We would love to help answer questions and appreciate any feedback you may have.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/it/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
diff --git a/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.pl-pl.md
deleted file mode 100644
index a1f7e4ec56a..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.pl-pl.md
+++ /dev/null
@@ -1,121 +0,0 @@
----
-title: M3db - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for M3db
-updated: 2025-02-19
----
-
-## Objective
-
-This page provides the technical capabilities and limitations of the Public Cloud Databases M3db offer.
-
-We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
-
-## Capabilities and limitations
-
-### Supported regions and multi-AZ
-
-The Public Cloud Databases offer is available in the following regions:
-
-- `BHS` (Beauharnois, Canada)
-- `DE` (Frankfurt, Germany)
-- `GRA` (Gravelines, France)
-- `SBG` (Strasbourg, France)
-- `SGP` (Singapore, Singapore)
-- `UK` (London, United Kingdom)
-- `WAW` (Warsaw, Poland)
-
-Entire database instances have to be in the same region. Multi-AZ is currently not supported.
-
-### M3db versions
-
-The Public Cloud Databases offer supports M3db version 1.5.
-
-Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. M3db recommends always installing and using the latest stable version.
-
-### Plans
-
-Three plans are available:
-
-- *Essential*
-- *Business*
-- *Enterprise*
-
-Here is an overview of the various plans' capabilities:
-
-| Plan         | Number of nodes by default | Read replicas  |
-| ------------ | -------------------------- | -------------  |
-| *Essential*  | 1                          | No             |
-| *Business*   | 3                          | Planned        |
-| *Enterprise* | 6                          | Planned        |
-
-Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention.
-
-> [!primary]
-> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
-
-#### Nodes and replicas
-
-- **Essential**: the cluster can support at most one node.
-- **Business**: the cluster is delivered with 3 nodes by default. Adding read replicas is planned.
-- **Enterprise**: the cluster is delivered with 6 nodes by default. Adding read replicas is planned.
-
-#### License type
-
-Each cluster is provided with the M3db Community (GPL) license.
-
-If any, license cost is included inside the service plans. You can't bring your own licenses.
-
-### Hardware resources
-
-For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/pl/public-cloud/prices/#9718).
-
-### Features
-
-#### Network
-
-Public as well as private networking (vRack) can be used for all the offers.
-
-Ingress and Egress traffic are included in the service plans and unmetered.
-
-The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
-
-##### Private network considerations
-
-Here are some considerations to take into account when using private network:
-
-- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
-- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
-- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
-- OpenStack subnets routes announcement will not be applied to your services.
-- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
-
-##### Authorised IPs
-
-Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable.
-
-#### Backups
-
-*Essential* plan clusters are automatically backed up daily. Backup retention is 1 day.
-
-*Business* plan clusters are automatically backed up daily. Backup retention is 6 days.
-
-*Enterprise* plan clusters are automatically backed up daily. Backup retention is 13 days.
-
-See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/databases_05_automated_backups) for more information.
-
-#### Logs and metrics
-
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your M3db logs in Opensearch and metrics in Dashboards service. See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
-
-- **Logs retention**: 1000 lines of logs
-- **Metrics retention**: 1 calendar month
-
-Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
-
-## We want your feedback!
-
-We would love to help answer questions and appreciate any feedback you may have.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/pl/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
diff --git a/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.pt-pt.md
deleted file mode 100644
index dcbe38fde5b..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/guide.pt-pt.md
+++ /dev/null
@@ -1,121 +0,0 @@
----
-title: M3db - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for M3db
-updated: 2025-02-19
----
-
-## Objective
-
-This page provides the technical capabilities and limitations of the Public Cloud Databases M3db offer.
-
-We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
-
-## Capabilities and limitations
-
-### Supported regions and multi-AZ
-
-The Public Cloud Databases offer is available in the following regions:
-
-- `BHS` (Beauharnois, Canada)
-- `DE` (Frankfurt, Germany)
-- `GRA` (Gravelines, France)
-- `SBG` (Strasbourg, France)
-- `SGP` (Singapore, Singapore)
-- `UK` (London, United Kingdom)
-- `WAW` (Warsaw, Poland)
-
-Entire database instances have to be in the same region. Multi-AZ is currently not supported.
-
-### M3db versions
-
-The Public Cloud Databases offer supports M3db version 1.5.
-
-Please refer to the [DBMS lifecycle policy guide](/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy) for recommendations on version upgrades and end of life announcements of major versions. M3db recommends always installing and using the latest stable version.
-
-### Plans
-
-Three plans are available:
-
-- *Essential*
-- *Business*
-- *Enterprise*
-
-Here is an overview of the various plans' capabilities:
-
-| Plan         | Number of nodes by default | Read replicas  |
-| ------------ | -------------------------- | -------------  |
-| *Essential*  | 1                          | No             |
-| *Business*   | 3                          | Planned        |
-| *Enterprise* | 6                          | Planned        |
-
-Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention.
-
-> [!primary]
-> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
-
-#### Nodes and replicas
-
-- **Essential**: the cluster can support at most one node.
-- **Business**: the cluster is delivered with 3 nodes by default. Adding read replicas is planned.
-- **Enterprise**: the cluster is delivered with 6 nodes by default. Adding read replicas is planned.
-
-#### License type
-
-Each cluster is provided with the M3db Community (GPL) license.
-
-If any, license cost is included inside the service plans. You can't bring your own licenses.
-
-### Hardware resources
-
-For detailed information about node types and pricing, please refer to the [Public Cloud pricing page](https://www.ovhcloud.com/pt/public-cloud/prices/#9718).
-
-### Features
-
-#### Network
-
-Public as well as private networking (vRack) can be used for all the offers.
-
-Ingress and Egress traffic are included in the service plans and unmetered.
-
-The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
-
-##### Private network considerations
-
-Here are some considerations to take into account when using private network:
-
-- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
-- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
-- Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
-- OpenStack subnets routes announcement will not be applied to your services.
-- You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
-
-##### Authorised IPs
-
-Once your service is up and running, you will be able to specify IP addresses (or CIDR blocks) to authorise incoming traffic. Until then, your service will be unreachable.
-
-#### Backups
-
-*Essential* plan clusters are automatically backed up daily. Backup retention is 1 day.
-
-*Business* plan clusters are automatically backed up daily. Backup retention is 6 days.
-
-*Enterprise* plan clusters are automatically backed up daily. Backup retention is 13 days.
-
-See the [Automated Backups guide](/pages/public_cloud/public_cloud_databases/databases_05_automated_backups) for more information.
-
-#### Logs and metrics
-
-Logs and metrics are available through the Control Panel, API and can be forwarded to Logs Data Platform. Additionally, cross service integration can be configured to leverage your logs and metrics in other Public Cloud Database services. You could then view your M3db logs in Opensearch and metrics in Dashboards service. See the [Cross Service Integration documentation](/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration) for more information. For more details on logs forwarding, see the [Public Cloud Databases - How to setup logs forwarding](/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer) guide.
-
-- **Logs retention**: 1000 lines of logs
-- **Metrics retention**: 1 calendar month
-
-Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
-
-## We want your feedback!
-
-We would love to help answer questions and appreciate any feedback you may have.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/pt/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
diff --git a/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/meta.yaml b/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/meta.yaml
deleted file mode 100755
index af48866e59c..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3db_01_capabilities/meta.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-id: 5b4461f5-134c-4834-96d6-dbdfc645a63e
-full_slug: public-cloud-databases-m3db-capabilities
-engine: m3db
-section: dashboard
-reference_category: public-cloud-databases-m3db-guides
\ No newline at end of file
diff --git a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.de-de.md b/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.de-de.md
deleted file mode 100644
index 0c805efa6e0..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.de-de.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-title: M3db - Configure your M3db instance to accept incoming connections
-excerpt: Find out how to configure your M3db instance to accept incoming connections
-updated: 2022-05-12
----
-
-## Objective
-
-Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
-
-**This guide explains how to configure your M3db instance to accept incoming connections.**
-
-## Requirements
-
-- A [Public Cloud project](https://www.ovhcloud.com/de/public-cloud/) in your OVHcloud account
-- Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.de/&ovhSubsidiary=de)
-- A M3db database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-
-## Instructions
-
-### Configure your M3db instance to accept incoming connections
-
-Before making a connection, we need to verify that our M3db instance is correctly configured.
-
-Log in to your [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.de/&ovhSubsidiary=de) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your M3db instance.
-
-#### Step 1: Verify your user roles and password
-
-Select the `Users`{.action} tab. Verify that you have a user with sufficient rights and a configured password. If you don't remember the user's password, you can either create a new user or regenerate the password of an existing user.
-
-> [!warning]
-> Be careful! By doing so you will need to update all the places where you already use this user/password pair.
->
-
-![User table](images/m3db_02_prepare_for_incoming_connections-20220530101005205.png){.thumbnail}
-
-You can add more users by clicking on the button `Add user`{.action}.
-
-![Add user](images/m3db_02_prepare_for_incoming_connections-20220530101111115.png){.thumbnail}
-
-Enter a username *(required)* and a group *(optional)*, then click `Create User`{.action}.
-
-> [!primary]
-> You can delete a user or regenerate a password via the `...`{.action} button in the `Users & Roles` table.
-
-#### Step 2: Authorise incoming connections from the M3db client
-
-> [!warning]
-> For security reasons the default network configuration doesn't allow any incoming connections. It is thus critical you authorise the suitable IP addresses in order to successfully access your database.
-
-In this step, select the `Authorised IPs`{.action} tab. IP addresses must be authorised here before they can connect to your database.
-
-Clicking on `Add an IP address or IP address block (CIDR)`{.action} opens a new window in which you can add single IP addresses or blocks to allow access to the database.
-
-![Add an IP](images/ip_authorize.png){.thumbnail}
-
-You can edit and retract database access via the `...`{.action} button in the IP table.
-
-> [!primary]
->
-> If you want to allow connections from the outside, you can enter the IP 0.0.0.0/0. Please use it carefully.
->
-
-#### Collect required information
-
-Select the `General information`{.action} tab to find the required login credentials in the `Login informations` section.
-
-![Login information tab](images/m3db_02_prepare_for_incoming_connections-20220530101418212.png){.thumbnail}
-
-Select the `Namespaces`{.action} tab to get the namespaces information.
-
-![Namespaces table](images/m3db_02_prepare_for_incoming_connections-20220530101803294.png){.thumbnail}
-
-> [!primary]
->
-> To create a new namespaces click on `Add a namespace`{.action} then fill the form :
->
-> ![Create new namespace](images/m3db_02_prepare_for_incoming_connections-20220530102131903.png){.thumbnail}
-
-Select the `Users`{.action} tab to get the username.
-
-![User table](images/m3db_02_prepare_for_incoming_connections-20220530101005205.png){.thumbnail}
-
-## Go further
-
-Visit the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/m3db) to find how to connect to your database with several languages.
-
-Visit our dedicated Discord channel: <https://discord.gg/ovhcloud>. Ask questions, provide feedback and interact directly with the team that builds our databases services.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/de/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Join our community of users on <https://community.ovh.com/en/>.
diff --git a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.en-asia.md b/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.en-asia.md
deleted file mode 100644
index 6c56dc72992..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.en-asia.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-title: M3db - Configure your M3db instance to accept incoming connections
-excerpt: Find out how to configure your M3db instance to accept incoming connections
-updated: 2022-05-12
----
-
-## Objective
-
-Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
-
-**This guide explains how to configure your M3db instance to accept incoming connections.**
-
-## Requirements
-
-- A [Public Cloud project](https://www.ovhcloud.com/asia/public-cloud/) in your OVHcloud account
-- Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/asia/&ovhSubsidiary=asia)
-- A M3db database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-
-## Instructions
-
-### Configure your M3db instance to accept incoming connections
-
-Before making a connection, we need to verify that our M3db instance is correctly configured.
-
-Log in to your [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/asia/&ovhSubsidiary=asia) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your M3db instance.
-
-#### Step 1: Verify your user roles and password
-
-Select the `Users`{.action} tab. Verify that you have a user with sufficient rights and a configured password. If you don't remember the user's password, you can either create a new user or regenerate the password of an existing user.
-
-> [!warning]
-> Be careful! By doing so you will need to update all the places where you already use this user/password pair.
->
-
-![User table](images/m3db_02_prepare_for_incoming_connections-20220530101005205.png){.thumbnail}
-
-You can add more users by clicking on the button `Add user`{.action}.
-
-![Add user](images/m3db_02_prepare_for_incoming_connections-20220530101111115.png){.thumbnail}
-
-Enter a username *(required)* and a group *(optional)*, then click `Create User`{.action}.
-
-> [!primary]
-> You can delete a user or regenerate a password via the `...`{.action} button in the `Users & Roles` table.
-
-#### Step 2: Authorise incoming connections from the M3db client
-
-> [!warning]
-> For security reasons the default network configuration doesn't allow any incoming connections. It is thus critical you authorise the suitable IP addresses in order to successfully access your database.
-
-In this step, select the `Authorised IPs`{.action} tab. IP addresses must be authorised here before they can connect to your database.
-
-Clicking on `Add an IP address or IP address block (CIDR)`{.action} opens a new window in which you can add single IP addresses or blocks to allow access to the database.
-
-![Add an IP](images/ip_authorize.png){.thumbnail}
-
-You can edit and retract database access via the `...`{.action} button in the IP table.
-
-> [!primary]
->
-> If you want to allow connections from the outside, you can enter the IP 0.0.0.0/0. Please use it carefully.
->
-
-#### Collect required information
-
-Select the `General information`{.action} tab to find the required login credentials in the `Login informations` section.
-
-![Login information tab](images/m3db_02_prepare_for_incoming_connections-20220530101418212.png){.thumbnail}
-
-Select the `Namespaces`{.action} tab to get the namespaces information.
-
-![Namespaces table](images/m3db_02_prepare_for_incoming_connections-20220530101803294.png){.thumbnail}
-
-> [!primary]
->
-> To create a new namespaces click on `Add a namespace`{.action} then fill the form :
->
-> ![Create new namespace](images/m3db_02_prepare_for_incoming_connections-20220530102131903.png){.thumbnail}
-
-Select the `Users`{.action} tab to get the username.
-
-![User table](images/m3db_02_prepare_for_incoming_connections-20220530101005205.png){.thumbnail}
-
-## Go further
-
-Visit the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/m3db) to find how to connect to your database with several languages.
-
-Visit our dedicated Discord channel: <https://discord.gg/ovhcloud>. Ask questions, provide feedback and interact directly with the team that builds our databases services.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/asia/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Join our community of users on <https://community.ovh.com/en/>.
diff --git a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.en-au.md b/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.en-au.md
deleted file mode 100644
index 10ae2820adf..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.en-au.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-title: M3db - Configure your M3db instance to accept incoming connections
-excerpt: Find out how to configure your M3db instance to accept incoming connections
-updated: 2022-05-12
----
-
-## Objective
-
-Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
-
-**This guide explains how to configure your M3db instance to accept incoming connections.**
-
-## Requirements
-
-- A [Public Cloud project](https://www.ovhcloud.com/en-au/public-cloud/) in your OVHcloud account
-- Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com.au/&ovhSubsidiary=au)
-- A M3db database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-
-## Instructions
-
-### Configure your M3db instance to accept incoming connections
-
-Before making a connection, we need to verify that our M3db instance is correctly configured.
-
-Log in to your [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com.au/&ovhSubsidiary=au) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your M3db instance.
-
-#### Step 1: Verify your user roles and password
-
-Select the `Users`{.action} tab. Verify that you have a user with sufficient rights and a configured password. If you don't remember the user's password, you can either create a new user or regenerate the password of an existing user.
-
-> [!warning]
-> Be careful! By doing so you will need to update all the places where you already use this user/password pair.
->
-
-![User table](images/m3db_02_prepare_for_incoming_connections-20220530101005205.png){.thumbnail}
-
-You can add more users by clicking on the button `Add user`{.action}.
-
-![Add user](images/m3db_02_prepare_for_incoming_connections-20220530101111115.png){.thumbnail}
-
-Enter a username *(required)* and a group *(optional)*, then click `Create User`{.action}.
-
-> [!primary]
-> You can delete a user or regenerate a password via the `...`{.action} button in the `Users & Roles` table.
-
-#### Step 2: Authorise incoming connections from the M3db client
-
-> [!warning]
-> For security reasons the default network configuration doesn't allow any incoming connections. It is thus critical you authorise the suitable IP addresses in order to successfully access your database.
-
-In this step, select the `Authorised IPs`{.action} tab. IP addresses must be authorised here before they can connect to your database.
-
-Clicking on `Add an IP address or IP address block (CIDR)`{.action} opens a new window in which you can add single IP addresses or blocks to allow access to the database.
-
-![Add an IP](images/ip_authorize.png){.thumbnail}
-
-You can edit and retract database access via the `...`{.action} button in the IP table.
-
-> [!primary]
->
-> If you want to allow connections from the outside, you can enter the IP 0.0.0.0/0. Please use it carefully.
->
-
-#### Collect required information
-
-Select the `General information`{.action} tab to find the required login credentials in the `Login informations` section.
-
-![Login information tab](images/m3db_02_prepare_for_incoming_connections-20220530101418212.png){.thumbnail}
-
-Select the `Namespaces`{.action} tab to get the namespaces information.
-
-![Namespaces table](images/m3db_02_prepare_for_incoming_connections-20220530101803294.png){.thumbnail}
-
-> [!primary]
->
-> To create a new namespaces click on `Add a namespace`{.action} then fill the form :
->
-> ![Create new namespace](images/m3db_02_prepare_for_incoming_connections-20220530102131903.png){.thumbnail}
-
-Select the `Users`{.action} tab to get the username.
-
-![User table](images/m3db_02_prepare_for_incoming_connections-20220530101005205.png){.thumbnail}
-
-## Go further
-
-Visit the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/m3db) to find how to connect to your database with several languages.
-
-Visit our dedicated Discord channel: <https://discord.gg/ovhcloud>. Ask questions, provide feedback and interact directly with the team that builds our databases services.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/en-au/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Join our community of users on <https://community.ovh.com/en/>.
diff --git a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.en-ca.md b/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.en-ca.md
deleted file mode 100644
index bdd76b85d0e..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.en-ca.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-title: M3db - Configure your M3db instance to accept incoming connections
-excerpt: Find out how to configure your M3db instance to accept incoming connections
-updated: 2022-05-12
----
-
-## Objective
-
-Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
-
-**This guide explains how to configure your M3db instance to accept incoming connections.**
-
-## Requirements
-
-- A [Public Cloud project](https://www.ovhcloud.com/en-ca/public-cloud/) in your OVHcloud account
-- Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/ca/en/&ovhSubsidiary=ca)
-- A M3db database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-
-## Instructions
-
-### Configure your M3db instance to accept incoming connections
-
-Before making a connection, we need to verify that our M3db instance is correctly configured.
-
-Log in to your [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/ca/en/&ovhSubsidiary=ca) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your M3db instance.
-
-#### Step 1: Verify your user roles and password
-
-Select the `Users`{.action} tab. Verify that you have a user with sufficient rights and a configured password. If you don't remember the user's password, you can either create a new user or regenerate the password of an existing user.
-
-> [!warning]
-> Be careful! By doing so you will need to update all the places where you already use this user/password pair.
->
-
-![User table](images/m3db_02_prepare_for_incoming_connections-20220530101005205.png){.thumbnail}
-
-You can add more users by clicking on the button `Add user`{.action}.
-
-![Add user](images/m3db_02_prepare_for_incoming_connections-20220530101111115.png){.thumbnail}
-
-Enter a username *(required)* and a group *(optional)*, then click `Create User`{.action}.
-
-> [!primary]
-> You can delete a user or regenerate a password via the `...`{.action} button in the `Users & Roles` table.
-
-#### Step 2: Authorise incoming connections from the M3db client
-
-> [!warning]
-> For security reasons the default network configuration doesn't allow any incoming connections. It is thus critical you authorise the suitable IP addresses in order to successfully access your database.
-
-In this step, select the `Authorised IPs`{.action} tab. IP addresses must be authorised here before they can connect to your database.
-
-Clicking on `Add an IP address or IP address block (CIDR)`{.action} opens a new window in which you can add single IP addresses or blocks to allow access to the database.
-
-![Add an IP](images/ip_authorize.png){.thumbnail}
-
-You can edit and retract database access via the `...`{.action} button in the IP table.
-
-> [!primary]
->
-> If you want to allow connections from the outside, you can enter the IP 0.0.0.0/0. Please use it carefully.
->
-
-#### Collect required information
-
-Select the `General information`{.action} tab to find the required login credentials in the `Login informations` section.
-
-![Login information tab](images/m3db_02_prepare_for_incoming_connections-20220530101418212.png){.thumbnail}
-
-Select the `Namespaces`{.action} tab to get the namespaces information.
-
-![Namespaces table](images/m3db_02_prepare_for_incoming_connections-20220530101803294.png){.thumbnail}
-
-> [!primary]
->
-> To create a new namespaces click on `Add a namespace`{.action} then fill the form :
->
-> ![Create new namespace](images/m3db_02_prepare_for_incoming_connections-20220530102131903.png){.thumbnail}
-
-Select the `Users`{.action} tab to get the username.
-
-![User table](images/m3db_02_prepare_for_incoming_connections-20220530101005205.png){.thumbnail}
-
-## Go further
-
-Visit the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/m3db) to find how to connect to your database with several languages.
-
-Visit our dedicated Discord channel: <https://discord.gg/ovhcloud>. Ask questions, provide feedback and interact directly with the team that builds our databases services.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/en-ca/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Join our community of users on <https://community.ovh.com/en/>.
diff --git a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.en-gb.md b/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.en-gb.md
deleted file mode 100644
index c88c5d64c02..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.en-gb.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-title: M3db - Configure your M3db instance to accept incoming connections
-excerpt: Find out how to configure your M3db instance to accept incoming connections
-updated: 2022-05-12
----
-
-## Objective
-
-Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
-
-**This guide explains how to configure your M3db instance to accept incoming connections.**
-
-## Requirements
-
-- A [Public Cloud project](https://www.ovhcloud.com/en-gb/public-cloud/) in your OVHcloud account
-- Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.co.uk/&ovhSubsidiary=GB)
-- A M3db database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-
-## Instructions
-
-### Configure your M3db instance to accept incoming connections
-
-Before making a connection, we need to verify that our M3db instance is correctly configured.
-
-Log in to your [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.co.uk/&ovhSubsidiary=GB) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your M3db instance.
-
-#### Step 1: Verify your user roles and password
-
-Select the `Users`{.action} tab. Verify that you have a user with sufficient rights and a configured password. If you don't remember the user's password, you can either create a new user or regenerate the password of an existing user.
-
-> [!warning]
-> Be careful! By doing so you will need to update all the places where you already use this user/password pair.
->
-
-![User table](images/m3db_02_prepare_for_incoming_connections-20220530101005205.png){.thumbnail}
-
-You can add more users by clicking on the button `Add user`{.action}.
-
-![Add user](images/m3db_02_prepare_for_incoming_connections-20220530101111115.png){.thumbnail}
-
-Enter a username *(required)* and a group *(optional)*, then click `Create User`{.action}.
-
-> [!primary]
-> You can delete a user or regenerate a password via the `...`{.action} button in the `Users & Roles` table.
-
-#### Step 2: Authorise incoming connections from the M3db client
-
-> [!warning]
-> For security reasons the default network configuration doesn't allow any incoming connections. It is thus critical you authorise the suitable IP addresses in order to successfully access your database.
-
-In this step, select the `Authorised IPs`{.action} tab. IP addresses must be authorised here before they can connect to your database.
-
-Clicking on `Add an IP address or IP address block (CIDR)`{.action} opens a new window in which you can add single IP addresses or blocks to allow access to the database.
-
-![Add an IP](images/ip_authorize.png){.thumbnail}
-
-You can edit and retract database access via the `...`{.action} button in the IP table.
-
-> [!primary]
->
-> If you want to allow connections from the outside, you can enter the IP 0.0.0.0/0. Please use it carefully.
->
-
-#### Collect required information
-
-Select the `General information`{.action} tab to find the required login credentials in the `Login informations` section.
-
-![Login information tab](images/m3db_02_prepare_for_incoming_connections-20220530101418212.png){.thumbnail}
-
-Select the `Namespaces`{.action} tab to get the namespaces information.
-
-![Namespaces table](images/m3db_02_prepare_for_incoming_connections-20220530101803294.png){.thumbnail}
-
-> [!primary]
->
-> To create a new namespaces click on `Add a namespace`{.action} then fill the form :
->
-> ![Create new namespace](images/m3db_02_prepare_for_incoming_connections-20220530102131903.png){.thumbnail}
-
-Select the `Users`{.action} tab to get the username.
-
-![User table](images/m3db_02_prepare_for_incoming_connections-20220530101005205.png){.thumbnail}
-
-## Go further
-
-Visit the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/m3db) to find how to connect to your database with several languages.
-
-Visit our dedicated Discord channel: <https://discord.gg/ovhcloud>. Ask questions, provide feedback and interact directly with the team that builds our databases services.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/en-gb/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Join our community of users on <https://community.ovh.com/en/>.
diff --git a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.en-ie.md b/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.en-ie.md
deleted file mode 100644
index 4be703d4543..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.en-ie.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-title: M3db - Configure your M3db instance to accept incoming connections
-excerpt: Find out how to configure your M3db instance to accept incoming connections
-updated: 2022-05-12
----
-
-## Objective
-
-Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
-
-**This guide explains how to configure your M3db instance to accept incoming connections.**
-
-## Requirements
-
-- A [Public Cloud project](https://www.ovhcloud.com/en-ie/public-cloud/) in your OVHcloud account
-- Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.ie/&ovhSubsidiary=ie)
-- A M3db database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-
-## Instructions
-
-### Configure your M3db instance to accept incoming connections
-
-Before making a connection, we need to verify that our M3db instance is correctly configured.
-
-Log in to your [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.ie/&ovhSubsidiary=ie) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your M3db instance.
-
-#### Step 1: Verify your user roles and password
-
-Select the `Users`{.action} tab. Verify that you have a user with sufficient rights and a configured password. If you don't remember the user's password, you can either create a new user or regenerate the password of an existing user.
-
-> [!warning]
-> Be careful! By doing so you will need to update all the places where you already use this user/password pair.
->
-
-![User table](images/m3db_02_prepare_for_incoming_connections-20220530101005205.png){.thumbnail}
-
-You can add more users by clicking on the button `Add user`{.action}.
-
-![Add user](images/m3db_02_prepare_for_incoming_connections-20220530101111115.png){.thumbnail}
-
-Enter a username *(required)* and a group *(optional)*, then click `Create User`{.action}.
-
-> [!primary]
-> You can delete a user or regenerate a password via the `...`{.action} button in the `Users & Roles` table.
-
-#### Step 2: Authorise incoming connections from the M3db client
-
-> [!warning]
-> For security reasons the default network configuration doesn't allow any incoming connections. It is thus critical you authorise the suitable IP addresses in order to successfully access your database.
-
-In this step, select the `Authorised IPs`{.action} tab. IP addresses must be authorised here before they can connect to your database.
-
-Clicking on `Add an IP address or IP address block (CIDR)`{.action} opens a new window in which you can add single IP addresses or blocks to allow access to the database.
-
-![Add an IP](images/ip_authorize.png){.thumbnail}
-
-You can edit and retract database access via the `...`{.action} button in the IP table.
-
-> [!primary]
->
-> If you want to allow connections from the outside, you can enter the IP 0.0.0.0/0. Please use it carefully.
->
-
-#### Collect required information
-
-Select the `General information`{.action} tab to find the required login credentials in the `Login informations` section.
-
-![Login information tab](images/m3db_02_prepare_for_incoming_connections-20220530101418212.png){.thumbnail}
-
-Select the `Namespaces`{.action} tab to get the namespaces information.
-
-![Namespaces table](images/m3db_02_prepare_for_incoming_connections-20220530101803294.png){.thumbnail}
-
-> [!primary]
->
-> To create a new namespaces click on `Add a namespace`{.action} then fill the form :
->
-> ![Create new namespace](images/m3db_02_prepare_for_incoming_connections-20220530102131903.png){.thumbnail}
-
-Select the `Users`{.action} tab to get the username.
-
-![User table](images/m3db_02_prepare_for_incoming_connections-20220530101005205.png){.thumbnail}
-
-## Go further
-
-Visit the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/m3db) to find how to connect to your database with several languages.
-
-Visit our dedicated Discord channel: <https://discord.gg/ovhcloud>. Ask questions, provide feedback and interact directly with the team that builds our databases services.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/en-ie/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Join our community of users on <https://community.ovh.com/en/>.
diff --git a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.en-sg.md b/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.en-sg.md
deleted file mode 100644
index 5059db8b2b7..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.en-sg.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-title: M3db - Configure your M3db instance to accept incoming connections
-excerpt: Find out how to configure your M3db instance to accept incoming connections
-updated: 2022-05-12
----
-
-## Objective
-
-Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
-
-**This guide explains how to configure your M3db instance to accept incoming connections.**
-
-## Requirements
-
-- A [Public Cloud project](https://www.ovhcloud.com/en-sg/public-cloud/) in your OVHcloud account
-- Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/sg/&ovhSubsidiary=sg)
-- A M3db database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-
-## Instructions
-
-### Configure your M3db instance to accept incoming connections
-
-Before making a connection, we need to verify that our M3db instance is correctly configured.
-
-Log in to your [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/sg/&ovhSubsidiary=sg) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your M3db instance.
-
-#### Step 1: Verify your user roles and password
-
-Select the `Users`{.action} tab. Verify that you have a user with sufficient rights and a configured password. If you don't remember the user's password, you can either create a new user or regenerate the password of an existing user.
-
-> [!warning]
-> Be careful! By doing so you will need to update all the places where you already use this user/password pair.
->
-
-![User table](images/m3db_02_prepare_for_incoming_connections-20220530101005205.png){.thumbnail}
-
-You can add more users by clicking on the button `Add user`{.action}.
-
-![Add user](images/m3db_02_prepare_for_incoming_connections-20220530101111115.png){.thumbnail}
-
-Enter a username *(required)* and a group *(optional)*, then click `Create User`{.action}.
-
-> [!primary]
-> You can delete a user or regenerate a password via the `...`{.action} button in the `Users & Roles` table.
-
-#### Step 2: Authorise incoming connections from the M3db client
-
-> [!warning]
-> For security reasons the default network configuration doesn't allow any incoming connections. It is thus critical you authorise the suitable IP addresses in order to successfully access your database.
-
-In this step, select the `Authorised IPs`{.action} tab. IP addresses must be authorised here before they can connect to your database.
-
-Clicking on `Add an IP address or IP address block (CIDR)`{.action} opens a new window in which you can add single IP addresses or blocks to allow access to the database.
-
-![Add an IP](images/ip_authorize.png){.thumbnail}
-
-You can edit and retract database access via the `...`{.action} button in the IP table.
-
-> [!primary]
->
-> If you want to allow connections from the outside, you can enter the IP 0.0.0.0/0. Please use it carefully.
->
-
-#### Collect required information
-
-Select the `General information`{.action} tab to find the required login credentials in the `Login informations` section.
-
-![Login information tab](images/m3db_02_prepare_for_incoming_connections-20220530101418212.png){.thumbnail}
-
-Select the `Namespaces`{.action} tab to get the namespaces information.
-
-![Namespaces table](images/m3db_02_prepare_for_incoming_connections-20220530101803294.png){.thumbnail}
-
-> [!primary]
->
-> To create a new namespaces click on `Add a namespace`{.action} then fill the form :
->
-> ![Create new namespace](images/m3db_02_prepare_for_incoming_connections-20220530102131903.png){.thumbnail}
-
-Select the `Users`{.action} tab to get the username.
-
-![User table](images/m3db_02_prepare_for_incoming_connections-20220530101005205.png){.thumbnail}
-
-## Go further
-
-Visit the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/m3db) to find how to connect to your database with several languages.
-
-Visit our dedicated Discord channel: <https://discord.gg/ovhcloud>. Ask questions, provide feedback and interact directly with the team that builds our databases services.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/en-sg/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Join our community of users on <https://community.ovh.com/en/>.
diff --git a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.en-us.md b/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.en-us.md
deleted file mode 100644
index f5ab2e43b12..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.en-us.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-title: M3db - Configure your M3db instance to accept incoming connections
-excerpt: Find out how to configure your M3db instance to accept incoming connections
-updated: 2022-05-12
----
-
-## Objective
-
-Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
-
-**This guide explains how to configure your M3db instance to accept incoming connections.**
-
-## Requirements
-
-- A [Public Cloud project](https://www.ovhcloud.com/en/public-cloud/) in your OVHcloud account
-- Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/world/&ovhSubsidiary=we)
-- A M3db database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-
-## Instructions
-
-### Configure your M3db instance to accept incoming connections
-
-Before making a connection, we need to verify that our M3db instance is correctly configured.
-
-Log in to your [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/world/&ovhSubsidiary=we) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your M3db instance.
-
-#### Step 1: Verify your user roles and password
-
-Select the `Users`{.action} tab. Verify that you have a user with sufficient rights and a configured password. If you don't remember the user's password, you can either create a new user or regenerate the password of an existing user.
-
-> [!warning]
-> Be careful! By doing so you will need to update all the places where you already use this user/password pair.
->
-
-![User table](images/m3db_02_prepare_for_incoming_connections-20220530101005205.png){.thumbnail}
-
-You can add more users by clicking on the button `Add user`{.action}.
-
-![Add user](images/m3db_02_prepare_for_incoming_connections-20220530101111115.png){.thumbnail}
-
-Enter a username *(required)* and a group *(optional)*, then click `Create User`{.action}.
-
-> [!primary]
-> You can delete a user or regenerate a password via the `...`{.action} button in the `Users & Roles` table.
-
-#### Step 2: Authorise incoming connections from the M3db client
-
-> [!warning]
-> For security reasons the default network configuration doesn't allow any incoming connections. It is thus critical you authorise the suitable IP addresses in order to successfully access your database.
-
-In this step, select the `Authorised IPs`{.action} tab. IP addresses must be authorised here before they can connect to your database.
-
-Clicking on `Add an IP address or IP address block (CIDR)`{.action} opens a new window in which you can add single IP addresses or blocks to allow access to the database.
-
-![Add an IP](images/ip_authorize.png){.thumbnail}
-
-You can edit and retract database access via the `...`{.action} button in the IP table.
-
-> [!primary]
->
-> If you want to allow connections from the outside, you can enter the IP 0.0.0.0/0. Please use it carefully.
->
-
-#### Collect required information
-
-Select the `General information`{.action} tab to find the required login credentials in the `Login informations` section.
-
-![Login information tab](images/m3db_02_prepare_for_incoming_connections-20220530101418212.png){.thumbnail}
-
-Select the `Namespaces`{.action} tab to get the namespaces information.
-
-![Namespaces table](images/m3db_02_prepare_for_incoming_connections-20220530101803294.png){.thumbnail}
-
-> [!primary]
->
-> To create a new namespaces click on `Add a namespace`{.action} then fill the form :
->
-> ![Create new namespace](images/m3db_02_prepare_for_incoming_connections-20220530102131903.png){.thumbnail}
-
-Select the `Users`{.action} tab to get the username.
-
-![User table](images/m3db_02_prepare_for_incoming_connections-20220530101005205.png){.thumbnail}
-
-## Go further
-
-Visit the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/m3db) to find how to connect to your database with several languages.
-
-Visit our dedicated Discord channel: <https://discord.gg/ovhcloud>. Ask questions, provide feedback and interact directly with the team that builds our databases services.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/en/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Join our community of users on <https://community.ovh.com/en/>.
diff --git a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.es-es.md b/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.es-es.md
deleted file mode 100644
index 61b2dbf5d24..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.es-es.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-title: M3db - Configure your M3db instance to accept incoming connections
-excerpt: Find out how to configure your M3db instance to accept incoming connections
-updated: 2022-05-12
----
-
-## Objective
-
-Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
-
-**This guide explains how to configure your M3db instance to accept incoming connections.**
-
-## Requirements
-
-- A [Public Cloud project](https://www.ovhcloud.com/es-es/public-cloud/) in your OVHcloud account
-- Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.es/&ovhSubsidiary=es)
-- A M3db database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-
-## Instructions
-
-### Configure your M3db instance to accept incoming connections
-
-Before making a connection, we need to verify that our M3db instance is correctly configured.
-
-Log in to your [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.es/&ovhSubsidiary=es) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your M3db instance.
-
-#### Step 1: Verify your user roles and password
-
-Select the `Users`{.action} tab. Verify that you have a user with sufficient rights and a configured password. If you don't remember the user's password, you can either create a new user or regenerate the password of an existing user.
-
-> [!warning]
-> Be careful! By doing so you will need to update all the places where you already use this user/password pair.
->
-
-![User table](images/m3db_02_prepare_for_incoming_connections-20220530101005205.png){.thumbnail}
-
-You can add more users by clicking on the button `Add user`{.action}.
-
-![Add user](images/m3db_02_prepare_for_incoming_connections-20220530101111115.png){.thumbnail}
-
-Enter a username *(required)* and a group *(optional)*, then click `Create User`{.action}.
-
-> [!primary]
-> You can delete a user or regenerate a password via the `...`{.action} button in the `Users & Roles` table.
-
-#### Step 2: Authorise incoming connections from the M3db client
-
-> [!warning]
-> For security reasons the default network configuration doesn't allow any incoming connections. It is thus critical you authorise the suitable IP addresses in order to successfully access your database.
-
-In this step, select the `Authorised IPs`{.action} tab. IP addresses must be authorised here before they can connect to your database.
-
-Clicking on `Add an IP address or IP address block (CIDR)`{.action} opens a new window in which you can add single IP addresses or blocks to allow access to the database.
-
-![Add an IP](images/ip_authorize.png){.thumbnail}
-
-You can edit and retract database access via the `...`{.action} button in the IP table.
-
-> [!primary]
->
-> If you want to allow connections from the outside, you can enter the IP 0.0.0.0/0. Please use it carefully.
->
-
-#### Collect required information
-
-Select the `General information`{.action} tab to find the required login credentials in the `Login informations` section.
-
-![Login information tab](images/m3db_02_prepare_for_incoming_connections-20220530101418212.png){.thumbnail}
-
-Select the `Namespaces`{.action} tab to get the namespaces information.
-
-![Namespaces table](images/m3db_02_prepare_for_incoming_connections-20220530101803294.png){.thumbnail}
-
-> [!primary]
->
-> To create a new namespaces click on `Add a namespace`{.action} then fill the form :
->
-> ![Create new namespace](images/m3db_02_prepare_for_incoming_connections-20220530102131903.png){.thumbnail}
-
-Select the `Users`{.action} tab to get the username.
-
-![User table](images/m3db_02_prepare_for_incoming_connections-20220530101005205.png){.thumbnail}
-
-## Go further
-
-Visit the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/m3db) to find how to connect to your database with several languages.
-
-Visit our dedicated Discord channel: <https://discord.gg/ovhcloud>. Ask questions, provide feedback and interact directly with the team that builds our databases services.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/es-es/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Join our community of users on <https://community.ovh.com/en/>.
diff --git a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.es-us.md b/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.es-us.md
deleted file mode 100644
index 32e0d823cd6..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.es-us.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-title: M3db - Configure your M3db instance to accept incoming connections
-excerpt: Find out how to configure your M3db instance to accept incoming connections
-updated: 2022-05-12
----
-
-## Objective
-
-Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
-
-**This guide explains how to configure your M3db instance to accept incoming connections.**
-
-## Requirements
-
-- A [Public Cloud project](https://www.ovhcloud.com/es/public-cloud/) in your OVHcloud account
-- Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/world/&ovhSubsidiary=ws)
-- A M3db database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-
-## Instructions
-
-### Configure your M3db instance to accept incoming connections
-
-Before making a connection, we need to verify that our M3db instance is correctly configured.
-
-Log in to your [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/world/&ovhSubsidiary=ws) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your M3db instance.
-
-#### Step 1: Verify your user roles and password
-
-Select the `Users`{.action} tab. Verify that you have a user with sufficient rights and a configured password. If you don't remember the user's password, you can either create a new user or regenerate the password of an existing user.
-
-> [!warning]
-> Be careful! By doing so you will need to update all the places where you already use this user/password pair.
->
-
-![User table](images/m3db_02_prepare_for_incoming_connections-20220530101005205.png){.thumbnail}
-
-You can add more users by clicking on the button `Add user`{.action}.
-
-![Add user](images/m3db_02_prepare_for_incoming_connections-20220530101111115.png){.thumbnail}
-
-Enter a username *(required)* and a group *(optional)*, then click `Create User`{.action}.
-
-> [!primary]
-> You can delete a user or regenerate a password via the `...`{.action} button in the `Users & Roles` table.
-
-#### Step 2: Authorise incoming connections from the M3db client
-
-> [!warning]
-> For security reasons the default network configuration doesn't allow any incoming connections. It is thus critical you authorise the suitable IP addresses in order to successfully access your database.
-
-In this step, select the `Authorised IPs`{.action} tab. IP addresses must be authorised here before they can connect to your database.
-
-Clicking on `Add an IP address or IP address block (CIDR)`{.action} opens a new window in which you can add single IP addresses or blocks to allow access to the database.
-
-![Add an IP](images/ip_authorize.png){.thumbnail}
-
-You can edit and retract database access via the `...`{.action} button in the IP table.
-
-> [!primary]
->
-> If you want to allow connections from the outside, you can enter the IP 0.0.0.0/0. Please use it carefully.
->
-
-#### Collect required information
-
-Select the `General information`{.action} tab to find the required login credentials in the `Login informations` section.
-
-![Login information tab](images/m3db_02_prepare_for_incoming_connections-20220530101418212.png){.thumbnail}
-
-Select the `Namespaces`{.action} tab to get the namespaces information.
-
-![Namespaces table](images/m3db_02_prepare_for_incoming_connections-20220530101803294.png){.thumbnail}
-
-> [!primary]
->
-> To create a new namespaces click on `Add a namespace`{.action} then fill the form :
->
-> ![Create new namespace](images/m3db_02_prepare_for_incoming_connections-20220530102131903.png){.thumbnail}
-
-Select the `Users`{.action} tab to get the username.
-
-![User table](images/m3db_02_prepare_for_incoming_connections-20220530101005205.png){.thumbnail}
-
-## Go further
-
-Visit the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/m3db) to find how to connect to your database with several languages.
-
-Visit our dedicated Discord channel: <https://discord.gg/ovhcloud>. Ask questions, provide feedback and interact directly with the team that builds our databases services.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/es/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Join our community of users on <https://community.ovh.com/en/>.
diff --git a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.fr-ca.md b/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.fr-ca.md
deleted file mode 100644
index d6a4120856d..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.fr-ca.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-title: M3db - Configurez votre instance M3db pour accepter les connexions entrantes (EN)
-excerpt: Find out how to configure your M3db instance to accept incoming connections
-updated: 2022-05-12
----
-
-## Objective
-
-Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
-
-**This guide explains how to configure your M3db instance to accept incoming connections.**
-
-## Requirements
-
-- A [Public Cloud project](https://www.ovhcloud.com/fr-ca/public-cloud/) in your OVHcloud account
-- Access to the [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/ca/fr/&ovhSubsidiary=qc)
-- A M3db database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-
-## Instructions
-
-### Configure your M3db instance to accept incoming connections
-
-Before making a connection, we need to verify that our M3db instance is correctly configured.
-
-Log in to your [OVHcloud Control Panel](https://ca.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/ca/fr/&ovhSubsidiary=qc) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your M3db instance.
-
-#### Step 1: Verify your user roles and password
-
-Select the `Users`{.action} tab. Verify that you have a user with sufficient rights and a configured password. If you don't remember the user's password, you can either create a new user or regenerate the password of an existing user.
-
-> [!warning]
-> Be careful! By doing so you will need to update all the places where you already use this user/password pair.
->
-
-![User table](images/m3db_02_prepare_for_incoming_connections-20220530101005205.png){.thumbnail}
-
-You can add more users by clicking on the button `Add user`{.action}.
-
-![Add user](images/m3db_02_prepare_for_incoming_connections-20220530101111115.png){.thumbnail}
-
-Enter a username *(required)* and a group *(optional)*, then click `Create User`{.action}.
-
-> [!primary]
-> You can delete a user or regenerate a password via the `...`{.action} button in the `Users & Roles` table.
-
-#### Step 2: Authorise incoming connections from the M3db client
-
-> [!warning]
-> For security reasons the default network configuration doesn't allow any incoming connections. It is thus critical you authorise the suitable IP addresses in order to successfully access your database.
-
-In this step, select the `Authorised IPs`{.action} tab. IP addresses must be authorised here before they can connect to your database.
-
-Clicking on `Add an IP address or IP address block (CIDR)`{.action} opens a new window in which you can add single IP addresses or blocks to allow access to the database.
-
-![Add an IP](images/ip_authorize.png){.thumbnail}
-
-You can edit and retract database access via the `...`{.action} button in the IP table.
-
-> [!primary]
->
-> If you want to allow connections from the outside, you can enter the IP 0.0.0.0/0. Please use it carefully.
->
-
-#### Collect required information
-
-Select the `General information`{.action} tab to find the required login credentials in the `Login informations` section.
-
-![Login information tab](images/m3db_02_prepare_for_incoming_connections-20220530101418212.png){.thumbnail}
-
-Select the `Namespaces`{.action} tab to get the namespaces information.
-
-![Namespaces table](images/m3db_02_prepare_for_incoming_connections-20220530101803294.png){.thumbnail}
-
-> [!primary]
->
-> To create a new namespaces click on `Add a namespace`{.action} then fill the form :
->
-> ![Create new namespace](images/m3db_02_prepare_for_incoming_connections-20220530102131903.png){.thumbnail}
-
-Select the `Users`{.action} tab to get the username.
-
-![User table](images/m3db_02_prepare_for_incoming_connections-20220530101005205.png){.thumbnail}
-
-## Go further
-
-Visit the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/m3db) to find how to connect to your database with several languages.
-
-Visit our dedicated Discord channel: <https://discord.gg/ovhcloud>. Ask questions, provide feedback and interact directly with the team that builds our databases services.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/fr-ca/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Join our community of users on <https://community.ovh.com/en/>.
diff --git a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.fr-fr.md b/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.fr-fr.md
deleted file mode 100644
index a45fe1af47e..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.fr-fr.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-title: M3db - Configurez votre instance M3db pour accepter les connexions entrantes (EN)
-excerpt: Find out how to configure your M3db instance to accept incoming connections
-updated: 2022-05-12
----
-
-## Objective
-
-Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
-
-**This guide explains how to configure your M3db instance to accept incoming connections.**
-
-## Requirements
-
-- A [Public Cloud project](https://www.ovhcloud.com/fr/public-cloud/) in your OVHcloud account
-- Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/fr/&ovhSubsidiary=fr)
-- A M3db database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-
-## Instructions
-
-### Configure your M3db instance to accept incoming connections
-
-Before making a connection, we need to verify that our M3db instance is correctly configured.
-
-Log in to your [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.com/fr/&ovhSubsidiary=fr) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your M3db instance.
-
-#### Step 1: Verify your user roles and password
-
-Select the `Users`{.action} tab. Verify that you have a user with sufficient rights and a configured password. If you don't remember the user's password, you can either create a new user or regenerate the password of an existing user.
-
-> [!warning]
-> Be careful! By doing so you will need to update all the places where you already use this user/password pair.
->
-
-![User table](images/m3db_02_prepare_for_incoming_connections-20220530101005205.png){.thumbnail}
-
-You can add more users by clicking on the button `Add user`{.action}.
-
-![Add user](images/m3db_02_prepare_for_incoming_connections-20220530101111115.png){.thumbnail}
-
-Enter a username *(required)* and a group *(optional)*, then click `Create User`{.action}.
-
-> [!primary]
-> You can delete a user or regenerate a password via the `...`{.action} button in the `Users & Roles` table.
-
-#### Step 2: Authorise incoming connections from the M3db client
-
-> [!warning]
-> For security reasons the default network configuration doesn't allow any incoming connections. It is thus critical you authorise the suitable IP addresses in order to successfully access your database.
-
-In this step, select the `Authorised IPs`{.action} tab. IP addresses must be authorised here before they can connect to your database.
-
-Clicking on `Add an IP address or IP address block (CIDR)`{.action} opens a new window in which you can add single IP addresses or blocks to allow access to the database.
-
-![Add an IP](images/ip_authorize.png){.thumbnail}
-
-You can edit and retract database access via the `...`{.action} button in the IP table.
-
-> [!primary]
->
-> If you want to allow connections from the outside, you can enter the IP 0.0.0.0/0. Please use it carefully.
->
-
-#### Collect required information
-
-Select the `General information`{.action} tab to find the required login credentials in the `Login informations` section.
-
-![Login information tab](images/m3db_02_prepare_for_incoming_connections-20220530101418212.png){.thumbnail}
-
-Select the `Namespaces`{.action} tab to get the namespaces information.
-
-![Namespaces table](images/m3db_02_prepare_for_incoming_connections-20220530101803294.png){.thumbnail}
-
-> [!primary]
->
-> To create a new namespaces click on `Add a namespace`{.action} then fill the form :
->
-> ![Create new namespace](images/m3db_02_prepare_for_incoming_connections-20220530102131903.png){.thumbnail}
-
-Select the `Users`{.action} tab to get the username.
-
-![User table](images/m3db_02_prepare_for_incoming_connections-20220530101005205.png){.thumbnail}
-
-## Go further
-
-Visit the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/m3db) to find how to connect to your database with several languages.
-
-Visit our dedicated Discord channel: <https://discord.gg/ovhcloud>. Ask questions, provide feedback and interact directly with the team that builds our databases services.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/fr/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Join our community of users on <https://community.ovh.com/en/>.
diff --git a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.it-it.md b/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.it-it.md
deleted file mode 100644
index 0b9a3f5042c..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.it-it.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-title: M3db - Configure your M3db instance to accept incoming connections
-excerpt: Find out how to configure your M3db instance to accept incoming connections
-updated: 2022-05-12
----
-
-## Objective
-
-Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
-
-**This guide explains how to configure your M3db instance to accept incoming connections.**
-
-## Requirements
-
-- A [Public Cloud project](https://www.ovhcloud.com/it/public-cloud/) in your OVHcloud account
-- Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.it/&ovhSubsidiary=it)
-- A M3db database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-
-## Instructions
-
-### Configure your M3db instance to accept incoming connections
-
-Before making a connection, we need to verify that our M3db instance is correctly configured.
-
-Log in to your [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.it/&ovhSubsidiary=it) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your M3db instance.
-
-#### Step 1: Verify your user roles and password
-
-Select the `Users`{.action} tab. Verify that you have a user with sufficient rights and a configured password. If you don't remember the user's password, you can either create a new user or regenerate the password of an existing user.
-
-> [!warning]
-> Be careful! By doing so you will need to update all the places where you already use this user/password pair.
->
-
-![User table](images/m3db_02_prepare_for_incoming_connections-20220530101005205.png){.thumbnail}
-
-You can add more users by clicking on the button `Add user`{.action}.
-
-![Add user](images/m3db_02_prepare_for_incoming_connections-20220530101111115.png){.thumbnail}
-
-Enter a username *(required)* and a group *(optional)*, then click `Create User`{.action}.
-
-> [!primary]
-> You can delete a user or regenerate a password via the `...`{.action} button in the `Users & Roles` table.
-
-#### Step 2: Authorise incoming connections from the M3db client
-
-> [!warning]
-> For security reasons the default network configuration doesn't allow any incoming connections. It is thus critical you authorise the suitable IP addresses in order to successfully access your database.
-
-In this step, select the `Authorised IPs`{.action} tab. IP addresses must be authorised here before they can connect to your database.
-
-Clicking on `Add an IP address or IP address block (CIDR)`{.action} opens a new window in which you can add single IP addresses or blocks to allow access to the database.
-
-![Add an IP](images/ip_authorize.png){.thumbnail}
-
-You can edit and retract database access via the `...`{.action} button in the IP table.
-
-> [!primary]
->
-> If you want to allow connections from the outside, you can enter the IP 0.0.0.0/0. Please use it carefully.
->
-
-#### Collect required information
-
-Select the `General information`{.action} tab to find the required login credentials in the `Login informations` section.
-
-![Login information tab](images/m3db_02_prepare_for_incoming_connections-20220530101418212.png){.thumbnail}
-
-Select the `Namespaces`{.action} tab to get the namespaces information.
-
-![Namespaces table](images/m3db_02_prepare_for_incoming_connections-20220530101803294.png){.thumbnail}
-
-> [!primary]
->
-> To create a new namespaces click on `Add a namespace`{.action} then fill the form :
->
-> ![Create new namespace](images/m3db_02_prepare_for_incoming_connections-20220530102131903.png){.thumbnail}
-
-Select the `Users`{.action} tab to get the username.
-
-![User table](images/m3db_02_prepare_for_incoming_connections-20220530101005205.png){.thumbnail}
-
-## Go further
-
-Visit the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/m3db) to find how to connect to your database with several languages.
-
-Visit our dedicated Discord channel: <https://discord.gg/ovhcloud>. Ask questions, provide feedback and interact directly with the team that builds our databases services.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/it/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Join our community of users on <https://community.ovh.com/en/>.
diff --git a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.pl-pl.md b/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.pl-pl.md
deleted file mode 100644
index dae2a9311bb..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.pl-pl.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-title: M3db - Configure your M3db instance to accept incoming connections
-excerpt: Find out how to configure your M3db instance to accept incoming connections
-updated: 2022-05-12
----
-
-## Objective
-
-Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
-
-**This guide explains how to configure your M3db instance to accept incoming connections.**
-
-## Requirements
-
-- A [Public Cloud project](https://www.ovhcloud.com/pl/public-cloud/) in your OVHcloud account
-- Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.pl/&ovhSubsidiary=pl)
-- A M3db database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-
-## Instructions
-
-### Configure your M3db instance to accept incoming connections
-
-Before making a connection, we need to verify that our M3db instance is correctly configured.
-
-Log in to your [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.pl/&ovhSubsidiary=pl) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your M3db instance.
-
-#### Step 1: Verify your user roles and password
-
-Select the `Users`{.action} tab. Verify that you have a user with sufficient rights and a configured password. If you don't remember the user's password, you can either create a new user or regenerate the password of an existing user.
-
-> [!warning]
-> Be careful! By doing so you will need to update all the places where you already use this user/password pair.
->
-
-![User table](images/m3db_02_prepare_for_incoming_connections-20220530101005205.png){.thumbnail}
-
-You can add more users by clicking on the button `Add user`{.action}.
-
-![Add user](images/m3db_02_prepare_for_incoming_connections-20220530101111115.png){.thumbnail}
-
-Enter a username *(required)* and a group *(optional)*, then click `Create User`{.action}.
-
-> [!primary]
-> You can delete a user or regenerate a password via the `...`{.action} button in the `Users & Roles` table.
-
-#### Step 2: Authorise incoming connections from the M3db client
-
-> [!warning]
-> For security reasons the default network configuration doesn't allow any incoming connections. It is thus critical you authorise the suitable IP addresses in order to successfully access your database.
-
-In this step, select the `Authorised IPs`{.action} tab. IP addresses must be authorised here before they can connect to your database.
-
-Clicking on `Add an IP address or IP address block (CIDR)`{.action} opens a new window in which you can add single IP addresses or blocks to allow access to the database.
-
-![Add an IP](images/ip_authorize.png){.thumbnail}
-
-You can edit and retract database access via the `...`{.action} button in the IP table.
-
-> [!primary]
->
-> If you want to allow connections from the outside, you can enter the IP 0.0.0.0/0. Please use it carefully.
->
-
-#### Collect required information
-
-Select the `General information`{.action} tab to find the required login credentials in the `Login informations` section.
-
-![Login information tab](images/m3db_02_prepare_for_incoming_connections-20220530101418212.png){.thumbnail}
-
-Select the `Namespaces`{.action} tab to get the namespaces information.
-
-![Namespaces table](images/m3db_02_prepare_for_incoming_connections-20220530101803294.png){.thumbnail}
-
-> [!primary]
->
-> To create a new namespaces click on `Add a namespace`{.action} then fill the form :
->
-> ![Create new namespace](images/m3db_02_prepare_for_incoming_connections-20220530102131903.png){.thumbnail}
-
-Select the `Users`{.action} tab to get the username.
-
-![User table](images/m3db_02_prepare_for_incoming_connections-20220530101005205.png){.thumbnail}
-
-## Go further
-
-Visit the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/m3db) to find how to connect to your database with several languages.
-
-Visit our dedicated Discord channel: <https://discord.gg/ovhcloud>. Ask questions, provide feedback and interact directly with the team that builds our databases services.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/pl/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Join our community of users on <https://community.ovh.com/en/>.
diff --git a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.pt-pt.md b/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.pt-pt.md
deleted file mode 100644
index 18272eda58c..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/guide.pt-pt.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-title: M3db - Configure your M3db instance to accept incoming connections
-excerpt: Find out how to configure your M3db instance to accept incoming connections
-updated: 2022-05-12
----
-
-## Objective
-
-Public Cloud Databases allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions.
-
-**This guide explains how to configure your M3db instance to accept incoming connections.**
-
-## Requirements
-
-- A [Public Cloud project](https://www.ovhcloud.com/pt/public-cloud/) in your OVHcloud account
-- Access to the [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.pt/&ovhSubsidiary=pt)
-- A M3db database running on your OVHcloud Public Cloud Databases ([this guide](/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel) can help you to meet this requirement)
-
-## Instructions
-
-### Configure your M3db instance to accept incoming connections
-
-Before making a connection, we need to verify that our M3db instance is correctly configured.
-
-Log in to your [OVHcloud Control Panel](https://www.ovh.com/auth/?action=gotomanager&from=https://www.ovh.pt/&ovhSubsidiary=pt) and open your `Public Cloud`{.action} project. Click on `Databases`{.action} in the left-hand navigation bar and select your M3db instance.
-
-#### Step 1: Verify your user roles and password
-
-Select the `Users`{.action} tab. Verify that you have a user with sufficient rights and a configured password. If you don't remember the user's password, you can either create a new user or regenerate the password of an existing user.
-
-> [!warning]
-> Be careful! By doing so you will need to update all the places where you already use this user/password pair.
->
-
-![User table](images/m3db_02_prepare_for_incoming_connections-20220530101005205.png){.thumbnail}
-
-You can add more users by clicking on the button `Add user`{.action}.
-
-![Add user](images/m3db_02_prepare_for_incoming_connections-20220530101111115.png){.thumbnail}
-
-Enter a username *(required)* and a group *(optional)*, then click `Create User`{.action}.
-
-> [!primary]
-> You can delete a user or regenerate a password via the `...`{.action} button in the `Users & Roles` table.
-
-#### Step 2: Authorise incoming connections from the M3db client
-
-> [!warning]
-> For security reasons the default network configuration doesn't allow any incoming connections. It is thus critical you authorise the suitable IP addresses in order to successfully access your database.
-
-In this step, select the `Authorised IPs`{.action} tab. IP addresses must be authorised here before they can connect to your database.
-
-Clicking on `Add an IP address or IP address block (CIDR)`{.action} opens a new window in which you can add single IP addresses or blocks to allow access to the database.
-
-![Add an IP](images/ip_authorize.png){.thumbnail}
-
-You can edit and retract database access via the `...`{.action} button in the IP table.
-
-> [!primary]
->
-> If you want to allow connections from the outside, you can enter the IP 0.0.0.0/0. Please use it carefully.
->
-
-#### Collect required information
-
-Select the `General information`{.action} tab to find the required login credentials in the `Login informations` section.
-
-![Login information tab](images/m3db_02_prepare_for_incoming_connections-20220530101418212.png){.thumbnail}
-
-Select the `Namespaces`{.action} tab to get the namespaces information.
-
-![Namespaces table](images/m3db_02_prepare_for_incoming_connections-20220530101803294.png){.thumbnail}
-
-> [!primary]
->
-> To create a new namespaces click on `Add a namespace`{.action} then fill the form :
->
-> ![Create new namespace](images/m3db_02_prepare_for_incoming_connections-20220530102131903.png){.thumbnail}
-
-Select the `Users`{.action} tab to get the username.
-
-![User table](images/m3db_02_prepare_for_incoming_connections-20220530101005205.png){.thumbnail}
-
-## Go further
-
-Visit the [Github examples repository](https://github.com/ovh/public-cloud-databases-examples/tree/main/databases/m3db) to find how to connect to your database with several languages.
-
-Visit our dedicated Discord channel: <https://discord.gg/ovhcloud>. Ask questions, provide feedback and interact directly with the team that builds our databases services.
-
-If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](https://www.ovhcloud.com/pt/professional-services/) to get a quote and ask our Professional Services experts for a custom analysis of your project.
-
-Join our community of users on <https://community.ovh.com/en/>.
diff --git a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/images/ip_authorize.png b/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/images/ip_authorize.png
deleted file mode 100644
index 9429239b425..00000000000
Binary files a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/images/ip_authorize.png and /dev/null differ
diff --git a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/images/m3db_02_prepare_for_incoming_connections-20220530101005205.png b/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/images/m3db_02_prepare_for_incoming_connections-20220530101005205.png
deleted file mode 100644
index 7810a747c80..00000000000
Binary files a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/images/m3db_02_prepare_for_incoming_connections-20220530101005205.png and /dev/null differ
diff --git a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/images/m3db_02_prepare_for_incoming_connections-20220530101111115.png b/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/images/m3db_02_prepare_for_incoming_connections-20220530101111115.png
deleted file mode 100644
index b12cee2258f..00000000000
Binary files a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/images/m3db_02_prepare_for_incoming_connections-20220530101111115.png and /dev/null differ
diff --git a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/images/m3db_02_prepare_for_incoming_connections-20220530101418212.png b/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/images/m3db_02_prepare_for_incoming_connections-20220530101418212.png
deleted file mode 100644
index 08a0ca7b787..00000000000
Binary files a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/images/m3db_02_prepare_for_incoming_connections-20220530101418212.png and /dev/null differ
diff --git a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/images/m3db_02_prepare_for_incoming_connections-20220530101803294.png b/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/images/m3db_02_prepare_for_incoming_connections-20220530101803294.png
deleted file mode 100644
index 8d2fa3199e3..00000000000
Binary files a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/images/m3db_02_prepare_for_incoming_connections-20220530101803294.png and /dev/null differ
diff --git a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/images/m3db_02_prepare_for_incoming_connections-20220530102131903.png b/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/images/m3db_02_prepare_for_incoming_connections-20220530102131903.png
deleted file mode 100644
index 441512c4111..00000000000
Binary files a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/images/m3db_02_prepare_for_incoming_connections-20220530102131903.png and /dev/null differ
diff --git a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/meta.yaml b/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/meta.yaml
deleted file mode 100755
index d14b31245bd..00000000000
--- a/pages/public_cloud/public_cloud_databases/m3db_02_prepare_for_incoming_connections/meta.yaml
+++ /dev/null
@@ -1,5 +0,0 @@
-id: 0266623f-6706-4e7a-8435-d105855f1083
-full_slug: public-cloud-databases-m3db-configure-instance
-engine: m3db
-section: settings
-reference_category: public-cloud-databases-m3db-guides
\ No newline at end of file