diff --git a/pages/index-translations.de.yaml b/pages/index-translations.de.yaml index 5dac99c7303..aa357c70687 100644 --- a/pages/index-translations.de.yaml +++ b/pages/index-translations.de.yaml @@ -139,42 +139,52 @@ public-cloud-containers-orchestration-managed-rancher-service-resources: Resourc public-cloud-containers-orchestration-managed-rancher-service-creating-importing-kubernetes: Creating or importing a Kubernetes cluster public-cloud-containers-orchestration-managed-rancher-service-operations-kubernetes: Operations on a Kubernetes cluster public-cloud-containers-orchestration-managed-rancher-service-deploy-applications: Deploying applications with Rancher -public-cloud-data-analytics: Analytics -public-cloud-data-analytics-general-information: General information -public-cloud-data-analytics-general-guides: General guides -public-cloud-databases: Public Cloud Databases -public-cloud-databases-general-information: General information -public-cloud-databases-general-guides: General guides -public-cloud-databases-mongodb: MongoDB +public-cloud-databases-cassandra-guides: Cassandra - Guides +public-cloud-databases-cassandra: Cassandra +public-cloud-databases-common-configuration: Configuration +public-cloud-databases-common-getting-started: Getting started +public-cloud-databases-common-key-concepts: Key concepts +public-cloud-databases-common-migration: Migration +public-cloud-databases-common-security: Security +public-cloud-databases-common-troubleshooting: Troubleshooting +public-cloud-databases-common: Common +public-cloud-databases-mongodb-advanced-guides: MongoDB - Advanced guides public-cloud-databases-mongodb-getting-started: MongoDB - Getting started public-cloud-databases-mongodb-guides: MongoDB - User guides -public-cloud-databases-mongodb-advanced-guides: MongoDB - Advanced guides public-cloud-databases-mongodb-tutorials: MongoDB - Tutorials -public-cloud-databases-mysql: MySQL +public-cloud-databases-mongodb: MongoDB public-cloud-databases-mysql-guides: MySQL - Guides public-cloud-databases-mysql-tutorials: MySQL - Tutorials -public-cloud-databases-postgresql: PostgreSQL +public-cloud-databases-mysql: MySQL public-cloud-databases-postgresql-guides: PostgreSQL - Guides public-cloud-databases-postgresql-tutorials: PostgreSQL - Tutorials -public-cloud-databases-valkey: Valkey +public-cloud-databases-postgresql: PostgreSQL public-cloud-databases-valkey-guides: Valkey - Guides public-cloud-databases-valkey-tutorials: Valkey - Tutorials -public-cloud-data-analytics-grafana: Dashboards +public-cloud-databases-valkey: Valkey +public-cloud-databases: Public Cloud Databases +public-cloud-data-analytics-common-configuration: Configuration +public-cloud-data-analytics-common-getting-started: Getting started +public-cloud-data-analytics-common-key-concepts: Key concepts +public-cloud-data-analytics-common-migration: Migration +public-cloud-data-analytics-common-security: Security +public-cloud-data-analytics-common-troubleshooting: Troubleshooting +public-cloud-data-analytics-common: Common public-cloud-data-analytics-grafana-guides: Dashboards - Guides public-cloud-data-analytics-grafana-tutorials: Dashboards - Tutorials -public-cloud-data-analytics-kafka: Kafka +public-cloud-data-analytics-grafana: Dashboards public-cloud-data-analytics-kafka-advanced-guides: Kafka - Advanced guides +public-cloud-data-analytics-kafka-connect-guides: Kafka Connect - Guides public-cloud-data-analytics-kafka-connect: Kafka Connect -public-cloud-data-analytics-kafka-connect-guides: Kafka Connect - Guides public-cloud-data-analytics-kafka-getting-started: Kafka - Getting started public-cloud-data-analytics-kafka-guides: Kafka - User guides +public-cloud-data-analytics-kafka-mirrormaker-guides: Kafka MirrorMaker - Guides public-cloud-data-analytics-kafka-mirrormaker: Kafka MirrorMaker -public-cloud-data-analytics-kafka-mirrormaker-guides: Kafka MirrorMaker - Guides public-cloud-data-analytics-kafka-tutorials: Kafka - Tutorials -public-cloud-databases-cassandra: Cassandra -public-cloud-databases-cassandra-guides: Cassandra - Guides +public-cloud-data-analytics-kafka: Kafka +public-cloud-data-analytics-opensearch-guides: OpenSearch - Guides public-cloud-data-analytics-opensearch: OpenSearch -public-cloud-data-analytics-opensearch-guides: OpenSearch - Guides +public-cloud-data-analytics: Analytics public-cloud-compute: Compute public-cloud-compute-getting-started: Erste Schritte public-cloud-compute-general-information: Allgemeine Informationen diff --git a/pages/index-translations.es.yaml b/pages/index-translations.es.yaml index 0af79bcc440..ab37c1ba49f 100755 --- a/pages/index-translations.es.yaml +++ b/pages/index-translations.es.yaml @@ -139,42 +139,52 @@ public-cloud-containers-orchestration-managed-rancher-service-resources: Resourc public-cloud-containers-orchestration-managed-rancher-service-creating-importing-kubernetes: Creating or importing a Kubernetes cluster public-cloud-containers-orchestration-managed-rancher-service-operations-kubernetes: Operations on a Kubernetes cluster public-cloud-containers-orchestration-managed-rancher-service-deploy-applications: Deploying applications with Rancher -public-cloud-data-analytics: Analytics -public-cloud-data-analytics-general-information: General information -public-cloud-data-analytics-general-guides: General guides -public-cloud-databases: Public Cloud Databases -public-cloud-databases-general-information: General information -public-cloud-databases-general-guides: General guides -public-cloud-databases-mongodb: MongoDB +public-cloud-databases-cassandra-guides: Cassandra - Guides +public-cloud-databases-cassandra: Cassandra +public-cloud-databases-common-configuration: Configuration +public-cloud-databases-common-getting-started: Getting started +public-cloud-databases-common-key-concepts: Key concepts +public-cloud-databases-common-migration: Migration +public-cloud-databases-common-security: Security +public-cloud-databases-common-troubleshooting: Troubleshooting +public-cloud-databases-common: Common +public-cloud-databases-mongodb-advanced-guides: MongoDB - Advanced guides public-cloud-databases-mongodb-getting-started: MongoDB - Getting started public-cloud-databases-mongodb-guides: MongoDB - User guides -public-cloud-databases-mongodb-advanced-guides: MongoDB - Advanced guides public-cloud-databases-mongodb-tutorials: MongoDB - Tutorials -public-cloud-databases-mysql: MySQL +public-cloud-databases-mongodb: MongoDB public-cloud-databases-mysql-guides: MySQL - Guides public-cloud-databases-mysql-tutorials: MySQL - Tutorials -public-cloud-databases-postgresql: PostgreSQL +public-cloud-databases-mysql: MySQL public-cloud-databases-postgresql-guides: PostgreSQL - Guides public-cloud-databases-postgresql-tutorials: PostgreSQL - Tutorials -public-cloud-databases-valkey: Valkey +public-cloud-databases-postgresql: PostgreSQL public-cloud-databases-valkey-guides: Valkey - Guides public-cloud-databases-valkey-tutorials: Valkey - Tutorials -public-cloud-data-analytics-grafana: Dashboards +public-cloud-databases-valkey: Valkey +public-cloud-databases: Public Cloud Databases +public-cloud-data-analytics-common-configuration: Configuration +public-cloud-data-analytics-common-getting-started: Getting started +public-cloud-data-analytics-common-key-concepts: Key concepts +public-cloud-data-analytics-common-migration: Migration +public-cloud-data-analytics-common-security: Security +public-cloud-data-analytics-common-troubleshooting: Troubleshooting +public-cloud-data-analytics-common: Common public-cloud-data-analytics-grafana-guides: Dashboards - Guides public-cloud-data-analytics-grafana-tutorials: Dashboards - Tutorials -public-cloud-data-analytics-kafka: Kafka +public-cloud-data-analytics-grafana: Dashboards public-cloud-data-analytics-kafka-advanced-guides: Kafka - Advanced guides +public-cloud-data-analytics-kafka-connect-guides: Kafka Connect - Guides public-cloud-data-analytics-kafka-connect: Kafka Connect -public-cloud-data-analytics-kafka-connect-guides: Kafka Connect - Guides public-cloud-data-analytics-kafka-getting-started: Kafka - Getting started public-cloud-data-analytics-kafka-guides: Kafka - User guides +public-cloud-data-analytics-kafka-mirrormaker-guides: Kafka MirrorMaker - Guides public-cloud-data-analytics-kafka-mirrormaker: Kafka MirrorMaker -public-cloud-data-analytics-kafka-mirrormaker-guides: Kafka MirrorMaker - Guides public-cloud-data-analytics-kafka-tutorials: Kafka - Tutorials -public-cloud-databases-cassandra: Cassandra -public-cloud-databases-cassandra-guides: Cassandra - Guides +public-cloud-data-analytics-kafka: Kafka +public-cloud-data-analytics-opensearch-guides: OpenSearch - Guides public-cloud-data-analytics-opensearch: OpenSearch -public-cloud-data-analytics-opensearch-guides: OpenSearch - Guides +public-cloud-data-analytics: Analytics public-cloud-compute: Compute public-cloud-compute-getting-started: Primeros pasos public-cloud-compute-general-information: Información general diff --git a/pages/index-translations.fq.yaml b/pages/index-translations.fq.yaml index 7e29b26ccb8..a8606f2b065 100755 --- a/pages/index-translations.fq.yaml +++ b/pages/index-translations.fq.yaml @@ -139,42 +139,52 @@ public-cloud-containers-orchestration-managed-rancher-service-resources: Resourc public-cloud-containers-orchestration-managed-rancher-service-creating-importing-kubernetes: Creating or importing a Kubernetes cluster public-cloud-containers-orchestration-managed-rancher-service-operations-kubernetes: Operations on a Kubernetes cluster public-cloud-containers-orchestration-managed-rancher-service-deploy-applications: Deploying applications with Rancher -public-cloud-data-analytics: Analytics -public-cloud-data-analytics-general-information: Informations générales -public-cloud-data-analytics-general-guides: Guides généraux -public-cloud-databases: Bases de données Public Cloud -public-cloud-databases-general-information: Informations générales -public-cloud-databases-general-guides: Guides généraux -public-cloud-databases-mongodb: MongoDB -public-cloud-databases-mongodb-getting-started: MongoDB - Getting started -public-cloud-databases-mongodb-guides: MongoDB - User guides +public-cloud-databases-cassandra-guides: Cassandra - Guides +public-cloud-databases-cassandra: Cassandra +public-cloud-databases-common-configuration: Configuration +public-cloud-databases-common-getting-started: Premiers pas +public-cloud-databases-common-key-concepts: Concepts clés +public-cloud-databases-common-migration: Migration +public-cloud-databases-common-security: Sécurité +public-cloud-databases-common-troubleshooting: Diagnostic +public-cloud-databases-common: Commun public-cloud-databases-mongodb-advanced-guides: MongoDB - Advanced guides -public-cloud-databases-mongodb-tutorials: MongoDB - Tutorials -public-cloud-databases-mysql: MySQL +public-cloud-databases-mongodb-getting-started: MongoDB - Premiers pas +public-cloud-databases-mongodb-guides: MongoDB - Guides utilisateur +public-cloud-databases-mongodb-tutorials: MongoDB - Tutoriels +public-cloud-databases-mongodb: MongoDB public-cloud-databases-mysql-guides: MySQL - Guides public-cloud-databases-mysql-tutorials: MySQL - Tutoriels -public-cloud-databases-postgresql: PostgreSQL +public-cloud-databases-mysql: MySQL public-cloud-databases-postgresql-guides: PostgreSQL - Guides public-cloud-databases-postgresql-tutorials: PostgreSQL - Tutoriels -public-cloud-databases-valkey: Valkey +public-cloud-databases-postgresql: PostgreSQL public-cloud-databases-valkey-guides: Valkey - Guides public-cloud-databases-valkey-tutorials: Valkey - Tutoriels -public-cloud-data-analytics-grafana: Dashboards +public-cloud-databases-valkey: Valkey +public-cloud-databases: Bases de données Public Cloud +public-cloud-data-analytics-common-configuration: Configuration +public-cloud-data-analytics-common-getting-started: Premiers pas +public-cloud-data-analytics-common-key-concepts: Concepts clés +public-cloud-data-analytics-common-migration: Migration +public-cloud-data-analytics-common-security: Sécurité +public-cloud-data-analytics-common-troubleshooting: Diagnostic +public-cloud-data-analytics-common: Commun public-cloud-data-analytics-grafana-guides: Dashboards - Guides public-cloud-data-analytics-grafana-tutorials: Dashboards - Tutoriels -public-cloud-data-analytics-kafka: Kafka +public-cloud-data-analytics-grafana: Dashboards public-cloud-data-analytics-kafka-advanced-guides: Kafka - Advanced guides +public-cloud-data-analytics-kafka-connect-guides: Kafka Connect - Guides public-cloud-data-analytics-kafka-connect: Kafka Connect -public-cloud-data-analytics-kafka-connect-guides: Kafka Connect - Guides public-cloud-data-analytics-kafka-getting-started: Kafka - Premiers pas public-cloud-data-analytics-kafka-guides: Kafka - Guides utilisateur +public-cloud-data-analytics-kafka-mirrormaker-guides: Kafka MirrorMaker - Guides public-cloud-data-analytics-kafka-mirrormaker: Kafka MirrorMaker -public-cloud-data-analytics-kafka-mirrormaker-guides: Kafka MirrorMaker - Guides public-cloud-data-analytics-kafka-tutorials: Kafka - Tutoriels -public-cloud-databases-cassandra: Cassandra -public-cloud-databases-cassandra-guides: Cassandra - Guides +public-cloud-data-analytics-kafka: Kafka +public-cloud-data-analytics-opensearch-guides: OpenSearch - Guides public-cloud-data-analytics-opensearch: OpenSearch -public-cloud-data-analytics-opensearch-guides: OpenSearch - Guides +public-cloud-data-analytics: Analytics public-cloud-compute: Compute public-cloud-compute-getting-started: Premiers pas public-cloud-compute-general-information: Informations générales diff --git a/pages/index-translations.fr.yaml b/pages/index-translations.fr.yaml index ab57fda0c55..01e72fadad1 100755 --- a/pages/index-translations.fr.yaml +++ b/pages/index-translations.fr.yaml @@ -140,42 +140,52 @@ public-cloud-containers-orchestration-managed-rancher-service-resources: Resourc public-cloud-containers-orchestration-managed-rancher-service-creating-importing-kubernetes: Creating or importing a Kubernetes cluster public-cloud-containers-orchestration-managed-rancher-service-operations-kubernetes: Operations on a Kubernetes cluster public-cloud-containers-orchestration-managed-rancher-service-deploy-applications: Deploying applications with Rancher -public-cloud-data-analytics: Analytics -public-cloud-data-analytics-general-information: Informations générales -public-cloud-data-analytics-general-guides: Guides généraux -public-cloud-databases: Bases de données Public Cloud -public-cloud-databases-general-information: Informations générales -public-cloud-databases-general-guides: Guides généraux -public-cloud-databases-mongodb: MongoDB +public-cloud-databases-cassandra-guides: Cassandra - Guides +public-cloud-databases-cassandra: Cassandra +public-cloud-databases-common-configuration: Configuration +public-cloud-databases-common-getting-started: Premiers pas +public-cloud-databases-common-key-concepts: Concepts clés +public-cloud-databases-common-migration: Migration +public-cloud-databases-common-security: Sécurité +public-cloud-databases-common-troubleshooting: Diagnostic +public-cloud-databases-common: Commun +public-cloud-databases-mongodb-advanced-guides: MongoDB - Advanced guides public-cloud-databases-mongodb-getting-started: MongoDB - Premiers pas public-cloud-databases-mongodb-guides: MongoDB - Guides utilisateur -public-cloud-databases-mongodb-advanced-guides: MongoDB - Advanced guides public-cloud-databases-mongodb-tutorials: MongoDB - Tutoriels -public-cloud-databases-mysql: MySQL +public-cloud-databases-mongodb: MongoDB public-cloud-databases-mysql-guides: MySQL - Guides public-cloud-databases-mysql-tutorials: MySQL - Tutoriels -public-cloud-databases-postgresql: PostgreSQL +public-cloud-databases-mysql: MySQL public-cloud-databases-postgresql-guides: PostgreSQL - Guides public-cloud-databases-postgresql-tutorials: PostgreSQL - Tutoriels -public-cloud-databases-valkey: Valkey +public-cloud-databases-postgresql: PostgreSQL public-cloud-databases-valkey-guides: Valkey - Guides public-cloud-databases-valkey-tutorials: Valkey - Tutoriels -public-cloud-data-analytics-grafana: Dashboards +public-cloud-databases-valkey: Valkey +public-cloud-databases: Bases de données Public Cloud +public-cloud-data-analytics-common-configuration: Configuration +public-cloud-data-analytics-common-getting-started: Premiers pas +public-cloud-data-analytics-common-key-concepts: Concepts clés +public-cloud-data-analytics-common-migration: Migration +public-cloud-data-analytics-common-security: Sécurité +public-cloud-data-analytics-common-troubleshooting: Diagnostic +public-cloud-data-analytics-common: Commun public-cloud-data-analytics-grafana-guides: Dashboards - Guides public-cloud-data-analytics-grafana-tutorials: Dashboards - Tutoriels -public-cloud-data-analytics-kafka: Kafka +public-cloud-data-analytics-grafana: Dashboards public-cloud-data-analytics-kafka-advanced-guides: Kafka - Advanced guides +public-cloud-data-analytics-kafka-connect-guides: Kafka Connect - Guides public-cloud-data-analytics-kafka-connect: Kafka Connect -public-cloud-data-analytics-kafka-connect-guides: Kafka Connect - Guides public-cloud-data-analytics-kafka-getting-started: Kafka - Premiers pas public-cloud-data-analytics-kafka-guides: Kafka - Guides utilisateur +public-cloud-data-analytics-kafka-mirrormaker-guides: Kafka MirrorMaker - Guides public-cloud-data-analytics-kafka-mirrormaker: Kafka MirrorMaker -public-cloud-data-analytics-kafka-mirrormaker-guides: Kafka MirrorMaker - Guides public-cloud-data-analytics-kafka-tutorials: Kafka - Tutoriels -public-cloud-databases-cassandra: Cassandra -public-cloud-databases-cassandra-guides: Cassandra - Guides +public-cloud-data-analytics-kafka: Kafka +public-cloud-data-analytics-opensearch-guides: OpenSearch - Guides public-cloud-data-analytics-opensearch: OpenSearch -public-cloud-data-analytics-opensearch-guides: OpenSearch - Guides +public-cloud-data-analytics: Analytics public-cloud-compute: Compute public-cloud-compute-getting-started: Premiers pas public-cloud-compute-general-information: Informations générales diff --git a/pages/index-translations.it.yaml b/pages/index-translations.it.yaml index 67bbc63304a..a8b7e8a1f6b 100644 --- a/pages/index-translations.it.yaml +++ b/pages/index-translations.it.yaml @@ -139,42 +139,52 @@ public-cloud-containers-orchestration-managed-rancher-service-resources: Resourc public-cloud-containers-orchestration-managed-rancher-service-creating-importing-kubernetes: Creating or importing a Kubernetes cluster public-cloud-containers-orchestration-managed-rancher-service-operations-kubernetes: Operations on a Kubernetes cluster public-cloud-containers-orchestration-managed-rancher-service-deploy-applications: Deploying applications with Rancher -public-cloud-data-analytics: Analytics -public-cloud-data-analytics-general-information: General information -public-cloud-data-analytics-general-guides: General guides -public-cloud-databases: Public Cloud Databases -public-cloud-databases-general-information: General information -public-cloud-databases-general-guides: General guides -public-cloud-databases-mongodb: MongoDB +public-cloud-databases-cassandra-guides: Cassandra - Guides +public-cloud-databases-cassandra: Cassandra +public-cloud-databases-common-configuration: Configuration +public-cloud-databases-common-getting-started: Getting started +public-cloud-databases-common-key-concepts: Key concepts +public-cloud-databases-common-migration: Migration +public-cloud-databases-common-security: Security +public-cloud-databases-common-troubleshooting: Troubleshooting +public-cloud-databases-common: Common +public-cloud-databases-mongodb-advanced-guides: MongoDB - Advanced guides public-cloud-databases-mongodb-getting-started: MongoDB - Getting started public-cloud-databases-mongodb-guides: MongoDB - User guides -public-cloud-databases-mongodb-advanced-guides: MongoDB - Advanced guides public-cloud-databases-mongodb-tutorials: MongoDB - Tutorials -public-cloud-databases-mysql: MySQL +public-cloud-databases-mongodb: MongoDB public-cloud-databases-mysql-guides: MySQL - Guides public-cloud-databases-mysql-tutorials: MySQL - Tutorials -public-cloud-databases-postgresql: PostgreSQL +public-cloud-databases-mysql: MySQL public-cloud-databases-postgresql-guides: PostgreSQL - Guides public-cloud-databases-postgresql-tutorials: PostgreSQL - Tutorials -public-cloud-databases-valkey: Valkey +public-cloud-databases-postgresql: PostgreSQL public-cloud-databases-valkey-guides: Valkey - Guides public-cloud-databases-valkey-tutorials: Valkey - Tutorials -public-cloud-data-analytics-grafana: Dashboards +public-cloud-databases-valkey: Valkey +public-cloud-databases: Public Cloud Databases +public-cloud-data-analytics-common-configuration: Configuration +public-cloud-data-analytics-common-getting-started: Getting started +public-cloud-data-analytics-common-key-concepts: Key concepts +public-cloud-data-analytics-common-migration: Migration +public-cloud-data-analytics-common-security: Security +public-cloud-data-analytics-common-troubleshooting: Troubleshooting +public-cloud-data-analytics-common: Common public-cloud-data-analytics-grafana-guides: Dashboards - Guides public-cloud-data-analytics-grafana-tutorials: Dashboards - Tutorials -public-cloud-data-analytics-kafka: Kafka +public-cloud-data-analytics-grafana: Dashboards public-cloud-data-analytics-kafka-advanced-guides: Kafka - Advanced guides +public-cloud-data-analytics-kafka-connect-guides: Kafka Connect - Guides public-cloud-data-analytics-kafka-connect: Kafka Connect -public-cloud-data-analytics-kafka-connect-guides: Kafka Connect - Guides public-cloud-data-analytics-kafka-getting-started: Kafka - Getting started public-cloud-data-analytics-kafka-guides: Kafka - User guides +public-cloud-data-analytics-kafka-mirrormaker-guides: Kafka MirrorMaker - Guides public-cloud-data-analytics-kafka-mirrormaker: Kafka MirrorMaker -public-cloud-data-analytics-kafka-mirrormaker-guides: Kafka MirrorMaker - Guides public-cloud-data-analytics-kafka-tutorials: Kafka - Tutorials -public-cloud-databases-cassandra: Cassandra -public-cloud-databases-cassandra-guides: Cassandra - Guides +public-cloud-data-analytics-kafka: Kafka +public-cloud-data-analytics-opensearch-guides: OpenSearch - Guides public-cloud-data-analytics-opensearch: OpenSearch -public-cloud-data-analytics-opensearch-guides: OpenSearch - Guides +public-cloud-data-analytics: Analytics public-cloud-compute: Compute public-cloud-compute-getting-started: Per iniziare public-cloud-compute-general-information: Informazioni generali diff --git a/pages/index-translations.pl.yaml b/pages/index-translations.pl.yaml index 4149b028605..277f9214b93 100755 --- a/pages/index-translations.pl.yaml +++ b/pages/index-translations.pl.yaml @@ -139,42 +139,52 @@ public-cloud-containers-orchestration-managed-rancher-service-resources: Resourc public-cloud-containers-orchestration-managed-rancher-service-creating-importing-kubernetes: Creating or importing a Kubernetes cluster public-cloud-containers-orchestration-managed-rancher-service-operations-kubernetes: Operations on a Kubernetes cluster public-cloud-containers-orchestration-managed-rancher-service-deploy-applications: Deploying applications with Rancher -public-cloud-data-analytics: Analytics -public-cloud-data-analytics-general-information: General information -public-cloud-data-analytics-general-guides: General guides -public-cloud-databases: Public Cloud Databases -public-cloud-databases-general-information: General information -public-cloud-databases-general-guides: General guides -public-cloud-databases-mongodb: MongoDB +public-cloud-databases-cassandra-guides: Cassandra - Guides +public-cloud-databases-cassandra: Cassandra +public-cloud-databases-common-configuration: Configuration +public-cloud-databases-common-getting-started: Getting started +public-cloud-databases-common-key-concepts: Key concepts +public-cloud-databases-common-migration: Migration +public-cloud-databases-common-security: Security +public-cloud-databases-common-troubleshooting: Troubleshooting +public-cloud-databases-common: Common +public-cloud-databases-mongodb-advanced-guides: MongoDB - Advanced guides public-cloud-databases-mongodb-getting-started: MongoDB - Getting started public-cloud-databases-mongodb-guides: MongoDB - User guides -public-cloud-databases-mongodb-advanced-guides: MongoDB - Advanced guides public-cloud-databases-mongodb-tutorials: MongoDB - Tutorials -public-cloud-databases-mysql: MySQL +public-cloud-databases-mongodb: MongoDB public-cloud-databases-mysql-guides: MySQL - Guides public-cloud-databases-mysql-tutorials: MySQL - Tutorials -public-cloud-databases-postgresql: PostgreSQL +public-cloud-databases-mysql: MySQL public-cloud-databases-postgresql-guides: PostgreSQL - Guides public-cloud-databases-postgresql-tutorials: PostgreSQL - Tutorials -public-cloud-databases-valkey: Valkey +public-cloud-databases-postgresql: PostgreSQL public-cloud-databases-valkey-guides: Valkey - Guides public-cloud-databases-valkey-tutorials: Valkey - Tutorials -public-cloud-data-analytics-grafana: Dashboards +public-cloud-databases-valkey: Valkey +public-cloud-databases: Public Cloud Databases +public-cloud-data-analytics-common-configuration: Configuration +public-cloud-data-analytics-common-getting-started: Getting started +public-cloud-data-analytics-common-key-concepts: Key concepts +public-cloud-data-analytics-common-migration: Migration +public-cloud-data-analytics-common-security: Security +public-cloud-data-analytics-common-troubleshooting: Troubleshooting +public-cloud-data-analytics-common: Common public-cloud-data-analytics-grafana-guides: Dashboards - Guides public-cloud-data-analytics-grafana-tutorials: Dashboards - Tutorials -public-cloud-data-analytics-kafka: Kafka +public-cloud-data-analytics-grafana: Dashboards public-cloud-data-analytics-kafka-advanced-guides: Kafka - Advanced guides +public-cloud-data-analytics-kafka-connect-guides: Kafka Connect - Guides public-cloud-data-analytics-kafka-connect: Kafka Connect -public-cloud-data-analytics-kafka-connect-guides: Kafka Connect - Guides public-cloud-data-analytics-kafka-getting-started: Kafka - Getting started public-cloud-data-analytics-kafka-guides: Kafka - User guides +public-cloud-data-analytics-kafka-mirrormaker-guides: Kafka MirrorMaker - Guides public-cloud-data-analytics-kafka-mirrormaker: Kafka MirrorMaker -public-cloud-data-analytics-kafka-mirrormaker-guides: Kafka MirrorMaker - Guides public-cloud-data-analytics-kafka-tutorials: Kafka - Tutorials -public-cloud-databases-cassandra: Cassandra -public-cloud-databases-cassandra-guides: Cassandra - Guides +public-cloud-data-analytics-kafka: Kafka +public-cloud-data-analytics-opensearch-guides: OpenSearch - Guides public-cloud-data-analytics-opensearch: OpenSearch -public-cloud-data-analytics-opensearch-guides: OpenSearch - Guides +public-cloud-data-analytics: Analytics public-cloud-compute: Compute public-cloud-compute-getting-started: Pierwsze kroki public-cloud-compute-general-information: Informacje ogólne diff --git a/pages/index-translations.pt.yaml b/pages/index-translations.pt.yaml index 52714a3a54d..6df914680d2 100755 --- a/pages/index-translations.pt.yaml +++ b/pages/index-translations.pt.yaml @@ -139,42 +139,52 @@ public-cloud-containers-orchestration-managed-rancher-service-resources: Resourc public-cloud-containers-orchestration-managed-rancher-service-creating-importing-kubernetes: Creating or importing a Kubernetes cluster public-cloud-containers-orchestration-managed-rancher-service-operations-kubernetes: Operations on a Kubernetes cluster public-cloud-containers-orchestration-managed-rancher-service-deploy-applications: Deploying applications with Rancher -public-cloud-data-analytics: Analytics -public-cloud-data-analytics-general-information: General information -public-cloud-data-analytics-general-guides: General guides -public-cloud-databases: Public Cloud Databases -public-cloud-databases-general-information: General information -public-cloud-databases-general-guides: General guides -public-cloud-databases-mongodb: MongoDB +public-cloud-databases-cassandra-guides: Cassandra - Guides +public-cloud-databases-cassandra: Cassandra +public-cloud-databases-common-configuration: Configuration +public-cloud-databases-common-getting-started: Getting started +public-cloud-databases-common-key-concepts: Key concepts +public-cloud-databases-common-migration: Migration +public-cloud-databases-common-security: Security +public-cloud-databases-common-troubleshooting: Troubleshooting +public-cloud-databases-common: Common +public-cloud-databases-mongodb-advanced-guides: MongoDB - Advanced guides public-cloud-databases-mongodb-getting-started: MongoDB - Getting started public-cloud-databases-mongodb-guides: MongoDB - User guides -public-cloud-databases-mongodb-advanced-guides: MongoDB - Advanced guides public-cloud-databases-mongodb-tutorials: MongoDB - Tutorials -public-cloud-databases-mysql: MySQL +public-cloud-databases-mongodb: MongoDB public-cloud-databases-mysql-guides: MySQL - Guides public-cloud-databases-mysql-tutorials: MySQL - Tutorials -public-cloud-databases-postgresql: PostgreSQL +public-cloud-databases-mysql: MySQL public-cloud-databases-postgresql-guides: PostgreSQL - Guides public-cloud-databases-postgresql-tutorials: PostgreSQL - Tutorials -public-cloud-databases-valkey: Valkey +public-cloud-databases-postgresql: PostgreSQL public-cloud-databases-valkey-guides: Valkey - Guides public-cloud-databases-valkey-tutorials: Valkey - Tutorials -public-cloud-data-analytics-grafana: Dashboards +public-cloud-databases-valkey: Valkey +public-cloud-databases: Public Cloud Databases +public-cloud-data-analytics-common-configuration: Configuration +public-cloud-data-analytics-common-getting-started: Getting started +public-cloud-data-analytics-common-key-concepts: Key concepts +public-cloud-data-analytics-common-migration: Migration +public-cloud-data-analytics-common-security: Security +public-cloud-data-analytics-common-troubleshooting: Troubleshooting +public-cloud-data-analytics-common: Common public-cloud-data-analytics-grafana-guides: Dashboards - Guides public-cloud-data-analytics-grafana-tutorials: Dashboards - Tutorials -public-cloud-data-analytics-kafka: Kafka +public-cloud-data-analytics-grafana: Dashboards public-cloud-data-analytics-kafka-advanced-guides: Kafka - Advanced guides +public-cloud-data-analytics-kafka-connect-guides: Kafka Connect - Guides public-cloud-data-analytics-kafka-connect: Kafka Connect -public-cloud-data-analytics-kafka-connect-guides: Kafka Connect - Guides public-cloud-data-analytics-kafka-getting-started: Kafka - Getting started public-cloud-data-analytics-kafka-guides: Kafka - User guides +public-cloud-data-analytics-kafka-mirrormaker-guides: Kafka MirrorMaker - Guides public-cloud-data-analytics-kafka-mirrormaker: Kafka MirrorMaker -public-cloud-data-analytics-kafka-mirrormaker-guides: Kafka MirrorMaker - Guides public-cloud-data-analytics-kafka-tutorials: Kafka - Tutorials -public-cloud-databases-cassandra: Cassandra -public-cloud-databases-cassandra-guides: Cassandra - Guides +public-cloud-data-analytics-kafka: Kafka +public-cloud-data-analytics-opensearch-guides: OpenSearch - Guides public-cloud-data-analytics-opensearch: OpenSearch -public-cloud-data-analytics-opensearch-guides: OpenSearch - Guides +public-cloud-data-analytics: Analytics public-cloud-compute: Compute public-cloud-compute-getting-started: Introdução public-cloud-compute-general-information: Informações gerais diff --git a/pages/index.md b/pages/index.md index bd4f93a34aa..f61ac4072ff 100644 --- a/pages/index.md +++ b/pages/index.md @@ -881,115 +881,183 @@ + [Securing your OVHcloud infrastructure with Stormshield Network Security](public_cloud/public_cloud_network_services/tutorial-stormshield_network_security_vrack) + [Securing your OVHcloud infrastructure with Ubika WAAP Gateway](public_cloud/public_cloud_network_services/tutorial-ubika_vrack) + [Public Cloud Databases](products/public-cloud-databases) - + [General information](public-cloud-databases-general-information) - + [Public Cloud Databases Concepts - Security overview](public_cloud/public_cloud_databases/information_01_security_overview) - + [Public Cloud Databases - Lifecycle policy](public_cloud/public_cloud_databases/information_02_lifecycle_policy) - + [Responsibility model](public_cloud/public_cloud_databases/information_03_shared_responsibility) - + [FAQ Public Cloud databases](public_cloud/public_cloud_databases/information_04_faq) - + [Public Cloud Databases - Capabilities and Limitations](public_cloud/public_cloud_databases/information_05_capabilities) - + [Comparison of Public Cloud Databases Deployment Modes - Understanding 3-AZ / 1-AZ](public_cloud/public_cloud_databases/databases_18_regions_comparison) - + [Public Cloud Databases - Maintenance operations](public_cloud/public_cloud_databases/databases_15_maintenances) - + [Public Cloud Databases - Automated Backups](public_cloud/public_cloud_databases/databases_05_automated_backups) - + [General guides](public-cloud-databases-general-guides) - + [Public Cloud Databases - Getting started](public_cloud/public_cloud_databases/databases_01_order_control_panel) - + [Public Cloud Databases - Getting started with APIs](public_cloud/public_cloud_databases/databases_02_order_api) - + [Public Cloud Databases - Getting started with Terraform](public_cloud/public_cloud_databases/databases_09_order_terraform) - + [Public Cloud Databases - How to configure your Private Network](public_cloud/public_cloud_databases/databases_08_vrack) - + [Public Cloud Databases - How to configure your advanced parameters](public_cloud/public_cloud_databases/databases_03_advanced_configuration) - + [Public Cloud Databases - How to troubleshoot your service](public_cloud/public_cloud_databases/databases_04_troubleshooting) - + [Public Cloud Databases - How to restore a backup](public_cloud/public_cloud_databases/databases_06_restore_backup) - + [Public Cloud Databases - How to handle 'Disk Full' situations](public_cloud/public_cloud_databases/databases_10_full_disk_handling) - + [Public Cloud Databases - How to resize your service storage](public_cloud/public_cloud_databases/databases_11_resize_your_cluster_storage) - + [Public Cloud Databases - How to update your service flavor](public_cloud/public_cloud_databases/databases_13_update_your_cluster_flavor) - + [Public Cloud Databases - How to update your service plan](public_cloud/public_cloud_databases/databases_14_upgrade_your_cluster_plan) - + [Public Cloud Databases - How to setup logs forwarding](public_cloud/public_cloud_databases/databases_16_logs_to_customer) - + [Public Cloud Databases - How to setup your Kubernetes database operator](public_cloud/public_cloud_databases/databases_12_operator) - + [Public Cloud Databases - How to setup a service integration](public_cloud/public_cloud_databases/databases_07_cross_service_integration) - + [Public Cloud Databases - How to fetch service metrics with Prometheus](public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus) - + [Public Cloud Databases - How to enable deletion protection](public_cloud/public_cloud_databases/databases_19_deletion_protection) - + [Public Cloud Databases - How to migrate to OVHcloud Database as a Service (DBaaS)](public_cloud/public_cloud_databases/databases_20_move_to_cloud) - + [Public Cloud Databases - How to migrate a database service from Gen 2 to Gen 3](public_cloud/public_cloud_databases/databases_20_migrate_from_gen2_to_gen3) - + [Reversibility Policy for Managed Document Database Product](account_and_service_management/reversibility/06-ddb_mongo) - + [Reversibility Policy for Managed Relational Database Product](account_and_service_management/reversibility/07-rdb_mysql_postgre) - + [Reversibility Policy for the Managed Message Broker product](account_and_service_management/reversibility/14-reversibility-mdb) - + [Reversibility Policy for the Managed Data Visualization product](account_and_service_management/reversibility/15-reversibility-obs-data-visualization) - + [Reversibility Policy for the product Managed Search Engine Software Platform](account_and_service_management/reversibility/22-SDB-opensearch-reversibility) - + [Reversibility Policy for the product Managed In-Memory Database ](account_and_service_management/reversibility/26-idb-reversibility-policy) - + [How to move a database service from a single AZ region to a 3-AZ region](public_cloud/public_cloud_databases/databases_19_migrate_from_1AZ_to_3AZ) - + [MongoDB](products/public-cloud-databases-mongodb) - + [Getting Started](public-cloud-databases-mongodb-getting-started) - + [MongoDB - Why MongoDB](public_cloud/public_cloud_databases/mongodb_17_why_mongodb) - + [MongoDB - Cluster Sizing](public_cloud/public_cloud_databases/mongodb_18_cluster_sizing) - + [MongoDB - Migrate to OVHcloud](public_cloud/public_cloud_databases/mongodb_19_migrate_to_ovhcloud) - + [MongoDB - Relation Migrator](public_cloud/public_cloud_databases/mongodb_20_relational_migrator) - + [MongoDB - Getting Started](public_cloud/public_cloud_databases/mongodb_13_getting_started) - + [MongoDB - Managing a database service from the OVHcloud Control Panel](public_cloud/public_cloud_databases/mongodb_02_manage_control_panel) - + [User guides](public-cloud-databases-mongodb-guides) - + [MongoDB - Capabilities and Limitations](public_cloud/public_cloud_databases/mongodb_01_concept_capabilities) - + [MongoDB - Developer Best Practices](public_cloud/public_cloud_databases/mongodb_26_developer_best_practices) - + [MongoDB - Developer Tools](public_cloud/public_cloud_databases/mongodb_27_developer_tools) - + [MongoDB - Operational Best Practices](public_cloud/public_cloud_databases/mongodb_21_operational_best_practices) - + [MongoDB - Monitoring a MongoDB cluster](public_cloud/public_cloud_databases/mongodb_15_monitoring) - + [MongoDB - Connect with MongoDB Compass](public_cloud/public_cloud_databases/mongodb_07_connect_compass) - + [MongoDB - Connect with CLI](public_cloud/public_cloud_databases/mongodb_03_connect_cli) - + [MongoDB - Connect with Python](public_cloud/public_cloud_databases/mongodb_05_connect_python) - + [MongoDB - Connect with PHP](public_cloud/public_cloud_databases/mongodb_04_connect_php) - + [MongoDB - Backups and Restores with the CLI](public_cloud/public_cloud_databases/mongodb_06_howto_backup_restore) - + [MongoDB - Understand the connection strings URI format](public_cloud/public_cloud_databases/mongodb_10_connection_strings) - + [Advanced guides](public-cloud-databases-mongodb-advanced-guides) - + [MongoDB - BI Connector](public_cloud/public_cloud_databases/mongodb_25_bi_connector) - + [MongoDB - Configure an Analytics node](public_cloud/public_cloud_databases/mongodb_08_analytics) - + [MongoDB - Kafka Connector](public_cloud/public_cloud_databases/mongodb_23_kafka_connector) - + [MongoDB - Read Preference and Write Concern](public_cloud/public_cloud_databases/mongodb_24_read_preference_and_write_concern) - + [Tutorials](public-cloud-databases-mongodb-tutorials) - + [MongoDB - Tutorial - How to build and connect a Node.js Application to MongoDB](public_cloud/public_cloud_databases/mongodb_tuto_01_connect_nodejs_to_managed_mongodb) - + [MongoDB - Tutorial - How to deploy a database with Terraform](public_cloud/public_cloud_databases/mongodb_14_deploy_with_terraform) - + [MongoDB - Tutorial - How to benchmark MongoDB instances](public_cloud/public_cloud_databases/mongodb_22_benchmark) - + [MySQL](products/public-cloud-databases-mysql) - + [Guides](public-cloud-databases-mysql-guides) - + [MySQL - Capabilities and Limitations](public_cloud/public_cloud_databases/mysql_01_capabilities) - + [MySQL - Configure your MySQL instance to accept incoming connections](public_cloud/public_cloud_databases/mysql_07_prepare_for_incoming_connections) - + [MySQL - Connect with CLI](public_cloud/public_cloud_databases/mysql_03_connect_cli) - + [MySQL - Connect with PHP](public_cloud/public_cloud_databases/mysql_04_connect_php) - + [MySQL - Connect with Python](public_cloud/public_cloud_databases/mysql_05_connect_python) - + [MySQL - Connect with MySQL Workbench](public_cloud/public_cloud_databases/mysql_06_connect_workbench) - + [MySQL - Advanced parameters references](public_cloud/public_cloud_databases/mysql_08_advanced_parameters_references) - + [Tutorials](public-cloud-databases-mysql-tutorials) - + [MySQL - Tutorial - Connect an OVHcloud Managed Kubernetes service to an OVHcloud Managed MySQL service](public_cloud/public_cloud_databases/mysql_tuto_01_connect-k8s-to-managed-mysql) - + [PostgreSQL](products/public-cloud-databases-postgresql) - + [Guides](public-cloud-databases-postgresql-guides) - + [PostgreSQL - Capabilities and Limitations](public_cloud/public_cloud_databases/postgresql_01_capabilities) - + [PostgreSQL - Available extensions](public_cloud/public_cloud_databases/postgresql_02_extensions) - + [PostgreSQL - Configure your PostgreSQL instance to accept incoming connections](public_cloud/public_cloud_databases/postgresql_07_prepare_for_incoming_connections) - + [PostgreSQL - Connect with CLI](public_cloud/public_cloud_databases/postgresql_03_connect_cli) - + [PostgreSQL - Connect with PHP](public_cloud/public_cloud_databases/postgresql_04_connect_php) - + [PostgreSQL - Connect with Python](public_cloud/public_cloud_databases/postgresql_05_connect_python) - + [PostgreSQL - Connect with pgAdmin](public_cloud/public_cloud_databases/postgresql_06_connect_pgadmin) - + [PostgreSQL - Create and use connection pools](public_cloud/public_cloud_databases/postgresql_08_pool) - + [PostgreSQL - Advanced parameters references](public_cloud/public_cloud_databases/postgresql_10_advanced_parameters_references) - + [PostgreSQL - Concepts - High availability and failure scenarios](public_cloud/public_cloud_databases/postgresql_09_concept_high_availability) - + [PostgreSQL - Detect and terminate long-running queries](public_cloud/public_cloud_databases/postgresql_11_terminate_queries) - + [Tutorials](public-cloud-databases-postgresql-tutorials) - + [PostgreSQL - Tutorial - Build a Strapi app connected to OVHcloud Managed PostgreSQL service](public_cloud/public_cloud_databases/postgresql_tuto_01_connect_strapi_to_managed_postgresql) - + [PostgreSQL - Tutorial - Install Wagtail and connect it to OVHcloud Managed PostgreSQL service](public_cloud/public_cloud_databases/postgresql_tuto_02_connect_wagtail_to_managed_postgresql) - + [PostgreSQL - Tutorial - How to migrate an on-premises database to Public Cloud Databases](public_cloud/public_cloud_databases/postgresql_tuto_03_migrate_ecdb) - + [Valkey](products/public-cloud-databases-valkey) - + [Guides](public-cloud-databases-valkey-guides) - + [Valkey - Capabilities and Limitations](public_cloud/public_cloud_databases/redis_01_capabilities) - + [Valkey - Configure your Valkey service to accept incoming connections](public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) - + [Valkey - Connect with CLI](public_cloud/public_cloud_databases/redis_03_connect_cli) - + [Valkey - Connect with PHP](public_cloud/public_cloud_databases/redis_04_connect_php) - + [Valkey - Connect with Python](public_cloud/public_cloud_databases/redis_05_connect_python) - + [Valkey - Connect with RedisInsight](public_cloud/public_cloud_databases/redis_06_connect_redisinsight) - + [Valkey - Manage ACLs via API](public_cloud/public_cloud_databases/redis_07_update_acls) - + [Valkey - Advanced parameters references](public_cloud/public_cloud_databases/redis_09_advanced_parameters_references) - + [Tutorials](public-cloud-databases-valkey-tutorials) - + [Valkey - Tutorial - Boost your CMS (from the example of WordPress)](public_cloud/public_cloud_databases/redis_tuto_01_wordpress) - + [Cassandra](products/public-cloud-databases-cassandra) - + [Guides](public-cloud-databases-cassandra-guides) - + [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) + + [PostgreSQL](products/public-cloud-databases-postgresql) + + [Guides](public-cloud-databases-postgresql-guides) + + [PostgreSQL - Capabilities and Limitations](public_cloud/public_cloud_databases/postgresql_01_capabilities) + + [PostgreSQL - Available extensions](public_cloud/public_cloud_databases/postgresql_02_extensions) + + [PostgreSQL - Configure your PostgreSQL instance to accept incoming connections](public_cloud/public_cloud_databases/postgresql_07_prepare_for_incoming_connections) + + [PostgreSQL - Connect with CLI](public_cloud/public_cloud_databases/postgresql_03_connect_cli) + + [PostgreSQL - Connect with PHP](public_cloud/public_cloud_databases/postgresql_04_connect_php) + + [PostgreSQL - Connect with Python](public_cloud/public_cloud_databases/postgresql_05_connect_python) + + [PostgreSQL - Connect with pgAdmin](public_cloud/public_cloud_databases/postgresql_06_connect_pgadmin) + + [PostgreSQL - Create and use connection pools](public_cloud/public_cloud_databases/postgresql_08_pool) + + [PostgreSQL - Advanced parameters references](public_cloud/public_cloud_databases/postgresql_10_advanced_parameters_references) + + [PostgreSQL - Concepts - High availability and failure scenarios](public_cloud/public_cloud_databases/postgresql_09_concept_high_availability) + + [PostgreSQL - Detect and terminate long-running queries](public_cloud/public_cloud_databases/postgresql_11_terminate_queries) + + [Tutorials](public-cloud-databases-postgresql-tutorials) + + [PostgreSQL - Tutorial - Build a Strapi app connected to OVHcloud Managed PostgreSQL service](public_cloud/public_cloud_databases/postgresql_tuto_01_connect_strapi_to_managed_postgresql) + + [PostgreSQL - Tutorial - Install Wagtail and connect it to OVHcloud Managed PostgreSQL service](public_cloud/public_cloud_databases/postgresql_tuto_02_connect_wagtail_to_managed_postgresql) + + [PostgreSQL - Tutorial - How to migrate an on-premises database to Public Cloud Databases](public_cloud/public_cloud_databases/postgresql_tuto_03_migrate_ecdb) + + [MySQL](products/public-cloud-databases-mysql) + + [Guides](public-cloud-databases-mysql-guides) + + [MySQL - Capabilities and Limitations](public_cloud/public_cloud_databases/mysql_01_capabilities) + + [MySQL - Configure your MySQL instance to accept incoming connections](public_cloud/public_cloud_databases/mysql_07_prepare_for_incoming_connections) + + [MySQL - Connect with CLI](public_cloud/public_cloud_databases/mysql_03_connect_cli) + + [MySQL - Connect with PHP](public_cloud/public_cloud_databases/mysql_04_connect_php) + + [MySQL - Connect with Python](public_cloud/public_cloud_databases/mysql_05_connect_python) + + [MySQL - Connect with MySQL Workbench](public_cloud/public_cloud_databases/mysql_06_connect_workbench) + + [MySQL - Advanced parameters references](public_cloud/public_cloud_databases/mysql_08_advanced_parameters_references) + + [Tutorials](public-cloud-databases-mysql-tutorials) + + [MySQL - Tutorial - Connect an OVHcloud Managed Kubernetes service to an OVHcloud Managed MySQL service](public_cloud/public_cloud_databases/mysql_tuto_01_connect-k8s-to-managed-mysql) + + [MongoDB](products/public-cloud-databases-mongodb) + + [Getting Started](public-cloud-databases-mongodb-getting-started) + + [MongoDB - Why MongoDB](public_cloud/public_cloud_databases/mongodb_17_why_mongodb) + + [MongoDB - Cluster Sizing](public_cloud/public_cloud_databases/mongodb_18_cluster_sizing) + + [MongoDB - Migrate to OVHcloud](public_cloud/public_cloud_databases/mongodb_19_migrate_to_ovhcloud) + + [MongoDB - Relation Migrator](public_cloud/public_cloud_databases/mongodb_20_relational_migrator) + + [MongoDB - Getting Started](public_cloud/public_cloud_databases/mongodb_13_getting_started) + + [MongoDB - Managing a database service from the OVHcloud Control Panel](public_cloud/public_cloud_databases/mongodb_02_manage_control_panel) + + [User guides](public-cloud-databases-mongodb-guides) + + [MongoDB - Capabilities and Limitations](public_cloud/public_cloud_databases/mongodb_01_concept_capabilities) + + [MongoDB - Developer Best Practices](public_cloud/public_cloud_databases/mongodb_26_developer_best_practices) + + [MongoDB - Developer Tools](public_cloud/public_cloud_databases/mongodb_27_developer_tools) + + [MongoDB - Operational Best Practices](public_cloud/public_cloud_databases/mongodb_21_operational_best_practices) + + [MongoDB - Monitoring a MongoDB cluster](public_cloud/public_cloud_databases/mongodb_15_monitoring) + + [MongoDB - Connect with MongoDB Compass](public_cloud/public_cloud_databases/mongodb_07_connect_compass) + + [MongoDB - Connect with CLI](public_cloud/public_cloud_databases/mongodb_03_connect_cli) + + [MongoDB - Connect with Python](public_cloud/public_cloud_databases/mongodb_05_connect_python) + + [MongoDB - Connect with PHP](public_cloud/public_cloud_databases/mongodb_04_connect_php) + + [MongoDB - Backups and Restores with the CLI](public_cloud/public_cloud_databases/mongodb_06_howto_backup_restore) + + [MongoDB - Understand the connection strings URI format](public_cloud/public_cloud_databases/mongodb_10_connection_strings) + + [Advanced guides](public-cloud-databases-mongodb-advanced-guides) + + [MongoDB - BI Connector](public_cloud/public_cloud_databases/mongodb_25_bi_connector) + + [MongoDB - Configure an Analytics node](public_cloud/public_cloud_databases/mongodb_08_analytics) + + [MongoDB - Kafka Connector](public_cloud/public_cloud_databases/mongodb_23_kafka_connector) + + [MongoDB - Read Preference and Write Concern](public_cloud/public_cloud_databases/mongodb_24_read_preference_and_write_concern) + + [Tutorials](public-cloud-databases-mongodb-tutorials) + + [MongoDB - Tutorial - How to build and connect a Node.js Application to MongoDB](public_cloud/public_cloud_databases/mongodb_tuto_01_connect_nodejs_to_managed_mongodb) + + [MongoDB - Tutorial - How to deploy a database with Terraform](public_cloud/public_cloud_databases/mongodb_14_deploy_with_terraform) + + [MongoDB - Tutorial - How to benchmark MongoDB instances](public_cloud/public_cloud_databases/mongodb_22_benchmark) + + [Valkey](products/public-cloud-databases-valkey) + + [Guides](public-cloud-databases-valkey-guides) + + [Valkey - Capabilities and Limitations](public_cloud/public_cloud_databases/redis_01_capabilities) + + [Valkey - Configure your Valkey service to accept incoming connections](public_cloud/public_cloud_databases/redis_08_prepare_for_incoming_connections) + + [Valkey - Connect with CLI](public_cloud/public_cloud_databases/redis_03_connect_cli) + + [Valkey - Connect with PHP](public_cloud/public_cloud_databases/redis_04_connect_php) + + [Valkey - Connect with Python](public_cloud/public_cloud_databases/redis_05_connect_python) + + [Valkey - Connect with RedisInsight](public_cloud/public_cloud_databases/redis_06_connect_redisinsight) + + [Valkey - Manage ACLs via API](public_cloud/public_cloud_databases/redis_07_update_acls) + + [Valkey - Advanced parameters references](public_cloud/public_cloud_databases/redis_09_advanced_parameters_references) + + [Tutorials](public-cloud-databases-valkey-tutorials) + + [Valkey - Tutorial - Boost your CMS (from the example of WordPress)](public_cloud/public_cloud_databases/redis_tuto_01_wordpress) + + [Cassandra](products/public-cloud-databases-cassandra) + + [Guides](public-cloud-databases-cassandra-guides) + + [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) + + [Common](public-cloud-databases-common) + + [Key concepts](public-cloud-databases-common-key-concepts) + + [Public Cloud Databases - Lifecycle policy](public_cloud/public_cloud_databases/information_02_lifecycle_policy) + + [FAQ Public Cloud databases](public_cloud/public_cloud_databases/information_04_faq) + + [Public Cloud Databases - Capabilities and Limitations](public_cloud/public_cloud_databases/information_05_capabilities) + + [Comparison of Public Cloud Databases Deployment Modes - Understanding 3-AZ / 1-AZ](public_cloud/public_cloud_databases/databases_18_regions_comparison) + + [Public Cloud Databases - Automated Backups](public_cloud/public_cloud_databases/databases_05_automated_backups) + + [Getting started](public-cloud-databases-common-getting-started) + + [Public Cloud Databases - Getting started](public_cloud/public_cloud_databases/databases_01_order_control_panel) + + [Public Cloud Databases - Getting started with APIs](public_cloud/public_cloud_databases/databases_02_order_api) + + [Public Cloud Databases - Getting started with Terraform](public_cloud/public_cloud_databases/databases_09_order_terraform) + + [Configuration](public-cloud-databases-common-configuration) + + [Public Cloud Databases - Maintenance operations](public_cloud/public_cloud_databases/databases_15_maintenances) + + [Public Cloud Databases - How to configure your Private Network](public_cloud/public_cloud_databases/databases_08_vrack) + + [Public Cloud Databases - How to configure your advanced parameters](public_cloud/public_cloud_databases/databases_03_advanced_configuration) + + [Public Cloud Databases - How to restore a backup](public_cloud/public_cloud_databases/databases_06_restore_backup) + + [Public Cloud Databases - How to resize your service storage](public_cloud/public_cloud_databases/databases_11_resize_your_cluster_storage) + + [Public Cloud Databases - How to update your service flavor](public_cloud/public_cloud_databases/databases_13_update_your_cluster_flavor) + + [Public Cloud Databases - How to update your service plan](public_cloud/public_cloud_databases/databases_14_upgrade_your_cluster_plan) + + [Public Cloud Databases - How to setup logs forwarding](public_cloud/public_cloud_databases/databases_16_logs_to_customer) + + [Public Cloud Databases - How to setup your Kubernetes database operator](public_cloud/public_cloud_databases/databases_12_operator) + + [Public Cloud Databases - How to setup a service integration](public_cloud/public_cloud_databases/databases_07_cross_service_integration) + + [Public Cloud Databases - How to fetch service metrics with Prometheus](public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus) + + [Public Cloud Databases - How to enable deletion protection](public_cloud/public_cloud_databases/databases_19_deletion_protection) + + [Migration](public-cloud-databases-common-migration) + + [Public Cloud Databases - How to migrate to OVHcloud Database as a Service (DBaaS)](public_cloud/public_cloud_databases/databases_20_move_to_cloud) + + [Public Cloud Databases - How to migrate a database service from Gen 2 to Gen 3](public_cloud/public_cloud_databases/databases_20_migrate_from_gen2_to_gen3) + + [How to move a database service from a single AZ region to a 3-AZ region](public_cloud/public_cloud_databases/databases_19_migrate_from_1AZ_to_3AZ) + + [Reversibility Policy for Managed Relational Database product](account_and_service_management/reversibility/07-rdb_mysql_postgre) + + [Reversibility Policy for Managed Document Database product](account_and_service_management/reversibility/06-ddb_mongo) + + [Reversibility Policy for Managed In-Memory Database product](account_and_service_management/reversibility/26-idb-reversibility-policy) + + [Security](public-cloud-databases-common-security) + + [Public Cloud Databases Concepts - Security overview](public_cloud/public_cloud_databases/information_01_security_overview) + + [Responsibility model](public_cloud/public_cloud_databases/information_03_shared_responsibility) + + [Troubleshooting](public-cloud-databases-troubleshooting) + + [Public Cloud Databases - How to troubleshoot your service](public_cloud/public_cloud_databases/databases_04_troubleshooting) + + [Public Cloud Databases - How to handle 'Disk Full' situations](public_cloud/public_cloud_databases/databases_10_full_disk_handling) + + [Analytics](products/public-cloud-data-analytics) + + [Kafka](products/public-cloud-data-analytics-kafka) + + [Getting Started](public-cloud-data-analytics-kafka-getting-started) + + [Kafka - Getting started](public_cloud/public_cloud_databases/kafka_02_getting_started) + + [User guides](public-cloud-data-analytics-kafka-guides) + + [Kafka - Capabilities and Limitations](public_cloud/public_cloud_databases/kafka_01_capabilities) + + [Kafka - How to create a Kafka cluster](public_cloud/data_analytics/analytics/kafka_create_cluster) + + [Kafka - How to configure your Kafka cluster to accept incoming connections](public_cloud/data_analytics/analytics/kafka_incoming_connections) + + [Kafka - How to connect to a Kafka cluster with CLI](public_cloud/data_analytics/analytics/kafka_connect_cluster_cli) + + [Kafka - How to create topics for your Kafka cluster](public_cloud/data_analytics/analytics/kafka_create_topics) + + [Kafka - How to use Access Control Lists (ACLs)](public_cloud/data_analytics/analytics/kafka_configure_acl) + + [Kafka - How to enable schema registry](public_cloud/data_analytics/analytics/kafka_enable_schema_registry) + + [Advanced guides](public-cloud-data-analytics-kafka-advanced-guides) + + [Kafka - Advanced parameters references](public_cloud/public_cloud_databases/kafka_03_advanced_parameters_references) + + [Tutorials](public-cloud-data-analytics-kafka-tutorials) + + [Kafka - Create publisher and consumer applications](public_cloud/public_cloud_databases/kafka_04_dev_python_basics) + + [Kafka Connect](products/public-cloud-data-analytics-kafka-connect) + + [Guides](public-cloud-data-analytics-kafka-connect-guides) + + [Kafka Connect - Capabilities and Limitations](public_cloud/public_cloud_databases/kafkaconnect_01_capabilities) + + [Kafka Connect - Advanced parameters references](public_cloud/public_cloud_databases/kafkaconnect_02_advanced_parameters_references) + + [Kafka MirrorMaker](products/public-cloud-data-analytics-kafka-mirrormaker) + + [Guides](public-cloud-data-analytics-kafka-mirrormaker-guides) + + [Kafka MirrorMaker - Capabilities and Limitations](public_cloud/public_cloud_databases/mirrormaker_01_capabilities) + + [OpenSearch](products/public-cloud-data-analytics-opensearch) + + [Guides](public-cloud-data-analytics-opensearch-guides) + + [OpenSearch - Capabilities and Limitations](public_cloud/public_cloud_databases/opensearch_01_capabilities) + + [OpenSearch - Getting started](public_cloud/public_cloud_databases/opensearch_02_getting_Started) + + [OpenSearch - Monitor your infra (with Logstash or Fluent Bit)](public_cloud/public_cloud_databases/opensearch_200_elk_like) + + [OpenSearch - Advanced parameters references](public_cloud/public_cloud_databases/opensearch_03_advanced_parameters_references) + + [Dashboards](products/public-cloud-data-analytics-grafana) + + [Guides](public-cloud-data-analytics-grafana-guides) + + [Dashboards - Capabilities and Limitations](public_cloud/public_cloud_databases/grafana_01_capabilities) + + [Dashboards - Configure your Dashboards instance to accept incoming connections](public_cloud/public_cloud_databases/grafana_02_prepare_for_incoming_connections) + + [Dashboards - Advanced parameters references](public_cloud/public_cloud_databases/grafana_03_advanced_parameters_references) + + [Tutorials](public-cloud-data-analytics-grafana-tutorials) + + [Dashboards - Tutorial - Expose your Grafana in your private network via a reverse proxy NGINX](public_cloud/public_cloud_databases/grafana_tuto_01_reverse_proxy) + + [Dashboards - Tutorial - How to use the Dashboards API](public_cloud/public_cloud_databases/grafana_tuto_02_using_api) + + [Common](public-cloud-data-analytics-common) + + [Key concepts](public-cloud-data-analytics-common-key-concepts) + + [Analytics - Lifecycle policy](public_cloud/data_analytics/analytics/information_02_lifecycle_policy) + + [Analytics - Capabilities and Limitations](public_cloud/data_analytics/analytics/information_03_capabilities) + + [Comparison of Analytics Engines Deployment Modes - Understanding 3-AZ / 1-AZ](public_cloud/data_analytics/analytics/analytics_regions_comparison) + + [Analytics - Maintenance operations](public_cloud/data_analytics/analytics/information_04_maintenances) + + [Analytics - Automated Backups](public_cloud/data_analytics/analytics/information_05_automated_backups) + + [Getting started](public-cloud-data-analytics-common-getting-started) + + [Analytics - Getting started](public_cloud/data_analytics/analytics/analytics_getting_started) + + [Analytics - Getting started with APIs](public_cloud/data_analytics/analytics/analytics_getting_started_api) + + [Analytics - Getting started with Terraform](public_cloud/data_analytics/analytics/analytics_getting_started_terraform) + + [Configuration](public-cloud-data-analytics-common-configuration) + + [Analytics - How to configure your advanced parameters](public_cloud/data_analytics/analytics/analytics_advanced_parameters) + + [Analytics - How to restore a backup](public_cloud/data_analytics/analytics/analytics_restore_backup) + + [Analytics - How to resize your service storage](public_cloud/data_analytics/analytics/analytics_resize_cluster_storage) + + [Analytics - How to update your service flavor](public_cloud/data_analytics/analytics/analytics_update_cluster_flavor) + + [Analytics - How to update your service plan](public_cloud/data_analytics/analytics/analytics_update_cluster_plan) + + [Analytics - How to setup logs forwarding](public_cloud/data_analytics/analytics/analytics_logs_to_customer) + + [Analytics - How to set up your Kubernetes database operator](public_cloud/data_analytics/analytics/analytics_kubernetes_operator) + + [Analytics - How to fetch service metrics with Prometheus](public_cloud/data_analytics/analytics/analytics_metrics_via_prometheus) + + [Migration](public-cloud-data-analytics-common-migration) + + [Reversibility Policy for the Managed Message Broker product](account_and_service_management/reversibility/14-reversibility-mdb) + + [Reversibility Policy for the Managed Search Engine Software Platform product](account_and_service_management/reversibility/22-SDB-opensearch-reversibility) + + [Reversibility Policy for the Managed Data Visualization product](account_and_service_management/reversibility/15-reversibility-obs-data-visualization) + + [Security](public-cloud-data-analytics-common-security) + + [Analytics - Security overview](public_cloud/data_analytics/analytics/information_01_security_overview) + + [Troubleshooting](public-cloud-data-analytics-common-troubleshooting) + + [Analytics - How to troubleshoot your service](public_cloud/data_analytics/analytics/analytics_troubleshooting) + + [Analytics - How to handle Disk Full situations](public_cloud/data_analytics/analytics/analytics_full_disk_handling) + [Containers & Orchestration](products/public-cloud-containers-orchestration) + [Managed Kubernetes Service (MKS)](products/public-cloud-containers-orchestration-managed-kubernetes-k8s) + [Getting started](public-cloud-containers-orchestration-managed-kubernetes-k8s-getting-started) @@ -1281,64 +1349,6 @@ + [Emulators](products/public-cloud-quantum-computing-emulator) + [Guides](public-cloud-quantum-computing-emulators-guides) + [Quantum emulators - Getting started](public_cloud/quantum_computing/getting-started-emulators) - + [Analytics](products/public-cloud-data-analytics) - + [General information](products/public-cloud-data-analytics-general-information) - + [Analytics - Security overview](public_cloud/public_cloud_databases/information_01_security_overview) - + [Analytics - Lifecycle policy](public_cloud/data_analytics/analytics/information_02_lifecycle_policy) - + [Analytics - Capabilities and Limitations](public_cloud/data_analytics/analytics/information_03_capabilities) - + [Comparison of Analytics Engines Deployment Modes - Understanding 3-AZ / 1-AZ](public_cloud/data_analytics/analytics/analytics_regions_comparison) - + [Analytics - Maintenance operations](public_cloud/data_analytics/analytics/information_04_maintenances) - + [Analytics - Automated Backups](public_cloud/data_analytics/analytics/information_05_automated_backups) - + [General guides](products/public-cloud-data-analytics-general-guides) - + [Analytics - Getting started](public_cloud/data_analytics/analytics/analytics_getting_started) - + [Analytics - Getting started with APIs](public_cloud/data_analytics/analytics/analytics_getting_started_api) - + [Analytics - Getting started with Terraform](public_cloud/data_analytics/analytics/analytics_getting_started_terraform) - + [Analytics - How to configure your advanced parameters](public_cloud/data_analytics/analytics/analytics_advanced_parameters) - + [Analytics - How to troubleshoot your service](public_cloud/data_analytics/analytics/analytics_troubleshooting) - + [Analytics - How to restore a backup](public_cloud/data_analytics/analytics/analytics_restore_backup) - + [Analytics - How to handle Disk Full situations](public_cloud/data_analytics/analytics/analytics_full_disk_handling) - + [Analytics - How to resize your service storage](public_cloud/data_analytics/analytics/analytics_resize_cluster_storage) - + [Analytics - How to update your service flavor](public_cloud/data_analytics/analytics/analytics_update_cluster_flavor) - + [Analytics - How to update your service plan](public_cloud/data_analytics/analytics/analytics_update_cluster_plan) - + [Analytics - How to setup logs forwarding](public_cloud/data_analytics/analytics/analytics_logs_to_customer) - + [Analytics - How to set up your Kubernetes database operator](public_cloud/data_analytics/analytics/analytics_kubernetes_operator) - + [Analytics - How to fetch service metrics with Prometheus](public_cloud/data_analytics/analytics/analytics_metrics_via_prometheus) - + [Kafka](products/public-cloud-data-analytics-kafka) - + [Getting Started](public-cloud-data-analytics-kafka-getting-started) - + [Kafka - Getting started](public_cloud/public_cloud_databases/kafka_02_getting_started) - + [User guides](public-cloud-data-analytics-kafka-guides) - + [Kafka - Capabilities and Limitations](public_cloud/public_cloud_databases/kafka_01_capabilities) - + [Kafka - How to create a Kafka cluster](public_cloud/data_analytics/analytics/kafka_create_cluster) - + [Kafka - How to configure your Kafka cluster to accept incoming connections](public_cloud/data_analytics/analytics/kafka_incoming_connections) - + [Kafka - How to connect to a Kafka cluster with CLI](public_cloud/data_analytics/analytics/kafka_connect_cluster_cli) - + [Kafka - How to create topics for your Kafka cluster](public_cloud/data_analytics/analytics/kafka_create_topics) - + [Kafka - How to use Access Control Lists (ACLs)](public_cloud/data_analytics/analytics/kafka_configure_acl) - + [Kafka - How to enable schema registry](public_cloud/data_analytics/analytics/kafka_enable_schema_registry) - + [Advanced guides](public-cloud-data-analytics-kafka-advanced-guides) - + [Kafka - Advanced parameters references](public_cloud/public_cloud_databases/kafka_03_advanced_parameters_references) - + [Tutorials](public-cloud-data-analytics-kafka-tutorials) - + [Kafka - Create publisher and consumer applications](public_cloud/public_cloud_databases/kafka_04_dev_python_basics) - + [Kafka Connect](products/public-cloud-data-analytics-kafka-connect) - + [Guides](public-cloud-data-analytics-kafka-connect-guides) - + [Kafka Connect - Capabilities and Limitations](public_cloud/public_cloud_databases/kafkaconnect_01_capabilities) - + [Kafka Connect - Advanced parameters references](public_cloud/public_cloud_databases/kafkaconnect_02_advanced_parameters_references) - + [Kafka MirrorMaker](products/public-cloud-data-analytics-kafka-mirrormaker) - + [Guides](public-cloud-data-analytics-kafka-mirrormaker-guides) - + [Kafka MirrorMaker - Capabilities and Limitations](public_cloud/public_cloud_databases/mirrormaker_01_capabilities) - + [OpenSearch](products/public-cloud-data-analytics-opensearch) - + [Guides](public-cloud-data-analytics-opensearch-guides) - + [OpenSearch - Capabilities and Limitations](public_cloud/public_cloud_databases/opensearch_01_capabilities) - + [OpenSearch - Getting started](public_cloud/public_cloud_databases/opensearch_02_getting_Started) - + [OpenSearch - Monitor your infra (with Logstash or Fluent Bit)](public_cloud/public_cloud_databases/opensearch_200_elk_like) - + [OpenSearch - Advanced parameters references](public_cloud/public_cloud_databases/opensearch_03_advanced_parameters_references) - + [Dashboards](products/public-cloud-data-analytics-grafana) - + [Guides](public-cloud-data-analytics-grafana-guides) - + [Dashboards - Capabilities and Limitations](public_cloud/public_cloud_databases/grafana_01_capabilities) - + [Dashboards - Configure your Dashboards instance to accept incoming connections](public_cloud/public_cloud_databases/grafana_02_prepare_for_incoming_connections) - + [Dashboards - Advanced parameters references](public_cloud/public_cloud_databases/grafana_03_advanced_parameters_references) - + [Tutorials](public-cloud-data-analytics-grafana-tutorials) - + [Dashboards - Tutorial - Expose your Grafana in your private network via a reverse proxy NGINX](public_cloud/public_cloud_databases/grafana_tuto_01_reverse_proxy) - + [Dashboards - Tutorial - How to use the Dashboards API](public_cloud/public_cloud_databases/grafana_tuto_02_using_api) + [Integrations](products/public-cloud-integrations) + [Prefect](public-cloud-integrations-prefect) + [Prefect - Guide - Getting Started](public_cloud/integrations/prefect_guide_01_getting_started) diff --git a/pages/public_cloud/data_analytics/analytics/analytics_advanced_parameters/meta.yaml b/pages/public_cloud/data_analytics/analytics/analytics_advanced_parameters/meta.yaml index ea2218f8bfa..f0c8487be1f 100644 --- a/pages/public_cloud/data_analytics/analytics/analytics_advanced_parameters/meta.yaml +++ b/pages/public_cloud/data_analytics/analytics/analytics_advanced_parameters/meta.yaml @@ -1,3 +1,3 @@ id: 219c6c6d-f8e9-48f4-b3b1-e29368e82edc full_slug: data-analytics-advanced-configuration -reference_category: data-analytics-general-guides \ No newline at end of file +reference_category: public-cloud-data-analytics-common-configuration \ No newline at end of file diff --git a/pages/public_cloud/data_analytics/analytics/analytics_full_disk_handling/meta.yaml b/pages/public_cloud/data_analytics/analytics/analytics_full_disk_handling/meta.yaml index 39c283293fd..97b58e53078 100644 --- a/pages/public_cloud/data_analytics/analytics/analytics_full_disk_handling/meta.yaml +++ b/pages/public_cloud/data_analytics/analytics/analytics_full_disk_handling/meta.yaml @@ -1,3 +1,3 @@ id: c01ec779-1e6a-40bb-82f2-6c8f0a7893fa full_slug: data-analytics-handling-disk-full -reference_category: data-analytics-general-guides \ No newline at end of file +reference_category: public-cloud-data-analytics-common-troubleshooting \ No newline at end of file diff --git a/pages/public_cloud/data_analytics/analytics/analytics_getting_started/meta.yaml b/pages/public_cloud/data_analytics/analytics/analytics_getting_started/meta.yaml index 5a1b719f0e8..0fce69aea86 100644 --- a/pages/public_cloud/data_analytics/analytics/analytics_getting_started/meta.yaml +++ b/pages/public_cloud/data_analytics/analytics/analytics_getting_started/meta.yaml @@ -1,3 +1,3 @@ id: 90628733-567d-48aa-bbdc-066e4470e6fa full_slug: data-analytics-getting-started -reference_category: data-analytics-general-guides \ No newline at end of file +reference_category: public-cloud-data-analytics-common-getting-started \ No newline at end of file diff --git a/pages/public_cloud/data_analytics/analytics/analytics_getting_started_api/meta.yaml b/pages/public_cloud/data_analytics/analytics/analytics_getting_started_api/meta.yaml index 55ab5e8f8db..40f499e4cfb 100644 --- a/pages/public_cloud/data_analytics/analytics/analytics_getting_started_api/meta.yaml +++ b/pages/public_cloud/data_analytics/analytics/analytics_getting_started_api/meta.yaml @@ -1,3 +1,3 @@ id: 08c5a7fa-a1a2-4fae-b59d-7879fd2e221f full_slug: data-analytics-getting-started-api -reference_category: data-analytics-general-guides \ No newline at end of file +reference_category: public-cloud-data-analytics-common-getting-started \ No newline at end of file diff --git a/pages/public_cloud/data_analytics/analytics/analytics_getting_started_terraform/meta.yaml b/pages/public_cloud/data_analytics/analytics/analytics_getting_started_terraform/meta.yaml index d7eeee8da7d..72d0e468b37 100644 --- a/pages/public_cloud/data_analytics/analytics/analytics_getting_started_terraform/meta.yaml +++ b/pages/public_cloud/data_analytics/analytics/analytics_getting_started_terraform/meta.yaml @@ -1,3 +1,3 @@ id: 14c9060d-4a43-4001-8efc-b427ecee8cbd full_slug: data-analytics-order-terraform -reference_category: data-analytics-general-guides \ No newline at end of file +reference_category: public-cloud-data-analytics-common-getting-started \ No newline at end of file diff --git a/pages/public_cloud/data_analytics/analytics/analytics_kubernetes_operator/meta.yaml b/pages/public_cloud/data_analytics/analytics/analytics_kubernetes_operator/meta.yaml index d009bc131ad..ce2275a192b 100644 --- a/pages/public_cloud/data_analytics/analytics/analytics_kubernetes_operator/meta.yaml +++ b/pages/public_cloud/data_analytics/analytics/analytics_kubernetes_operator/meta.yaml @@ -1,3 +1,3 @@ id: d8add0d1-ba78-4787-8f42-07146863bbab full_slug: data-analytics-database-operator -reference_category: data-analytics-general-guides \ No newline at end of file +reference_category: public-cloud-data-analytics-common-configuration \ No newline at end of file diff --git a/pages/public_cloud/data_analytics/analytics/analytics_logs_to_customer/meta.yaml b/pages/public_cloud/data_analytics/analytics/analytics_logs_to_customer/meta.yaml index 9ed9ac8454a..2d12ffbddbf 100644 --- a/pages/public_cloud/data_analytics/analytics/analytics_logs_to_customer/meta.yaml +++ b/pages/public_cloud/data_analytics/analytics/analytics_logs_to_customer/meta.yaml @@ -1,3 +1,3 @@ id: dcc19a9a-a9be-45af-85c0-0d44e175b85b full_slug: data-analytics-logs-to-customers -reference_category: data-analytics-general-guides \ No newline at end of file +reference_category: public-cloud-data-analytics-common-configuration \ No newline at end of file diff --git a/pages/public_cloud/data_analytics/analytics/analytics_metrics_via_prometheus/meta.yaml b/pages/public_cloud/data_analytics/analytics/analytics_metrics_via_prometheus/meta.yaml index c537ce719fd..2a7261f0180 100644 --- a/pages/public_cloud/data_analytics/analytics/analytics_metrics_via_prometheus/meta.yaml +++ b/pages/public_cloud/data_analytics/analytics/analytics_metrics_via_prometheus/meta.yaml @@ -1,3 +1,3 @@ id: 3e4c0dc1-5afc-45de-8584-75af6bb76967 full_slug: data-analytics-service-metrics-with-prometheus -reference_category: data-analytics-general-guides +reference_category: public-cloud-data-analytics-common-configuration \ No newline at end of file diff --git a/pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/meta.yaml b/pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/meta.yaml index 5da18d61238..0dc5e206bbd 100644 --- a/pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/meta.yaml +++ b/pages/public_cloud/data_analytics/analytics/analytics_regions_comparison/meta.yaml @@ -1,2 +1,3 @@ id: 0041c9bd-8bf4-493a-8414-4c05349264f9 -full_slug: data-analytics-regions-comparison \ No newline at end of file +full_slug: data-analytics-regions-comparison +reference_category: public-cloud-data-analytics-common-key-concepts \ No newline at end of file diff --git a/pages/public_cloud/data_analytics/analytics/analytics_resize_cluster_storage/meta.yaml b/pages/public_cloud/data_analytics/analytics/analytics_resize_cluster_storage/meta.yaml index 64422e5229d..b5105933fa7 100644 --- a/pages/public_cloud/data_analytics/analytics/analytics_resize_cluster_storage/meta.yaml +++ b/pages/public_cloud/data_analytics/analytics/analytics_resize_cluster_storage/meta.yaml @@ -1,3 +1,3 @@ id: c65006f8-89dc-41fb-81b1-2fe88f104636 full_slug: data-analytics-resize-cluster-storage -reference_category: data-analytics-general-guides \ No newline at end of file +reference_category: public-cloud-data-analytics-common-configuration \ No newline at end of file diff --git a/pages/public_cloud/data_analytics/analytics/analytics_restore_backup/meta.yaml b/pages/public_cloud/data_analytics/analytics/analytics_restore_backup/meta.yaml index 554964ba661..b9af3acf3f5 100644 --- a/pages/public_cloud/data_analytics/analytics/analytics_restore_backup/meta.yaml +++ b/pages/public_cloud/data_analytics/analytics/analytics_restore_backup/meta.yaml @@ -1,3 +1,3 @@ id: e6b7d4b2-d3f7-425f-bcc6-91e50780a4df full_slug: data-analytics-restore-backup -reference_category: data-analytics-general-guides \ No newline at end of file +reference_category: public-cloud-data-analytics-common-configuration \ No newline at end of file diff --git a/pages/public_cloud/data_analytics/analytics/analytics_troubleshooting/meta.yaml b/pages/public_cloud/data_analytics/analytics/analytics_troubleshooting/meta.yaml index ee42ead7b5f..30e3c794bda 100644 --- a/pages/public_cloud/data_analytics/analytics/analytics_troubleshooting/meta.yaml +++ b/pages/public_cloud/data_analytics/analytics/analytics_troubleshooting/meta.yaml @@ -1,3 +1,3 @@ id: c2545cdc-2d35-4ea5-9566-a7cb9cf9dbfe full_slug: data-analytics-troubleshooting -reference_category: data-analytics-general-guides \ No newline at end of file +reference_category: public-cloud-data-analytics-common-troubleshooting \ No newline at end of file diff --git a/pages/public_cloud/data_analytics/analytics/analytics_update_cluster_flavor/meta.yaml b/pages/public_cloud/data_analytics/analytics/analytics_update_cluster_flavor/meta.yaml index 6c1f48caccd..1061f1552bf 100644 --- a/pages/public_cloud/data_analytics/analytics/analytics_update_cluster_flavor/meta.yaml +++ b/pages/public_cloud/data_analytics/analytics/analytics_update_cluster_flavor/meta.yaml @@ -1,3 +1,3 @@ id: 2f9c4779-bd89-4cad-9980-636691059307 full_slug: data-analytics-update-cluster-flavor -reference_category: data-analytics-general-guides \ No newline at end of file +reference_category: public-cloud-data-analytics-common-configuration \ No newline at end of file diff --git a/pages/public_cloud/data_analytics/analytics/analytics_update_cluster_plan/meta.yaml b/pages/public_cloud/data_analytics/analytics/analytics_update_cluster_plan/meta.yaml index 424eb38b67b..43013fed2e8 100644 --- a/pages/public_cloud/data_analytics/analytics/analytics_update_cluster_plan/meta.yaml +++ b/pages/public_cloud/data_analytics/analytics/analytics_update_cluster_plan/meta.yaml @@ -1,3 +1,3 @@ id: fc998686-fc04-4417-b4d6-5fd0da7e9869 full_slug: data-analytics-update-cluster-plan -reference_category: data-analytics-general-guides \ No newline at end of file +reference_category: public-cloud-data-analytics-common-configuration \ No newline at end of file diff --git a/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.de-de.md b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.de-de.md new file mode 100644 index 00000000000..f0851db31d7 --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.de-de.md @@ -0,0 +1,164 @@ +--- +title: Analytics Concepts - Security overview +excerpt: Analytics security overview +updated: 2025-11-04 +--- + +## Objective + +In addition to [the responsibility model for Analytics services](/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/), this security fact sheets aims at describing security features and functions associated to the service. It describes also best practices that customers can adopt to secure their services. + +## 1.Certifications + +- ISO/IEC 27001 +- ISO/IEC 27701 +- ISO/IEC 27017 +- ISO/IEC 27018 +- HDS +- SOC 1 type 1 +- SOC 2 type 1 +- CSA type 1 +- C5 type 1 + +## 2.Best pratices to be deployed on the service + +### 2.1 Recommandations once the service is delivered + +Once you have followed [these first steps to subscribe your service](/pages/public_cloud/data_analytics/analytics/analytics_getting_started) and reset the default password communicated to access to the service, you must filter connections by using iptables.
+You can also activate a private connection by using the vRack option. + +### 2.2 Vulnerability scans + +You are authorized to perform vulnerability scans on the service you have subscribed to. OVHcloud doesn't have to be previously informed.
+Security measures deployed by OVHcloud (especially network protection) aren't disabled, because such an audit's purpose is to demonstrate a clear vision of the security level of the customer's infrastructure.
+You are not authorized to use your service to scan other infrastructures. + +## 3.SLA + +SLA are available only for "Business/Production" and "Enterprise/Advanced" plans of this service.
+SLA for the Business/Production range in Single AZ are 99,90%.
+SLA for the Enterprise/Advanced range in Single AZ are 99,95%.
+SLA for the Production range in Multi AZ are 99,95%.
+SLA for the Advanced range in Multi AZ are 99,99%.
+The calculation method of SLA consists of the total number of minutes in the month in question deducted from the number of minutes of unavailability over the month in question. The total is divided by the total number of minutes in the month. +Service credits can be 10%, 25 % or 100% of the hourly cost per hour of unavailability of the affected Service. You can refer to the Particular Conditions of the service to get more details about the monthly available rate for each service range or plan and credits limitation. + +## 4.Backups + +### 4.1 Technical backups + +Technical backups are backups made by OVHcloud to maintain the Service Level Agreement. These backups can not be activated at customer request. + +### 4.2 Customer data backups + +Customer data (DB) is backed up, automated and operated following different frequencies. Those backups are encrypted and uploaded to a remote, replicated storage backend, in a different datacenter from the one the analytics service is hosted on. Details about frequencies, RPO and locations are listed following type of services and ranges at [this link](/pages/public_cloud/data_analytics/analytics/information_05_automated_backups).
+Customer data backup health status is checked daily by OVHcloud.
+If you need to restore your data using a backup, you can follow [this guide](/pages/public_cloud/data_analytics/analytics/analytics_restore_backup) and create a new service for this purpose. + +## 5.Logs + +| **Source** | **Content** | **Documentation** | +| --- | --- | --- | +| Control Panel | Logs of interactions made by admin, technical or billing contacts in the Control Panel and services they have access to, using API calls. |- (see `/me/api/logs`)
- [List of API calls done with your account](https://api.ovh.com/console/#/me/api/logs/self~GET)
- [List of API calls done on services you have access to](https://api.ovh.com/console/#/me/api/logs/services~GET)
-[Get your audit logs](https://api.ovh.com/console/#/me/logs/audit~GET) | +| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Cassandra service as an example `/cloud/project/{serviceName}/database/cassandra/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | + +## 6.API + +| **Name** | **Capacity** | **Link** | +| --- | --- | --- | +| Control Panel and service | Manage customer accounts and services on which each account has access rights. | [https://eu.api.ovh.com/console/#/dbaas/logs](https://eu.api.ovh.com/console/#/dbaas/logs)) | + +## 7.Accounts - User + +### 7.1 Control plane + +Using your customer account on the OVHcloud Control Panel, you are able to manage your service using [three different contacts](/pages/account_and_service_management/account_information/managing_contacts).
+OVHcloud uses another account with an internal NIC to refer a customer having subscribed to several services. + +To enforce security access to your account on the Control Panel, we recommend activating a [two-factor authentication mechanism](/pages/account_and_service_management/account_information/secure-ovhcloud-account-with-2fa) or [SSO(Single Sign-On) authentication](/pages/account_and_service_management/account_information/ovhcloud-account-connect-saml-adfs). + +You can also [create your own IAM policy](/pages/account_and_service_management/account_information/iam-policy-ui) on the service, with a user interface or [via API](/pages/account_and_service_management/account_information/iam-policies-api), and manage your users and groups.
+You can troubleshoot your IAM policy configuration and analyse actions [by using API calls to get logs](/pages/manage_and_operate/iam/iam-troubleshooting). + +### 7.2 Data plane + +Once a VM is created by OVHcloud, on which the customer Analytics engines run, a TLS certificate is generated and used by the customer to access his DB. The certificate is renewed every three months. + +## 8.Features and options available at service delivery + +### 8.1 High availability + +Different plans are made available on the service: Essential, Business/Production and Enterprise/Advanced plans.
+You can choose a "Business/Production" or "Enterprise/Advanced" offer to benefit from a high availability service as your data will be replicated across multiple nodes following the chosen plan. + +### 8.2 Data encryption + +#### 8.2.1 Encryption made by the OVHcloud teams + +All network traffic on the infrastructure managing the Analytics service is encrypted. Services volumes are also encrypted with a unique key specific for each customer project.
+These operations are made, by default, by the OVHcloud operation team. + +> [!primary] +> +> Currently, OVHcloud does not offer KMS as a service, you cannot bring your own keys. KMIP is managed by OVHcloud. +> + +For a MongoDB engine : + +- **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. +The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. +We use the LUKS2 mode aes-cbc-essiv:sha256 with a 512-bit key. +- **Backups:** backups are encrypted with a randomly generated key. This key is Asymetric RSA4096. + +For all the Analytics engines such as Kafka, OpenSearch and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage: + +- **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. +The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. +We use the LUKS2 default mode aes-xts-plain64:sha256 with a 512-bit key. +- **Backups:** backups are encrypted with a randomly generated key per file. These keys are in turn encrypted with a RSA key-encryption key-pair and stored in the header section of each backup segment. +The file encryption is performed with AES-256 in CTR mode with HMAC-SHA256 for integrity protection. +The RSA key-pair is randomly generated for each service. The key lengths are 256-bit for block encryption, 512-bit for the integrity protection and 3072-bits for the RSA key. + + +#### 8.2.2 In-use encryption on client side + +> [!primary] +> +> Currently, OVHcloud does not offer a KMS as a service, you cannot bring your own keys. KMIP is managed by OVHcloud. +> + +Currently, we do not provide in-use encryption except for MongoDB Advanced plans, based on MongoDB Client-Side Field Level Encryption.
+Data is encrypted client-side with customer-controlled encryption keys, before being sent, stored, or retrieved from the service. + +### 8.3 CVE monitoring + +The OVHcloud operation team in charge of the maintenance of Public Cloud Analytics services is constantly monitoring CVE on the different DBMS available. This monitoring is done through different channels, official mailing lists, security community, internal security check...
+ +We are also in constant communication with the MongoDB team, in order to provide fast and smooth transition to the latest security version of MongoDB. + +### 8.4 vRack option + +You can activate the vRack option at the subscription step or afterwards and have your private network for your Analytics project. + +### 8.5 HDS option + +The HDS option can be activated on the service.
+This option is available only for "Business/Production" and "Enterprise/Advanced" plans for this service.
+The subscription to the Business support level is mandatory, at least to maintain necessary requirements. + +## 9.Reversibility + +You can import and export your data following recommendations provided by editors for each Analytics engine technology. + +### 9.1 Erasure of customer data + +Once you destroy your Public Cloud project (your Analytics project) in the OVHcloud Control Panel, all allocated resources are relased automtically, including used encryption keys.
+As the encryption keys are unique for each project, they will be deleted after service decommissioning. Data can not be retrieved after. + +## Go further + +[Public Cloud Analytics documentation](/products/public-cloud-data-analytics) + +Visit our dedicated Discord channel: . 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](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. diff --git a/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.en-asia.md b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.en-asia.md new file mode 100644 index 00000000000..3ce01881a35 --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.en-asia.md @@ -0,0 +1,164 @@ +--- +title: Analytics Concepts - Security overview +excerpt: Analytics security overview +updated: 2025-11-04 +--- + +## Objective + +In addition to [the responsibility model for Analytics services](/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/), this security fact sheets aims at describing security features and functions associated to the service. It describes also best practices that customers can adopt to secure their services. + +## 1.Certifications + +- ISO/IEC 27001 +- ISO/IEC 27701 +- ISO/IEC 27017 +- ISO/IEC 27018 +- HDS +- SOC 1 type 1 +- SOC 2 type 1 +- CSA type 1 +- C5 type 1 + +## 2.Best pratices to be deployed on the service + +### 2.1 Recommandations once the service is delivered + +Once you have followed [these first steps to subscribe your service](/pages/public_cloud/data_analytics/analytics/analytics_getting_started) and reset the default password communicated to access to the service, you must filter connections by using iptables.
+You can also activate a private connection by using the vRack option. + +### 2.2 Vulnerability scans + +You are authorized to perform vulnerability scans on the service you have subscribed to. OVHcloud doesn't have to be previously informed.
+Security measures deployed by OVHcloud (especially network protection) aren't disabled, because such an audit's purpose is to demonstrate a clear vision of the security level of the customer's infrastructure.
+You are not authorized to use your service to scan other infrastructures. + +## 3.SLA + +SLA are available only for "Business/Production" and "Enterprise/Advanced" plans of this service.
+SLA for the Business/Production range in Single AZ are 99,90%.
+SLA for the Enterprise/Advanced range in Single AZ are 99,95%.
+SLA for the Production range in Multi AZ are 99,95%.
+SLA for the Advanced range in Multi AZ are 99,99%.
+The calculation method of SLA consists of the total number of minutes in the month in question deducted from the number of minutes of unavailability over the month in question. The total is divided by the total number of minutes in the month. +Service credits can be 10%, 25 % or 100% of the hourly cost per hour of unavailability of the affected Service. You can refer to the Particular Conditions of the service to get more details about the monthly available rate for each service range or plan and credits limitation. + +## 4.Backups + +### 4.1 Technical backups + +Technical backups are backups made by OVHcloud to maintain the Service Level Agreement. These backups can not be activated at customer request. + +### 4.2 Customer data backups + +Customer data (DB) is backed up, automated and operated following different frequencies. Those backups are encrypted and uploaded to a remote, replicated storage backend, in a different datacenter from the one the analytics service is hosted on. Details about frequencies, RPO and locations are listed following type of services and ranges at [this link](/pages/public_cloud/data_analytics/analytics/information_05_automated_backups).
+Customer data backup health status is checked daily by OVHcloud.
+If you need to restore your data using a backup, you can follow [this guide](/pages/public_cloud/data_analytics/analytics/analytics_restore_backup) and create a new service for this purpose. + +## 5.Logs + +| **Source** | **Content** | **Documentation** | +| --- | --- | --- | +| Control Panel | Logs of interactions made by admin, technical or billing contacts in the Control Panel and services they have access to, using API calls. |- (see `/me/api/logs`)
- [List of API calls done with your account](https://api.ovh.com/console/#/me/api/logs/self~GET)
- [List of API calls done on services you have access to](https://api.ovh.com/console/#/me/api/logs/services~GET)
-[Get your audit logs](https://api.ovh.com/console/#/me/logs/audit~GET) | +| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Cassandra service as an example `/cloud/project/{serviceName}/database/cassandra/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | + +## 6.API + +| **Name** | **Capacity** | **Link** | +| --- | --- | --- | +| Control Panel and service | Manage customer accounts and services on which each account has access rights. | [https://ca.api.ovh.com/console/#/dbaas/logs](https://ca.api.ovh.com/console/#/dbaas/logs)) | + +## 7.Accounts - User + +### 7.1 Control plane + +Using your customer account on the OVHcloud Control Panel, you are able to manage your service using [three different contacts](/pages/account_and_service_management/account_information/managing_contacts).
+OVHcloud uses another account with an internal NIC to refer a customer having subscribed to several services. + +To enforce security access to your account on the Control Panel, we recommend activating a [two-factor authentication mechanism](/pages/account_and_service_management/account_information/secure-ovhcloud-account-with-2fa) or [SSO(Single Sign-On) authentication](/pages/account_and_service_management/account_information/ovhcloud-account-connect-saml-adfs). + +You can also [create your own IAM policy](/pages/account_and_service_management/account_information/iam-policy-ui) on the service, with a user interface or [via API](/pages/account_and_service_management/account_information/iam-policies-api), and manage your users and groups.
+You can troubleshoot your IAM policy configuration and analyse actions [by using API calls to get logs](/pages/manage_and_operate/iam/iam-troubleshooting). + +### 7.2 Data plane + +Once a VM is created by OVHcloud, on which the customer Analytics engines run, a TLS certificate is generated and used by the customer to access his DB. The certificate is renewed every three months. + +## 8.Features and options available at service delivery + +### 8.1 High availability + +Different plans are made available on the service: Essential, Business/Production and Enterprise/Advanced plans.
+You can choose a "Business/Production" or "Enterprise/Advanced" offer to benefit from a high availability service as your data will be replicated across multiple nodes following the chosen plan. + +### 8.2 Data encryption + +#### 8.2.1 Encryption made by the OVHcloud teams + +All network traffic on the infrastructure managing the Analytics service is encrypted. Services volumes are also encrypted with a unique key specific for each customer project.
+These operations are made, by default, by the OVHcloud operation team. + +> [!primary] +> +> Currently, OVHcloud does not offer KMS as a service, you cannot bring your own keys. KMIP is managed by OVHcloud. +> + +For a MongoDB engine : + +- **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. +The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. +We use the LUKS2 mode aes-cbc-essiv:sha256 with a 512-bit key. +- **Backups:** backups are encrypted with a randomly generated key. This key is Asymetric RSA4096. + +For all the Analytics engines such as Kafka, OpenSearch and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage: + +- **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. +The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. +We use the LUKS2 default mode aes-xts-plain64:sha256 with a 512-bit key. +- **Backups:** backups are encrypted with a randomly generated key per file. These keys are in turn encrypted with a RSA key-encryption key-pair and stored in the header section of each backup segment. +The file encryption is performed with AES-256 in CTR mode with HMAC-SHA256 for integrity protection. +The RSA key-pair is randomly generated for each service. The key lengths are 256-bit for block encryption, 512-bit for the integrity protection and 3072-bits for the RSA key. + + +#### 8.2.2 In-use encryption on client side + +> [!primary] +> +> Currently, OVHcloud does not offer a KMS as a service, you cannot bring your own keys. KMIP is managed by OVHcloud. +> + +Currently, we do not provide in-use encryption except for MongoDB Advanced plans, based on MongoDB Client-Side Field Level Encryption.
+Data is encrypted client-side with customer-controlled encryption keys, before being sent, stored, or retrieved from the service. + +### 8.3 CVE monitoring + +The OVHcloud operation team in charge of the maintenance of Public Cloud Analytics services is constantly monitoring CVE on the different DBMS available. This monitoring is done through different channels, official mailing lists, security community, internal security check...
+ +We are also in constant communication with the MongoDB team, in order to provide fast and smooth transition to the latest security version of MongoDB. + +### 8.4 vRack option + +You can activate the vRack option at the subscription step or afterwards and have your private network for your Analytics project. + +### 8.5 HDS option + +The HDS option can be activated on the service.
+This option is available only for "Business/Production" and "Enterprise/Advanced" plans for this service.
+The subscription to the Business support level is mandatory, at least to maintain necessary requirements. + +## 9.Reversibility + +You can import and export your data following recommendations provided by editors for each Analytics engine technology. + +### 9.1 Erasure of customer data + +Once you destroy your Public Cloud project (your Analytics project) in the OVHcloud Control Panel, all allocated resources are relased automtically, including used encryption keys.
+As the encryption keys are unique for each project, they will be deleted after service decommissioning. Data can not be retrieved after. + +## Go further + +[Public Cloud Analytics documentation](/products/public-cloud-data-analytics) + +Visit our dedicated Discord channel: . 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](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. diff --git a/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.en-au.md b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.en-au.md new file mode 100644 index 00000000000..3ce01881a35 --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.en-au.md @@ -0,0 +1,164 @@ +--- +title: Analytics Concepts - Security overview +excerpt: Analytics security overview +updated: 2025-11-04 +--- + +## Objective + +In addition to [the responsibility model for Analytics services](/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/), this security fact sheets aims at describing security features and functions associated to the service. It describes also best practices that customers can adopt to secure their services. + +## 1.Certifications + +- ISO/IEC 27001 +- ISO/IEC 27701 +- ISO/IEC 27017 +- ISO/IEC 27018 +- HDS +- SOC 1 type 1 +- SOC 2 type 1 +- CSA type 1 +- C5 type 1 + +## 2.Best pratices to be deployed on the service + +### 2.1 Recommandations once the service is delivered + +Once you have followed [these first steps to subscribe your service](/pages/public_cloud/data_analytics/analytics/analytics_getting_started) and reset the default password communicated to access to the service, you must filter connections by using iptables.
+You can also activate a private connection by using the vRack option. + +### 2.2 Vulnerability scans + +You are authorized to perform vulnerability scans on the service you have subscribed to. OVHcloud doesn't have to be previously informed.
+Security measures deployed by OVHcloud (especially network protection) aren't disabled, because such an audit's purpose is to demonstrate a clear vision of the security level of the customer's infrastructure.
+You are not authorized to use your service to scan other infrastructures. + +## 3.SLA + +SLA are available only for "Business/Production" and "Enterprise/Advanced" plans of this service.
+SLA for the Business/Production range in Single AZ are 99,90%.
+SLA for the Enterprise/Advanced range in Single AZ are 99,95%.
+SLA for the Production range in Multi AZ are 99,95%.
+SLA for the Advanced range in Multi AZ are 99,99%.
+The calculation method of SLA consists of the total number of minutes in the month in question deducted from the number of minutes of unavailability over the month in question. The total is divided by the total number of minutes in the month. +Service credits can be 10%, 25 % or 100% of the hourly cost per hour of unavailability of the affected Service. You can refer to the Particular Conditions of the service to get more details about the monthly available rate for each service range or plan and credits limitation. + +## 4.Backups + +### 4.1 Technical backups + +Technical backups are backups made by OVHcloud to maintain the Service Level Agreement. These backups can not be activated at customer request. + +### 4.2 Customer data backups + +Customer data (DB) is backed up, automated and operated following different frequencies. Those backups are encrypted and uploaded to a remote, replicated storage backend, in a different datacenter from the one the analytics service is hosted on. Details about frequencies, RPO and locations are listed following type of services and ranges at [this link](/pages/public_cloud/data_analytics/analytics/information_05_automated_backups).
+Customer data backup health status is checked daily by OVHcloud.
+If you need to restore your data using a backup, you can follow [this guide](/pages/public_cloud/data_analytics/analytics/analytics_restore_backup) and create a new service for this purpose. + +## 5.Logs + +| **Source** | **Content** | **Documentation** | +| --- | --- | --- | +| Control Panel | Logs of interactions made by admin, technical or billing contacts in the Control Panel and services they have access to, using API calls. |- (see `/me/api/logs`)
- [List of API calls done with your account](https://api.ovh.com/console/#/me/api/logs/self~GET)
- [List of API calls done on services you have access to](https://api.ovh.com/console/#/me/api/logs/services~GET)
-[Get your audit logs](https://api.ovh.com/console/#/me/logs/audit~GET) | +| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Cassandra service as an example `/cloud/project/{serviceName}/database/cassandra/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | + +## 6.API + +| **Name** | **Capacity** | **Link** | +| --- | --- | --- | +| Control Panel and service | Manage customer accounts and services on which each account has access rights. | [https://ca.api.ovh.com/console/#/dbaas/logs](https://ca.api.ovh.com/console/#/dbaas/logs)) | + +## 7.Accounts - User + +### 7.1 Control plane + +Using your customer account on the OVHcloud Control Panel, you are able to manage your service using [three different contacts](/pages/account_and_service_management/account_information/managing_contacts).
+OVHcloud uses another account with an internal NIC to refer a customer having subscribed to several services. + +To enforce security access to your account on the Control Panel, we recommend activating a [two-factor authentication mechanism](/pages/account_and_service_management/account_information/secure-ovhcloud-account-with-2fa) or [SSO(Single Sign-On) authentication](/pages/account_and_service_management/account_information/ovhcloud-account-connect-saml-adfs). + +You can also [create your own IAM policy](/pages/account_and_service_management/account_information/iam-policy-ui) on the service, with a user interface or [via API](/pages/account_and_service_management/account_information/iam-policies-api), and manage your users and groups.
+You can troubleshoot your IAM policy configuration and analyse actions [by using API calls to get logs](/pages/manage_and_operate/iam/iam-troubleshooting). + +### 7.2 Data plane + +Once a VM is created by OVHcloud, on which the customer Analytics engines run, a TLS certificate is generated and used by the customer to access his DB. The certificate is renewed every three months. + +## 8.Features and options available at service delivery + +### 8.1 High availability + +Different plans are made available on the service: Essential, Business/Production and Enterprise/Advanced plans.
+You can choose a "Business/Production" or "Enterprise/Advanced" offer to benefit from a high availability service as your data will be replicated across multiple nodes following the chosen plan. + +### 8.2 Data encryption + +#### 8.2.1 Encryption made by the OVHcloud teams + +All network traffic on the infrastructure managing the Analytics service is encrypted. Services volumes are also encrypted with a unique key specific for each customer project.
+These operations are made, by default, by the OVHcloud operation team. + +> [!primary] +> +> Currently, OVHcloud does not offer KMS as a service, you cannot bring your own keys. KMIP is managed by OVHcloud. +> + +For a MongoDB engine : + +- **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. +The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. +We use the LUKS2 mode aes-cbc-essiv:sha256 with a 512-bit key. +- **Backups:** backups are encrypted with a randomly generated key. This key is Asymetric RSA4096. + +For all the Analytics engines such as Kafka, OpenSearch and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage: + +- **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. +The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. +We use the LUKS2 default mode aes-xts-plain64:sha256 with a 512-bit key. +- **Backups:** backups are encrypted with a randomly generated key per file. These keys are in turn encrypted with a RSA key-encryption key-pair and stored in the header section of each backup segment. +The file encryption is performed with AES-256 in CTR mode with HMAC-SHA256 for integrity protection. +The RSA key-pair is randomly generated for each service. The key lengths are 256-bit for block encryption, 512-bit for the integrity protection and 3072-bits for the RSA key. + + +#### 8.2.2 In-use encryption on client side + +> [!primary] +> +> Currently, OVHcloud does not offer a KMS as a service, you cannot bring your own keys. KMIP is managed by OVHcloud. +> + +Currently, we do not provide in-use encryption except for MongoDB Advanced plans, based on MongoDB Client-Side Field Level Encryption.
+Data is encrypted client-side with customer-controlled encryption keys, before being sent, stored, or retrieved from the service. + +### 8.3 CVE monitoring + +The OVHcloud operation team in charge of the maintenance of Public Cloud Analytics services is constantly monitoring CVE on the different DBMS available. This monitoring is done through different channels, official mailing lists, security community, internal security check...
+ +We are also in constant communication with the MongoDB team, in order to provide fast and smooth transition to the latest security version of MongoDB. + +### 8.4 vRack option + +You can activate the vRack option at the subscription step or afterwards and have your private network for your Analytics project. + +### 8.5 HDS option + +The HDS option can be activated on the service.
+This option is available only for "Business/Production" and "Enterprise/Advanced" plans for this service.
+The subscription to the Business support level is mandatory, at least to maintain necessary requirements. + +## 9.Reversibility + +You can import and export your data following recommendations provided by editors for each Analytics engine technology. + +### 9.1 Erasure of customer data + +Once you destroy your Public Cloud project (your Analytics project) in the OVHcloud Control Panel, all allocated resources are relased automtically, including used encryption keys.
+As the encryption keys are unique for each project, they will be deleted after service decommissioning. Data can not be retrieved after. + +## Go further + +[Public Cloud Analytics documentation](/products/public-cloud-data-analytics) + +Visit our dedicated Discord channel: . 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](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. diff --git a/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.en-ca.md b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.en-ca.md new file mode 100644 index 00000000000..3ce01881a35 --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.en-ca.md @@ -0,0 +1,164 @@ +--- +title: Analytics Concepts - Security overview +excerpt: Analytics security overview +updated: 2025-11-04 +--- + +## Objective + +In addition to [the responsibility model for Analytics services](/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/), this security fact sheets aims at describing security features and functions associated to the service. It describes also best practices that customers can adopt to secure their services. + +## 1.Certifications + +- ISO/IEC 27001 +- ISO/IEC 27701 +- ISO/IEC 27017 +- ISO/IEC 27018 +- HDS +- SOC 1 type 1 +- SOC 2 type 1 +- CSA type 1 +- C5 type 1 + +## 2.Best pratices to be deployed on the service + +### 2.1 Recommandations once the service is delivered + +Once you have followed [these first steps to subscribe your service](/pages/public_cloud/data_analytics/analytics/analytics_getting_started) and reset the default password communicated to access to the service, you must filter connections by using iptables.
+You can also activate a private connection by using the vRack option. + +### 2.2 Vulnerability scans + +You are authorized to perform vulnerability scans on the service you have subscribed to. OVHcloud doesn't have to be previously informed.
+Security measures deployed by OVHcloud (especially network protection) aren't disabled, because such an audit's purpose is to demonstrate a clear vision of the security level of the customer's infrastructure.
+You are not authorized to use your service to scan other infrastructures. + +## 3.SLA + +SLA are available only for "Business/Production" and "Enterprise/Advanced" plans of this service.
+SLA for the Business/Production range in Single AZ are 99,90%.
+SLA for the Enterprise/Advanced range in Single AZ are 99,95%.
+SLA for the Production range in Multi AZ are 99,95%.
+SLA for the Advanced range in Multi AZ are 99,99%.
+The calculation method of SLA consists of the total number of minutes in the month in question deducted from the number of minutes of unavailability over the month in question. The total is divided by the total number of minutes in the month. +Service credits can be 10%, 25 % or 100% of the hourly cost per hour of unavailability of the affected Service. You can refer to the Particular Conditions of the service to get more details about the monthly available rate for each service range or plan and credits limitation. + +## 4.Backups + +### 4.1 Technical backups + +Technical backups are backups made by OVHcloud to maintain the Service Level Agreement. These backups can not be activated at customer request. + +### 4.2 Customer data backups + +Customer data (DB) is backed up, automated and operated following different frequencies. Those backups are encrypted and uploaded to a remote, replicated storage backend, in a different datacenter from the one the analytics service is hosted on. Details about frequencies, RPO and locations are listed following type of services and ranges at [this link](/pages/public_cloud/data_analytics/analytics/information_05_automated_backups).
+Customer data backup health status is checked daily by OVHcloud.
+If you need to restore your data using a backup, you can follow [this guide](/pages/public_cloud/data_analytics/analytics/analytics_restore_backup) and create a new service for this purpose. + +## 5.Logs + +| **Source** | **Content** | **Documentation** | +| --- | --- | --- | +| Control Panel | Logs of interactions made by admin, technical or billing contacts in the Control Panel and services they have access to, using API calls. |- (see `/me/api/logs`)
- [List of API calls done with your account](https://api.ovh.com/console/#/me/api/logs/self~GET)
- [List of API calls done on services you have access to](https://api.ovh.com/console/#/me/api/logs/services~GET)
-[Get your audit logs](https://api.ovh.com/console/#/me/logs/audit~GET) | +| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Cassandra service as an example `/cloud/project/{serviceName}/database/cassandra/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | + +## 6.API + +| **Name** | **Capacity** | **Link** | +| --- | --- | --- | +| Control Panel and service | Manage customer accounts and services on which each account has access rights. | [https://ca.api.ovh.com/console/#/dbaas/logs](https://ca.api.ovh.com/console/#/dbaas/logs)) | + +## 7.Accounts - User + +### 7.1 Control plane + +Using your customer account on the OVHcloud Control Panel, you are able to manage your service using [three different contacts](/pages/account_and_service_management/account_information/managing_contacts).
+OVHcloud uses another account with an internal NIC to refer a customer having subscribed to several services. + +To enforce security access to your account on the Control Panel, we recommend activating a [two-factor authentication mechanism](/pages/account_and_service_management/account_information/secure-ovhcloud-account-with-2fa) or [SSO(Single Sign-On) authentication](/pages/account_and_service_management/account_information/ovhcloud-account-connect-saml-adfs). + +You can also [create your own IAM policy](/pages/account_and_service_management/account_information/iam-policy-ui) on the service, with a user interface or [via API](/pages/account_and_service_management/account_information/iam-policies-api), and manage your users and groups.
+You can troubleshoot your IAM policy configuration and analyse actions [by using API calls to get logs](/pages/manage_and_operate/iam/iam-troubleshooting). + +### 7.2 Data plane + +Once a VM is created by OVHcloud, on which the customer Analytics engines run, a TLS certificate is generated and used by the customer to access his DB. The certificate is renewed every three months. + +## 8.Features and options available at service delivery + +### 8.1 High availability + +Different plans are made available on the service: Essential, Business/Production and Enterprise/Advanced plans.
+You can choose a "Business/Production" or "Enterprise/Advanced" offer to benefit from a high availability service as your data will be replicated across multiple nodes following the chosen plan. + +### 8.2 Data encryption + +#### 8.2.1 Encryption made by the OVHcloud teams + +All network traffic on the infrastructure managing the Analytics service is encrypted. Services volumes are also encrypted with a unique key specific for each customer project.
+These operations are made, by default, by the OVHcloud operation team. + +> [!primary] +> +> Currently, OVHcloud does not offer KMS as a service, you cannot bring your own keys. KMIP is managed by OVHcloud. +> + +For a MongoDB engine : + +- **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. +The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. +We use the LUKS2 mode aes-cbc-essiv:sha256 with a 512-bit key. +- **Backups:** backups are encrypted with a randomly generated key. This key is Asymetric RSA4096. + +For all the Analytics engines such as Kafka, OpenSearch and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage: + +- **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. +The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. +We use the LUKS2 default mode aes-xts-plain64:sha256 with a 512-bit key. +- **Backups:** backups are encrypted with a randomly generated key per file. These keys are in turn encrypted with a RSA key-encryption key-pair and stored in the header section of each backup segment. +The file encryption is performed with AES-256 in CTR mode with HMAC-SHA256 for integrity protection. +The RSA key-pair is randomly generated for each service. The key lengths are 256-bit for block encryption, 512-bit for the integrity protection and 3072-bits for the RSA key. + + +#### 8.2.2 In-use encryption on client side + +> [!primary] +> +> Currently, OVHcloud does not offer a KMS as a service, you cannot bring your own keys. KMIP is managed by OVHcloud. +> + +Currently, we do not provide in-use encryption except for MongoDB Advanced plans, based on MongoDB Client-Side Field Level Encryption.
+Data is encrypted client-side with customer-controlled encryption keys, before being sent, stored, or retrieved from the service. + +### 8.3 CVE monitoring + +The OVHcloud operation team in charge of the maintenance of Public Cloud Analytics services is constantly monitoring CVE on the different DBMS available. This monitoring is done through different channels, official mailing lists, security community, internal security check...
+ +We are also in constant communication with the MongoDB team, in order to provide fast and smooth transition to the latest security version of MongoDB. + +### 8.4 vRack option + +You can activate the vRack option at the subscription step or afterwards and have your private network for your Analytics project. + +### 8.5 HDS option + +The HDS option can be activated on the service.
+This option is available only for "Business/Production" and "Enterprise/Advanced" plans for this service.
+The subscription to the Business support level is mandatory, at least to maintain necessary requirements. + +## 9.Reversibility + +You can import and export your data following recommendations provided by editors for each Analytics engine technology. + +### 9.1 Erasure of customer data + +Once you destroy your Public Cloud project (your Analytics project) in the OVHcloud Control Panel, all allocated resources are relased automtically, including used encryption keys.
+As the encryption keys are unique for each project, they will be deleted after service decommissioning. Data can not be retrieved after. + +## Go further + +[Public Cloud Analytics documentation](/products/public-cloud-data-analytics) + +Visit our dedicated Discord channel: . 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](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. diff --git a/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.en-gb.md b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.en-gb.md new file mode 100644 index 00000000000..f0851db31d7 --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.en-gb.md @@ -0,0 +1,164 @@ +--- +title: Analytics Concepts - Security overview +excerpt: Analytics security overview +updated: 2025-11-04 +--- + +## Objective + +In addition to [the responsibility model for Analytics services](/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/), this security fact sheets aims at describing security features and functions associated to the service. It describes also best practices that customers can adopt to secure their services. + +## 1.Certifications + +- ISO/IEC 27001 +- ISO/IEC 27701 +- ISO/IEC 27017 +- ISO/IEC 27018 +- HDS +- SOC 1 type 1 +- SOC 2 type 1 +- CSA type 1 +- C5 type 1 + +## 2.Best pratices to be deployed on the service + +### 2.1 Recommandations once the service is delivered + +Once you have followed [these first steps to subscribe your service](/pages/public_cloud/data_analytics/analytics/analytics_getting_started) and reset the default password communicated to access to the service, you must filter connections by using iptables.
+You can also activate a private connection by using the vRack option. + +### 2.2 Vulnerability scans + +You are authorized to perform vulnerability scans on the service you have subscribed to. OVHcloud doesn't have to be previously informed.
+Security measures deployed by OVHcloud (especially network protection) aren't disabled, because such an audit's purpose is to demonstrate a clear vision of the security level of the customer's infrastructure.
+You are not authorized to use your service to scan other infrastructures. + +## 3.SLA + +SLA are available only for "Business/Production" and "Enterprise/Advanced" plans of this service.
+SLA for the Business/Production range in Single AZ are 99,90%.
+SLA for the Enterprise/Advanced range in Single AZ are 99,95%.
+SLA for the Production range in Multi AZ are 99,95%.
+SLA for the Advanced range in Multi AZ are 99,99%.
+The calculation method of SLA consists of the total number of minutes in the month in question deducted from the number of minutes of unavailability over the month in question. The total is divided by the total number of minutes in the month. +Service credits can be 10%, 25 % or 100% of the hourly cost per hour of unavailability of the affected Service. You can refer to the Particular Conditions of the service to get more details about the monthly available rate for each service range or plan and credits limitation. + +## 4.Backups + +### 4.1 Technical backups + +Technical backups are backups made by OVHcloud to maintain the Service Level Agreement. These backups can not be activated at customer request. + +### 4.2 Customer data backups + +Customer data (DB) is backed up, automated and operated following different frequencies. Those backups are encrypted and uploaded to a remote, replicated storage backend, in a different datacenter from the one the analytics service is hosted on. Details about frequencies, RPO and locations are listed following type of services and ranges at [this link](/pages/public_cloud/data_analytics/analytics/information_05_automated_backups).
+Customer data backup health status is checked daily by OVHcloud.
+If you need to restore your data using a backup, you can follow [this guide](/pages/public_cloud/data_analytics/analytics/analytics_restore_backup) and create a new service for this purpose. + +## 5.Logs + +| **Source** | **Content** | **Documentation** | +| --- | --- | --- | +| Control Panel | Logs of interactions made by admin, technical or billing contacts in the Control Panel and services they have access to, using API calls. |- (see `/me/api/logs`)
- [List of API calls done with your account](https://api.ovh.com/console/#/me/api/logs/self~GET)
- [List of API calls done on services you have access to](https://api.ovh.com/console/#/me/api/logs/services~GET)
-[Get your audit logs](https://api.ovh.com/console/#/me/logs/audit~GET) | +| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Cassandra service as an example `/cloud/project/{serviceName}/database/cassandra/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | + +## 6.API + +| **Name** | **Capacity** | **Link** | +| --- | --- | --- | +| Control Panel and service | Manage customer accounts and services on which each account has access rights. | [https://eu.api.ovh.com/console/#/dbaas/logs](https://eu.api.ovh.com/console/#/dbaas/logs)) | + +## 7.Accounts - User + +### 7.1 Control plane + +Using your customer account on the OVHcloud Control Panel, you are able to manage your service using [three different contacts](/pages/account_and_service_management/account_information/managing_contacts).
+OVHcloud uses another account with an internal NIC to refer a customer having subscribed to several services. + +To enforce security access to your account on the Control Panel, we recommend activating a [two-factor authentication mechanism](/pages/account_and_service_management/account_information/secure-ovhcloud-account-with-2fa) or [SSO(Single Sign-On) authentication](/pages/account_and_service_management/account_information/ovhcloud-account-connect-saml-adfs). + +You can also [create your own IAM policy](/pages/account_and_service_management/account_information/iam-policy-ui) on the service, with a user interface or [via API](/pages/account_and_service_management/account_information/iam-policies-api), and manage your users and groups.
+You can troubleshoot your IAM policy configuration and analyse actions [by using API calls to get logs](/pages/manage_and_operate/iam/iam-troubleshooting). + +### 7.2 Data plane + +Once a VM is created by OVHcloud, on which the customer Analytics engines run, a TLS certificate is generated and used by the customer to access his DB. The certificate is renewed every three months. + +## 8.Features and options available at service delivery + +### 8.1 High availability + +Different plans are made available on the service: Essential, Business/Production and Enterprise/Advanced plans.
+You can choose a "Business/Production" or "Enterprise/Advanced" offer to benefit from a high availability service as your data will be replicated across multiple nodes following the chosen plan. + +### 8.2 Data encryption + +#### 8.2.1 Encryption made by the OVHcloud teams + +All network traffic on the infrastructure managing the Analytics service is encrypted. Services volumes are also encrypted with a unique key specific for each customer project.
+These operations are made, by default, by the OVHcloud operation team. + +> [!primary] +> +> Currently, OVHcloud does not offer KMS as a service, you cannot bring your own keys. KMIP is managed by OVHcloud. +> + +For a MongoDB engine : + +- **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. +The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. +We use the LUKS2 mode aes-cbc-essiv:sha256 with a 512-bit key. +- **Backups:** backups are encrypted with a randomly generated key. This key is Asymetric RSA4096. + +For all the Analytics engines such as Kafka, OpenSearch and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage: + +- **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. +The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. +We use the LUKS2 default mode aes-xts-plain64:sha256 with a 512-bit key. +- **Backups:** backups are encrypted with a randomly generated key per file. These keys are in turn encrypted with a RSA key-encryption key-pair and stored in the header section of each backup segment. +The file encryption is performed with AES-256 in CTR mode with HMAC-SHA256 for integrity protection. +The RSA key-pair is randomly generated for each service. The key lengths are 256-bit for block encryption, 512-bit for the integrity protection and 3072-bits for the RSA key. + + +#### 8.2.2 In-use encryption on client side + +> [!primary] +> +> Currently, OVHcloud does not offer a KMS as a service, you cannot bring your own keys. KMIP is managed by OVHcloud. +> + +Currently, we do not provide in-use encryption except for MongoDB Advanced plans, based on MongoDB Client-Side Field Level Encryption.
+Data is encrypted client-side with customer-controlled encryption keys, before being sent, stored, or retrieved from the service. + +### 8.3 CVE monitoring + +The OVHcloud operation team in charge of the maintenance of Public Cloud Analytics services is constantly monitoring CVE on the different DBMS available. This monitoring is done through different channels, official mailing lists, security community, internal security check...
+ +We are also in constant communication with the MongoDB team, in order to provide fast and smooth transition to the latest security version of MongoDB. + +### 8.4 vRack option + +You can activate the vRack option at the subscription step or afterwards and have your private network for your Analytics project. + +### 8.5 HDS option + +The HDS option can be activated on the service.
+This option is available only for "Business/Production" and "Enterprise/Advanced" plans for this service.
+The subscription to the Business support level is mandatory, at least to maintain necessary requirements. + +## 9.Reversibility + +You can import and export your data following recommendations provided by editors for each Analytics engine technology. + +### 9.1 Erasure of customer data + +Once you destroy your Public Cloud project (your Analytics project) in the OVHcloud Control Panel, all allocated resources are relased automtically, including used encryption keys.
+As the encryption keys are unique for each project, they will be deleted after service decommissioning. Data can not be retrieved after. + +## Go further + +[Public Cloud Analytics documentation](/products/public-cloud-data-analytics) + +Visit our dedicated Discord channel: . 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](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. diff --git a/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.en-ie.md b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.en-ie.md new file mode 100644 index 00000000000..f0851db31d7 --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.en-ie.md @@ -0,0 +1,164 @@ +--- +title: Analytics Concepts - Security overview +excerpt: Analytics security overview +updated: 2025-11-04 +--- + +## Objective + +In addition to [the responsibility model for Analytics services](/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/), this security fact sheets aims at describing security features and functions associated to the service. It describes also best practices that customers can adopt to secure their services. + +## 1.Certifications + +- ISO/IEC 27001 +- ISO/IEC 27701 +- ISO/IEC 27017 +- ISO/IEC 27018 +- HDS +- SOC 1 type 1 +- SOC 2 type 1 +- CSA type 1 +- C5 type 1 + +## 2.Best pratices to be deployed on the service + +### 2.1 Recommandations once the service is delivered + +Once you have followed [these first steps to subscribe your service](/pages/public_cloud/data_analytics/analytics/analytics_getting_started) and reset the default password communicated to access to the service, you must filter connections by using iptables.
+You can also activate a private connection by using the vRack option. + +### 2.2 Vulnerability scans + +You are authorized to perform vulnerability scans on the service you have subscribed to. OVHcloud doesn't have to be previously informed.
+Security measures deployed by OVHcloud (especially network protection) aren't disabled, because such an audit's purpose is to demonstrate a clear vision of the security level of the customer's infrastructure.
+You are not authorized to use your service to scan other infrastructures. + +## 3.SLA + +SLA are available only for "Business/Production" and "Enterprise/Advanced" plans of this service.
+SLA for the Business/Production range in Single AZ are 99,90%.
+SLA for the Enterprise/Advanced range in Single AZ are 99,95%.
+SLA for the Production range in Multi AZ are 99,95%.
+SLA for the Advanced range in Multi AZ are 99,99%.
+The calculation method of SLA consists of the total number of minutes in the month in question deducted from the number of minutes of unavailability over the month in question. The total is divided by the total number of minutes in the month. +Service credits can be 10%, 25 % or 100% of the hourly cost per hour of unavailability of the affected Service. You can refer to the Particular Conditions of the service to get more details about the monthly available rate for each service range or plan and credits limitation. + +## 4.Backups + +### 4.1 Technical backups + +Technical backups are backups made by OVHcloud to maintain the Service Level Agreement. These backups can not be activated at customer request. + +### 4.2 Customer data backups + +Customer data (DB) is backed up, automated and operated following different frequencies. Those backups are encrypted and uploaded to a remote, replicated storage backend, in a different datacenter from the one the analytics service is hosted on. Details about frequencies, RPO and locations are listed following type of services and ranges at [this link](/pages/public_cloud/data_analytics/analytics/information_05_automated_backups).
+Customer data backup health status is checked daily by OVHcloud.
+If you need to restore your data using a backup, you can follow [this guide](/pages/public_cloud/data_analytics/analytics/analytics_restore_backup) and create a new service for this purpose. + +## 5.Logs + +| **Source** | **Content** | **Documentation** | +| --- | --- | --- | +| Control Panel | Logs of interactions made by admin, technical or billing contacts in the Control Panel and services they have access to, using API calls. |- (see `/me/api/logs`)
- [List of API calls done with your account](https://api.ovh.com/console/#/me/api/logs/self~GET)
- [List of API calls done on services you have access to](https://api.ovh.com/console/#/me/api/logs/services~GET)
-[Get your audit logs](https://api.ovh.com/console/#/me/logs/audit~GET) | +| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Cassandra service as an example `/cloud/project/{serviceName}/database/cassandra/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | + +## 6.API + +| **Name** | **Capacity** | **Link** | +| --- | --- | --- | +| Control Panel and service | Manage customer accounts and services on which each account has access rights. | [https://eu.api.ovh.com/console/#/dbaas/logs](https://eu.api.ovh.com/console/#/dbaas/logs)) | + +## 7.Accounts - User + +### 7.1 Control plane + +Using your customer account on the OVHcloud Control Panel, you are able to manage your service using [three different contacts](/pages/account_and_service_management/account_information/managing_contacts).
+OVHcloud uses another account with an internal NIC to refer a customer having subscribed to several services. + +To enforce security access to your account on the Control Panel, we recommend activating a [two-factor authentication mechanism](/pages/account_and_service_management/account_information/secure-ovhcloud-account-with-2fa) or [SSO(Single Sign-On) authentication](/pages/account_and_service_management/account_information/ovhcloud-account-connect-saml-adfs). + +You can also [create your own IAM policy](/pages/account_and_service_management/account_information/iam-policy-ui) on the service, with a user interface or [via API](/pages/account_and_service_management/account_information/iam-policies-api), and manage your users and groups.
+You can troubleshoot your IAM policy configuration and analyse actions [by using API calls to get logs](/pages/manage_and_operate/iam/iam-troubleshooting). + +### 7.2 Data plane + +Once a VM is created by OVHcloud, on which the customer Analytics engines run, a TLS certificate is generated and used by the customer to access his DB. The certificate is renewed every three months. + +## 8.Features and options available at service delivery + +### 8.1 High availability + +Different plans are made available on the service: Essential, Business/Production and Enterprise/Advanced plans.
+You can choose a "Business/Production" or "Enterprise/Advanced" offer to benefit from a high availability service as your data will be replicated across multiple nodes following the chosen plan. + +### 8.2 Data encryption + +#### 8.2.1 Encryption made by the OVHcloud teams + +All network traffic on the infrastructure managing the Analytics service is encrypted. Services volumes are also encrypted with a unique key specific for each customer project.
+These operations are made, by default, by the OVHcloud operation team. + +> [!primary] +> +> Currently, OVHcloud does not offer KMS as a service, you cannot bring your own keys. KMIP is managed by OVHcloud. +> + +For a MongoDB engine : + +- **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. +The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. +We use the LUKS2 mode aes-cbc-essiv:sha256 with a 512-bit key. +- **Backups:** backups are encrypted with a randomly generated key. This key is Asymetric RSA4096. + +For all the Analytics engines such as Kafka, OpenSearch and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage: + +- **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. +The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. +We use the LUKS2 default mode aes-xts-plain64:sha256 with a 512-bit key. +- **Backups:** backups are encrypted with a randomly generated key per file. These keys are in turn encrypted with a RSA key-encryption key-pair and stored in the header section of each backup segment. +The file encryption is performed with AES-256 in CTR mode with HMAC-SHA256 for integrity protection. +The RSA key-pair is randomly generated for each service. The key lengths are 256-bit for block encryption, 512-bit for the integrity protection and 3072-bits for the RSA key. + + +#### 8.2.2 In-use encryption on client side + +> [!primary] +> +> Currently, OVHcloud does not offer a KMS as a service, you cannot bring your own keys. KMIP is managed by OVHcloud. +> + +Currently, we do not provide in-use encryption except for MongoDB Advanced plans, based on MongoDB Client-Side Field Level Encryption.
+Data is encrypted client-side with customer-controlled encryption keys, before being sent, stored, or retrieved from the service. + +### 8.3 CVE monitoring + +The OVHcloud operation team in charge of the maintenance of Public Cloud Analytics services is constantly monitoring CVE on the different DBMS available. This monitoring is done through different channels, official mailing lists, security community, internal security check...
+ +We are also in constant communication with the MongoDB team, in order to provide fast and smooth transition to the latest security version of MongoDB. + +### 8.4 vRack option + +You can activate the vRack option at the subscription step or afterwards and have your private network for your Analytics project. + +### 8.5 HDS option + +The HDS option can be activated on the service.
+This option is available only for "Business/Production" and "Enterprise/Advanced" plans for this service.
+The subscription to the Business support level is mandatory, at least to maintain necessary requirements. + +## 9.Reversibility + +You can import and export your data following recommendations provided by editors for each Analytics engine technology. + +### 9.1 Erasure of customer data + +Once you destroy your Public Cloud project (your Analytics project) in the OVHcloud Control Panel, all allocated resources are relased automtically, including used encryption keys.
+As the encryption keys are unique for each project, they will be deleted after service decommissioning. Data can not be retrieved after. + +## Go further + +[Public Cloud Analytics documentation](/products/public-cloud-data-analytics) + +Visit our dedicated Discord channel: . 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](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. diff --git a/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.en-sg.md b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.en-sg.md new file mode 100644 index 00000000000..3ce01881a35 --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.en-sg.md @@ -0,0 +1,164 @@ +--- +title: Analytics Concepts - Security overview +excerpt: Analytics security overview +updated: 2025-11-04 +--- + +## Objective + +In addition to [the responsibility model for Analytics services](/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/), this security fact sheets aims at describing security features and functions associated to the service. It describes also best practices that customers can adopt to secure their services. + +## 1.Certifications + +- ISO/IEC 27001 +- ISO/IEC 27701 +- ISO/IEC 27017 +- ISO/IEC 27018 +- HDS +- SOC 1 type 1 +- SOC 2 type 1 +- CSA type 1 +- C5 type 1 + +## 2.Best pratices to be deployed on the service + +### 2.1 Recommandations once the service is delivered + +Once you have followed [these first steps to subscribe your service](/pages/public_cloud/data_analytics/analytics/analytics_getting_started) and reset the default password communicated to access to the service, you must filter connections by using iptables.
+You can also activate a private connection by using the vRack option. + +### 2.2 Vulnerability scans + +You are authorized to perform vulnerability scans on the service you have subscribed to. OVHcloud doesn't have to be previously informed.
+Security measures deployed by OVHcloud (especially network protection) aren't disabled, because such an audit's purpose is to demonstrate a clear vision of the security level of the customer's infrastructure.
+You are not authorized to use your service to scan other infrastructures. + +## 3.SLA + +SLA are available only for "Business/Production" and "Enterprise/Advanced" plans of this service.
+SLA for the Business/Production range in Single AZ are 99,90%.
+SLA for the Enterprise/Advanced range in Single AZ are 99,95%.
+SLA for the Production range in Multi AZ are 99,95%.
+SLA for the Advanced range in Multi AZ are 99,99%.
+The calculation method of SLA consists of the total number of minutes in the month in question deducted from the number of minutes of unavailability over the month in question. The total is divided by the total number of minutes in the month. +Service credits can be 10%, 25 % or 100% of the hourly cost per hour of unavailability of the affected Service. You can refer to the Particular Conditions of the service to get more details about the monthly available rate for each service range or plan and credits limitation. + +## 4.Backups + +### 4.1 Technical backups + +Technical backups are backups made by OVHcloud to maintain the Service Level Agreement. These backups can not be activated at customer request. + +### 4.2 Customer data backups + +Customer data (DB) is backed up, automated and operated following different frequencies. Those backups are encrypted and uploaded to a remote, replicated storage backend, in a different datacenter from the one the analytics service is hosted on. Details about frequencies, RPO and locations are listed following type of services and ranges at [this link](/pages/public_cloud/data_analytics/analytics/information_05_automated_backups).
+Customer data backup health status is checked daily by OVHcloud.
+If you need to restore your data using a backup, you can follow [this guide](/pages/public_cloud/data_analytics/analytics/analytics_restore_backup) and create a new service for this purpose. + +## 5.Logs + +| **Source** | **Content** | **Documentation** | +| --- | --- | --- | +| Control Panel | Logs of interactions made by admin, technical or billing contacts in the Control Panel and services they have access to, using API calls. |- (see `/me/api/logs`)
- [List of API calls done with your account](https://api.ovh.com/console/#/me/api/logs/self~GET)
- [List of API calls done on services you have access to](https://api.ovh.com/console/#/me/api/logs/services~GET)
-[Get your audit logs](https://api.ovh.com/console/#/me/logs/audit~GET) | +| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Cassandra service as an example `/cloud/project/{serviceName}/database/cassandra/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | + +## 6.API + +| **Name** | **Capacity** | **Link** | +| --- | --- | --- | +| Control Panel and service | Manage customer accounts and services on which each account has access rights. | [https://ca.api.ovh.com/console/#/dbaas/logs](https://ca.api.ovh.com/console/#/dbaas/logs)) | + +## 7.Accounts - User + +### 7.1 Control plane + +Using your customer account on the OVHcloud Control Panel, you are able to manage your service using [three different contacts](/pages/account_and_service_management/account_information/managing_contacts).
+OVHcloud uses another account with an internal NIC to refer a customer having subscribed to several services. + +To enforce security access to your account on the Control Panel, we recommend activating a [two-factor authentication mechanism](/pages/account_and_service_management/account_information/secure-ovhcloud-account-with-2fa) or [SSO(Single Sign-On) authentication](/pages/account_and_service_management/account_information/ovhcloud-account-connect-saml-adfs). + +You can also [create your own IAM policy](/pages/account_and_service_management/account_information/iam-policy-ui) on the service, with a user interface or [via API](/pages/account_and_service_management/account_information/iam-policies-api), and manage your users and groups.
+You can troubleshoot your IAM policy configuration and analyse actions [by using API calls to get logs](/pages/manage_and_operate/iam/iam-troubleshooting). + +### 7.2 Data plane + +Once a VM is created by OVHcloud, on which the customer Analytics engines run, a TLS certificate is generated and used by the customer to access his DB. The certificate is renewed every three months. + +## 8.Features and options available at service delivery + +### 8.1 High availability + +Different plans are made available on the service: Essential, Business/Production and Enterprise/Advanced plans.
+You can choose a "Business/Production" or "Enterprise/Advanced" offer to benefit from a high availability service as your data will be replicated across multiple nodes following the chosen plan. + +### 8.2 Data encryption + +#### 8.2.1 Encryption made by the OVHcloud teams + +All network traffic on the infrastructure managing the Analytics service is encrypted. Services volumes are also encrypted with a unique key specific for each customer project.
+These operations are made, by default, by the OVHcloud operation team. + +> [!primary] +> +> Currently, OVHcloud does not offer KMS as a service, you cannot bring your own keys. KMIP is managed by OVHcloud. +> + +For a MongoDB engine : + +- **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. +The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. +We use the LUKS2 mode aes-cbc-essiv:sha256 with a 512-bit key. +- **Backups:** backups are encrypted with a randomly generated key. This key is Asymetric RSA4096. + +For all the Analytics engines such as Kafka, OpenSearch and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage: + +- **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. +The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. +We use the LUKS2 default mode aes-xts-plain64:sha256 with a 512-bit key. +- **Backups:** backups are encrypted with a randomly generated key per file. These keys are in turn encrypted with a RSA key-encryption key-pair and stored in the header section of each backup segment. +The file encryption is performed with AES-256 in CTR mode with HMAC-SHA256 for integrity protection. +The RSA key-pair is randomly generated for each service. The key lengths are 256-bit for block encryption, 512-bit for the integrity protection and 3072-bits for the RSA key. + + +#### 8.2.2 In-use encryption on client side + +> [!primary] +> +> Currently, OVHcloud does not offer a KMS as a service, you cannot bring your own keys. KMIP is managed by OVHcloud. +> + +Currently, we do not provide in-use encryption except for MongoDB Advanced plans, based on MongoDB Client-Side Field Level Encryption.
+Data is encrypted client-side with customer-controlled encryption keys, before being sent, stored, or retrieved from the service. + +### 8.3 CVE monitoring + +The OVHcloud operation team in charge of the maintenance of Public Cloud Analytics services is constantly monitoring CVE on the different DBMS available. This monitoring is done through different channels, official mailing lists, security community, internal security check...
+ +We are also in constant communication with the MongoDB team, in order to provide fast and smooth transition to the latest security version of MongoDB. + +### 8.4 vRack option + +You can activate the vRack option at the subscription step or afterwards and have your private network for your Analytics project. + +### 8.5 HDS option + +The HDS option can be activated on the service.
+This option is available only for "Business/Production" and "Enterprise/Advanced" plans for this service.
+The subscription to the Business support level is mandatory, at least to maintain necessary requirements. + +## 9.Reversibility + +You can import and export your data following recommendations provided by editors for each Analytics engine technology. + +### 9.1 Erasure of customer data + +Once you destroy your Public Cloud project (your Analytics project) in the OVHcloud Control Panel, all allocated resources are relased automtically, including used encryption keys.
+As the encryption keys are unique for each project, they will be deleted after service decommissioning. Data can not be retrieved after. + +## Go further + +[Public Cloud Analytics documentation](/products/public-cloud-data-analytics) + +Visit our dedicated Discord channel: . 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](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. diff --git a/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.en-us.md b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.en-us.md new file mode 100644 index 00000000000..3ce01881a35 --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.en-us.md @@ -0,0 +1,164 @@ +--- +title: Analytics Concepts - Security overview +excerpt: Analytics security overview +updated: 2025-11-04 +--- + +## Objective + +In addition to [the responsibility model for Analytics services](/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/), this security fact sheets aims at describing security features and functions associated to the service. It describes also best practices that customers can adopt to secure their services. + +## 1.Certifications + +- ISO/IEC 27001 +- ISO/IEC 27701 +- ISO/IEC 27017 +- ISO/IEC 27018 +- HDS +- SOC 1 type 1 +- SOC 2 type 1 +- CSA type 1 +- C5 type 1 + +## 2.Best pratices to be deployed on the service + +### 2.1 Recommandations once the service is delivered + +Once you have followed [these first steps to subscribe your service](/pages/public_cloud/data_analytics/analytics/analytics_getting_started) and reset the default password communicated to access to the service, you must filter connections by using iptables.
+You can also activate a private connection by using the vRack option. + +### 2.2 Vulnerability scans + +You are authorized to perform vulnerability scans on the service you have subscribed to. OVHcloud doesn't have to be previously informed.
+Security measures deployed by OVHcloud (especially network protection) aren't disabled, because such an audit's purpose is to demonstrate a clear vision of the security level of the customer's infrastructure.
+You are not authorized to use your service to scan other infrastructures. + +## 3.SLA + +SLA are available only for "Business/Production" and "Enterprise/Advanced" plans of this service.
+SLA for the Business/Production range in Single AZ are 99,90%.
+SLA for the Enterprise/Advanced range in Single AZ are 99,95%.
+SLA for the Production range in Multi AZ are 99,95%.
+SLA for the Advanced range in Multi AZ are 99,99%.
+The calculation method of SLA consists of the total number of minutes in the month in question deducted from the number of minutes of unavailability over the month in question. The total is divided by the total number of minutes in the month. +Service credits can be 10%, 25 % or 100% of the hourly cost per hour of unavailability of the affected Service. You can refer to the Particular Conditions of the service to get more details about the monthly available rate for each service range or plan and credits limitation. + +## 4.Backups + +### 4.1 Technical backups + +Technical backups are backups made by OVHcloud to maintain the Service Level Agreement. These backups can not be activated at customer request. + +### 4.2 Customer data backups + +Customer data (DB) is backed up, automated and operated following different frequencies. Those backups are encrypted and uploaded to a remote, replicated storage backend, in a different datacenter from the one the analytics service is hosted on. Details about frequencies, RPO and locations are listed following type of services and ranges at [this link](/pages/public_cloud/data_analytics/analytics/information_05_automated_backups).
+Customer data backup health status is checked daily by OVHcloud.
+If you need to restore your data using a backup, you can follow [this guide](/pages/public_cloud/data_analytics/analytics/analytics_restore_backup) and create a new service for this purpose. + +## 5.Logs + +| **Source** | **Content** | **Documentation** | +| --- | --- | --- | +| Control Panel | Logs of interactions made by admin, technical or billing contacts in the Control Panel and services they have access to, using API calls. |- (see `/me/api/logs`)
- [List of API calls done with your account](https://api.ovh.com/console/#/me/api/logs/self~GET)
- [List of API calls done on services you have access to](https://api.ovh.com/console/#/me/api/logs/services~GET)
-[Get your audit logs](https://api.ovh.com/console/#/me/logs/audit~GET) | +| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Cassandra service as an example `/cloud/project/{serviceName}/database/cassandra/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | + +## 6.API + +| **Name** | **Capacity** | **Link** | +| --- | --- | --- | +| Control Panel and service | Manage customer accounts and services on which each account has access rights. | [https://ca.api.ovh.com/console/#/dbaas/logs](https://ca.api.ovh.com/console/#/dbaas/logs)) | + +## 7.Accounts - User + +### 7.1 Control plane + +Using your customer account on the OVHcloud Control Panel, you are able to manage your service using [three different contacts](/pages/account_and_service_management/account_information/managing_contacts).
+OVHcloud uses another account with an internal NIC to refer a customer having subscribed to several services. + +To enforce security access to your account on the Control Panel, we recommend activating a [two-factor authentication mechanism](/pages/account_and_service_management/account_information/secure-ovhcloud-account-with-2fa) or [SSO(Single Sign-On) authentication](/pages/account_and_service_management/account_information/ovhcloud-account-connect-saml-adfs). + +You can also [create your own IAM policy](/pages/account_and_service_management/account_information/iam-policy-ui) on the service, with a user interface or [via API](/pages/account_and_service_management/account_information/iam-policies-api), and manage your users and groups.
+You can troubleshoot your IAM policy configuration and analyse actions [by using API calls to get logs](/pages/manage_and_operate/iam/iam-troubleshooting). + +### 7.2 Data plane + +Once a VM is created by OVHcloud, on which the customer Analytics engines run, a TLS certificate is generated and used by the customer to access his DB. The certificate is renewed every three months. + +## 8.Features and options available at service delivery + +### 8.1 High availability + +Different plans are made available on the service: Essential, Business/Production and Enterprise/Advanced plans.
+You can choose a "Business/Production" or "Enterprise/Advanced" offer to benefit from a high availability service as your data will be replicated across multiple nodes following the chosen plan. + +### 8.2 Data encryption + +#### 8.2.1 Encryption made by the OVHcloud teams + +All network traffic on the infrastructure managing the Analytics service is encrypted. Services volumes are also encrypted with a unique key specific for each customer project.
+These operations are made, by default, by the OVHcloud operation team. + +> [!primary] +> +> Currently, OVHcloud does not offer KMS as a service, you cannot bring your own keys. KMIP is managed by OVHcloud. +> + +For a MongoDB engine : + +- **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. +The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. +We use the LUKS2 mode aes-cbc-essiv:sha256 with a 512-bit key. +- **Backups:** backups are encrypted with a randomly generated key. This key is Asymetric RSA4096. + +For all the Analytics engines such as Kafka, OpenSearch and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage: + +- **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. +The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. +We use the LUKS2 default mode aes-xts-plain64:sha256 with a 512-bit key. +- **Backups:** backups are encrypted with a randomly generated key per file. These keys are in turn encrypted with a RSA key-encryption key-pair and stored in the header section of each backup segment. +The file encryption is performed with AES-256 in CTR mode with HMAC-SHA256 for integrity protection. +The RSA key-pair is randomly generated for each service. The key lengths are 256-bit for block encryption, 512-bit for the integrity protection and 3072-bits for the RSA key. + + +#### 8.2.2 In-use encryption on client side + +> [!primary] +> +> Currently, OVHcloud does not offer a KMS as a service, you cannot bring your own keys. KMIP is managed by OVHcloud. +> + +Currently, we do not provide in-use encryption except for MongoDB Advanced plans, based on MongoDB Client-Side Field Level Encryption.
+Data is encrypted client-side with customer-controlled encryption keys, before being sent, stored, or retrieved from the service. + +### 8.3 CVE monitoring + +The OVHcloud operation team in charge of the maintenance of Public Cloud Analytics services is constantly monitoring CVE on the different DBMS available. This monitoring is done through different channels, official mailing lists, security community, internal security check...
+ +We are also in constant communication with the MongoDB team, in order to provide fast and smooth transition to the latest security version of MongoDB. + +### 8.4 vRack option + +You can activate the vRack option at the subscription step or afterwards and have your private network for your Analytics project. + +### 8.5 HDS option + +The HDS option can be activated on the service.
+This option is available only for "Business/Production" and "Enterprise/Advanced" plans for this service.
+The subscription to the Business support level is mandatory, at least to maintain necessary requirements. + +## 9.Reversibility + +You can import and export your data following recommendations provided by editors for each Analytics engine technology. + +### 9.1 Erasure of customer data + +Once you destroy your Public Cloud project (your Analytics project) in the OVHcloud Control Panel, all allocated resources are relased automtically, including used encryption keys.
+As the encryption keys are unique for each project, they will be deleted after service decommissioning. Data can not be retrieved after. + +## Go further + +[Public Cloud Analytics documentation](/products/public-cloud-data-analytics) + +Visit our dedicated Discord channel: . 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](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. diff --git a/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.es-es.md b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.es-es.md new file mode 100644 index 00000000000..f0851db31d7 --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.es-es.md @@ -0,0 +1,164 @@ +--- +title: Analytics Concepts - Security overview +excerpt: Analytics security overview +updated: 2025-11-04 +--- + +## Objective + +In addition to [the responsibility model for Analytics services](/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/), this security fact sheets aims at describing security features and functions associated to the service. It describes also best practices that customers can adopt to secure their services. + +## 1.Certifications + +- ISO/IEC 27001 +- ISO/IEC 27701 +- ISO/IEC 27017 +- ISO/IEC 27018 +- HDS +- SOC 1 type 1 +- SOC 2 type 1 +- CSA type 1 +- C5 type 1 + +## 2.Best pratices to be deployed on the service + +### 2.1 Recommandations once the service is delivered + +Once you have followed [these first steps to subscribe your service](/pages/public_cloud/data_analytics/analytics/analytics_getting_started) and reset the default password communicated to access to the service, you must filter connections by using iptables.
+You can also activate a private connection by using the vRack option. + +### 2.2 Vulnerability scans + +You are authorized to perform vulnerability scans on the service you have subscribed to. OVHcloud doesn't have to be previously informed.
+Security measures deployed by OVHcloud (especially network protection) aren't disabled, because such an audit's purpose is to demonstrate a clear vision of the security level of the customer's infrastructure.
+You are not authorized to use your service to scan other infrastructures. + +## 3.SLA + +SLA are available only for "Business/Production" and "Enterprise/Advanced" plans of this service.
+SLA for the Business/Production range in Single AZ are 99,90%.
+SLA for the Enterprise/Advanced range in Single AZ are 99,95%.
+SLA for the Production range in Multi AZ are 99,95%.
+SLA for the Advanced range in Multi AZ are 99,99%.
+The calculation method of SLA consists of the total number of minutes in the month in question deducted from the number of minutes of unavailability over the month in question. The total is divided by the total number of minutes in the month. +Service credits can be 10%, 25 % or 100% of the hourly cost per hour of unavailability of the affected Service. You can refer to the Particular Conditions of the service to get more details about the monthly available rate for each service range or plan and credits limitation. + +## 4.Backups + +### 4.1 Technical backups + +Technical backups are backups made by OVHcloud to maintain the Service Level Agreement. These backups can not be activated at customer request. + +### 4.2 Customer data backups + +Customer data (DB) is backed up, automated and operated following different frequencies. Those backups are encrypted and uploaded to a remote, replicated storage backend, in a different datacenter from the one the analytics service is hosted on. Details about frequencies, RPO and locations are listed following type of services and ranges at [this link](/pages/public_cloud/data_analytics/analytics/information_05_automated_backups).
+Customer data backup health status is checked daily by OVHcloud.
+If you need to restore your data using a backup, you can follow [this guide](/pages/public_cloud/data_analytics/analytics/analytics_restore_backup) and create a new service for this purpose. + +## 5.Logs + +| **Source** | **Content** | **Documentation** | +| --- | --- | --- | +| Control Panel | Logs of interactions made by admin, technical or billing contacts in the Control Panel and services they have access to, using API calls. |- (see `/me/api/logs`)
- [List of API calls done with your account](https://api.ovh.com/console/#/me/api/logs/self~GET)
- [List of API calls done on services you have access to](https://api.ovh.com/console/#/me/api/logs/services~GET)
-[Get your audit logs](https://api.ovh.com/console/#/me/logs/audit~GET) | +| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Cassandra service as an example `/cloud/project/{serviceName}/database/cassandra/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | + +## 6.API + +| **Name** | **Capacity** | **Link** | +| --- | --- | --- | +| Control Panel and service | Manage customer accounts and services on which each account has access rights. | [https://eu.api.ovh.com/console/#/dbaas/logs](https://eu.api.ovh.com/console/#/dbaas/logs)) | + +## 7.Accounts - User + +### 7.1 Control plane + +Using your customer account on the OVHcloud Control Panel, you are able to manage your service using [three different contacts](/pages/account_and_service_management/account_information/managing_contacts).
+OVHcloud uses another account with an internal NIC to refer a customer having subscribed to several services. + +To enforce security access to your account on the Control Panel, we recommend activating a [two-factor authentication mechanism](/pages/account_and_service_management/account_information/secure-ovhcloud-account-with-2fa) or [SSO(Single Sign-On) authentication](/pages/account_and_service_management/account_information/ovhcloud-account-connect-saml-adfs). + +You can also [create your own IAM policy](/pages/account_and_service_management/account_information/iam-policy-ui) on the service, with a user interface or [via API](/pages/account_and_service_management/account_information/iam-policies-api), and manage your users and groups.
+You can troubleshoot your IAM policy configuration and analyse actions [by using API calls to get logs](/pages/manage_and_operate/iam/iam-troubleshooting). + +### 7.2 Data plane + +Once a VM is created by OVHcloud, on which the customer Analytics engines run, a TLS certificate is generated and used by the customer to access his DB. The certificate is renewed every three months. + +## 8.Features and options available at service delivery + +### 8.1 High availability + +Different plans are made available on the service: Essential, Business/Production and Enterprise/Advanced plans.
+You can choose a "Business/Production" or "Enterprise/Advanced" offer to benefit from a high availability service as your data will be replicated across multiple nodes following the chosen plan. + +### 8.2 Data encryption + +#### 8.2.1 Encryption made by the OVHcloud teams + +All network traffic on the infrastructure managing the Analytics service is encrypted. Services volumes are also encrypted with a unique key specific for each customer project.
+These operations are made, by default, by the OVHcloud operation team. + +> [!primary] +> +> Currently, OVHcloud does not offer KMS as a service, you cannot bring your own keys. KMIP is managed by OVHcloud. +> + +For a MongoDB engine : + +- **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. +The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. +We use the LUKS2 mode aes-cbc-essiv:sha256 with a 512-bit key. +- **Backups:** backups are encrypted with a randomly generated key. This key is Asymetric RSA4096. + +For all the Analytics engines such as Kafka, OpenSearch and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage: + +- **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. +The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. +We use the LUKS2 default mode aes-xts-plain64:sha256 with a 512-bit key. +- **Backups:** backups are encrypted with a randomly generated key per file. These keys are in turn encrypted with a RSA key-encryption key-pair and stored in the header section of each backup segment. +The file encryption is performed with AES-256 in CTR mode with HMAC-SHA256 for integrity protection. +The RSA key-pair is randomly generated for each service. The key lengths are 256-bit for block encryption, 512-bit for the integrity protection and 3072-bits for the RSA key. + + +#### 8.2.2 In-use encryption on client side + +> [!primary] +> +> Currently, OVHcloud does not offer a KMS as a service, you cannot bring your own keys. KMIP is managed by OVHcloud. +> + +Currently, we do not provide in-use encryption except for MongoDB Advanced plans, based on MongoDB Client-Side Field Level Encryption.
+Data is encrypted client-side with customer-controlled encryption keys, before being sent, stored, or retrieved from the service. + +### 8.3 CVE monitoring + +The OVHcloud operation team in charge of the maintenance of Public Cloud Analytics services is constantly monitoring CVE on the different DBMS available. This monitoring is done through different channels, official mailing lists, security community, internal security check...
+ +We are also in constant communication with the MongoDB team, in order to provide fast and smooth transition to the latest security version of MongoDB. + +### 8.4 vRack option + +You can activate the vRack option at the subscription step or afterwards and have your private network for your Analytics project. + +### 8.5 HDS option + +The HDS option can be activated on the service.
+This option is available only for "Business/Production" and "Enterprise/Advanced" plans for this service.
+The subscription to the Business support level is mandatory, at least to maintain necessary requirements. + +## 9.Reversibility + +You can import and export your data following recommendations provided by editors for each Analytics engine technology. + +### 9.1 Erasure of customer data + +Once you destroy your Public Cloud project (your Analytics project) in the OVHcloud Control Panel, all allocated resources are relased automtically, including used encryption keys.
+As the encryption keys are unique for each project, they will be deleted after service decommissioning. Data can not be retrieved after. + +## Go further + +[Public Cloud Analytics documentation](/products/public-cloud-data-analytics) + +Visit our dedicated Discord channel: . 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](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. diff --git a/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.es-us.md b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.es-us.md new file mode 100644 index 00000000000..3ce01881a35 --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.es-us.md @@ -0,0 +1,164 @@ +--- +title: Analytics Concepts - Security overview +excerpt: Analytics security overview +updated: 2025-11-04 +--- + +## Objective + +In addition to [the responsibility model for Analytics services](/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/), this security fact sheets aims at describing security features and functions associated to the service. It describes also best practices that customers can adopt to secure their services. + +## 1.Certifications + +- ISO/IEC 27001 +- ISO/IEC 27701 +- ISO/IEC 27017 +- ISO/IEC 27018 +- HDS +- SOC 1 type 1 +- SOC 2 type 1 +- CSA type 1 +- C5 type 1 + +## 2.Best pratices to be deployed on the service + +### 2.1 Recommandations once the service is delivered + +Once you have followed [these first steps to subscribe your service](/pages/public_cloud/data_analytics/analytics/analytics_getting_started) and reset the default password communicated to access to the service, you must filter connections by using iptables.
+You can also activate a private connection by using the vRack option. + +### 2.2 Vulnerability scans + +You are authorized to perform vulnerability scans on the service you have subscribed to. OVHcloud doesn't have to be previously informed.
+Security measures deployed by OVHcloud (especially network protection) aren't disabled, because such an audit's purpose is to demonstrate a clear vision of the security level of the customer's infrastructure.
+You are not authorized to use your service to scan other infrastructures. + +## 3.SLA + +SLA are available only for "Business/Production" and "Enterprise/Advanced" plans of this service.
+SLA for the Business/Production range in Single AZ are 99,90%.
+SLA for the Enterprise/Advanced range in Single AZ are 99,95%.
+SLA for the Production range in Multi AZ are 99,95%.
+SLA for the Advanced range in Multi AZ are 99,99%.
+The calculation method of SLA consists of the total number of minutes in the month in question deducted from the number of minutes of unavailability over the month in question. The total is divided by the total number of minutes in the month. +Service credits can be 10%, 25 % or 100% of the hourly cost per hour of unavailability of the affected Service. You can refer to the Particular Conditions of the service to get more details about the monthly available rate for each service range or plan and credits limitation. + +## 4.Backups + +### 4.1 Technical backups + +Technical backups are backups made by OVHcloud to maintain the Service Level Agreement. These backups can not be activated at customer request. + +### 4.2 Customer data backups + +Customer data (DB) is backed up, automated and operated following different frequencies. Those backups are encrypted and uploaded to a remote, replicated storage backend, in a different datacenter from the one the analytics service is hosted on. Details about frequencies, RPO and locations are listed following type of services and ranges at [this link](/pages/public_cloud/data_analytics/analytics/information_05_automated_backups).
+Customer data backup health status is checked daily by OVHcloud.
+If you need to restore your data using a backup, you can follow [this guide](/pages/public_cloud/data_analytics/analytics/analytics_restore_backup) and create a new service for this purpose. + +## 5.Logs + +| **Source** | **Content** | **Documentation** | +| --- | --- | --- | +| Control Panel | Logs of interactions made by admin, technical or billing contacts in the Control Panel and services they have access to, using API calls. |- (see `/me/api/logs`)
- [List of API calls done with your account](https://api.ovh.com/console/#/me/api/logs/self~GET)
- [List of API calls done on services you have access to](https://api.ovh.com/console/#/me/api/logs/services~GET)
-[Get your audit logs](https://api.ovh.com/console/#/me/logs/audit~GET) | +| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Cassandra service as an example `/cloud/project/{serviceName}/database/cassandra/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | + +## 6.API + +| **Name** | **Capacity** | **Link** | +| --- | --- | --- | +| Control Panel and service | Manage customer accounts and services on which each account has access rights. | [https://ca.api.ovh.com/console/#/dbaas/logs](https://ca.api.ovh.com/console/#/dbaas/logs)) | + +## 7.Accounts - User + +### 7.1 Control plane + +Using your customer account on the OVHcloud Control Panel, you are able to manage your service using [three different contacts](/pages/account_and_service_management/account_information/managing_contacts).
+OVHcloud uses another account with an internal NIC to refer a customer having subscribed to several services. + +To enforce security access to your account on the Control Panel, we recommend activating a [two-factor authentication mechanism](/pages/account_and_service_management/account_information/secure-ovhcloud-account-with-2fa) or [SSO(Single Sign-On) authentication](/pages/account_and_service_management/account_information/ovhcloud-account-connect-saml-adfs). + +You can also [create your own IAM policy](/pages/account_and_service_management/account_information/iam-policy-ui) on the service, with a user interface or [via API](/pages/account_and_service_management/account_information/iam-policies-api), and manage your users and groups.
+You can troubleshoot your IAM policy configuration and analyse actions [by using API calls to get logs](/pages/manage_and_operate/iam/iam-troubleshooting). + +### 7.2 Data plane + +Once a VM is created by OVHcloud, on which the customer Analytics engines run, a TLS certificate is generated and used by the customer to access his DB. The certificate is renewed every three months. + +## 8.Features and options available at service delivery + +### 8.1 High availability + +Different plans are made available on the service: Essential, Business/Production and Enterprise/Advanced plans.
+You can choose a "Business/Production" or "Enterprise/Advanced" offer to benefit from a high availability service as your data will be replicated across multiple nodes following the chosen plan. + +### 8.2 Data encryption + +#### 8.2.1 Encryption made by the OVHcloud teams + +All network traffic on the infrastructure managing the Analytics service is encrypted. Services volumes are also encrypted with a unique key specific for each customer project.
+These operations are made, by default, by the OVHcloud operation team. + +> [!primary] +> +> Currently, OVHcloud does not offer KMS as a service, you cannot bring your own keys. KMIP is managed by OVHcloud. +> + +For a MongoDB engine : + +- **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. +The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. +We use the LUKS2 mode aes-cbc-essiv:sha256 with a 512-bit key. +- **Backups:** backups are encrypted with a randomly generated key. This key is Asymetric RSA4096. + +For all the Analytics engines such as Kafka, OpenSearch and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage: + +- **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. +The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. +We use the LUKS2 default mode aes-xts-plain64:sha256 with a 512-bit key. +- **Backups:** backups are encrypted with a randomly generated key per file. These keys are in turn encrypted with a RSA key-encryption key-pair and stored in the header section of each backup segment. +The file encryption is performed with AES-256 in CTR mode with HMAC-SHA256 for integrity protection. +The RSA key-pair is randomly generated for each service. The key lengths are 256-bit for block encryption, 512-bit for the integrity protection and 3072-bits for the RSA key. + + +#### 8.2.2 In-use encryption on client side + +> [!primary] +> +> Currently, OVHcloud does not offer a KMS as a service, you cannot bring your own keys. KMIP is managed by OVHcloud. +> + +Currently, we do not provide in-use encryption except for MongoDB Advanced plans, based on MongoDB Client-Side Field Level Encryption.
+Data is encrypted client-side with customer-controlled encryption keys, before being sent, stored, or retrieved from the service. + +### 8.3 CVE monitoring + +The OVHcloud operation team in charge of the maintenance of Public Cloud Analytics services is constantly monitoring CVE on the different DBMS available. This monitoring is done through different channels, official mailing lists, security community, internal security check...
+ +We are also in constant communication with the MongoDB team, in order to provide fast and smooth transition to the latest security version of MongoDB. + +### 8.4 vRack option + +You can activate the vRack option at the subscription step or afterwards and have your private network for your Analytics project. + +### 8.5 HDS option + +The HDS option can be activated on the service.
+This option is available only for "Business/Production" and "Enterprise/Advanced" plans for this service.
+The subscription to the Business support level is mandatory, at least to maintain necessary requirements. + +## 9.Reversibility + +You can import and export your data following recommendations provided by editors for each Analytics engine technology. + +### 9.1 Erasure of customer data + +Once you destroy your Public Cloud project (your Analytics project) in the OVHcloud Control Panel, all allocated resources are relased automtically, including used encryption keys.
+As the encryption keys are unique for each project, they will be deleted after service decommissioning. Data can not be retrieved after. + +## Go further + +[Public Cloud Analytics documentation](/products/public-cloud-data-analytics) + +Visit our dedicated Discord channel: . 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](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. diff --git a/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.fr-ca.md b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.fr-ca.md new file mode 100644 index 00000000000..7965c63a27a --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.fr-ca.md @@ -0,0 +1,164 @@ +--- +title: Analytics Concepts - Présentation de la sécurité (EN) +excerpt: Analytics security overview +updated: 2025-11-04 +--- + +## Objective + +In addition to [the responsibility model for Analytics services](/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/), this security fact sheets aims at describing security features and functions associated to the service. It describes also best practices that customers can adopt to secure their services. + +## 1.Certifications + +- ISO/IEC 27001 +- ISO/IEC 27701 +- ISO/IEC 27017 +- ISO/IEC 27018 +- HDS +- SOC 1 type 1 +- SOC 2 type 1 +- CSA type 1 +- C5 type 1 + +## 2.Best pratices to be deployed on the service + +### 2.1 Recommandations once the service is delivered + +Once you have followed [these first steps to subscribe your service](/pages/public_cloud/data_analytics/analytics/analytics_getting_started) and reset the default password communicated to access to the service, you must filter connections by using iptables.
+You can also activate a private connection by using the vRack option. + +### 2.2 Vulnerability scans + +You are authorized to perform vulnerability scans on the service you have subscribed to. OVHcloud doesn't have to be previously informed.
+Security measures deployed by OVHcloud (especially network protection) aren't disabled, because such an audit's purpose is to demonstrate a clear vision of the security level of the customer's infrastructure.
+You are not authorized to use your service to scan other infrastructures. + +## 3.SLA + +SLA are available only for "Business/Production" and "Enterprise/Advanced" plans of this service.
+SLA for the Business/Production range in Single AZ are 99,90%.
+SLA for the Enterprise/Advanced range in Single AZ are 99,95%.
+SLA for the Production range in Multi AZ are 99,95%.
+SLA for the Advanced range in Multi AZ are 99,99%.
+The calculation method of SLA consists of the total number of minutes in the month in question deducted from the number of minutes of unavailability over the month in question. The total is divided by the total number of minutes in the month. +Service credits can be 10%, 25 % or 100% of the hourly cost per hour of unavailability of the affected Service. You can refer to the Particular Conditions of the service to get more details about the monthly available rate for each service range or plan and credits limitation. + +## 4.Backups + +### 4.1 Technical backups + +Technical backups are backups made by OVHcloud to maintain the Service Level Agreement. These backups can not be activated at customer request. + +### 4.2 Customer data backups + +Customer data (DB) is backed up, automated and operated following different frequencies. Those backups are encrypted and uploaded to a remote, replicated storage backend, in a different datacenter from the one the analytics service is hosted on. Details about frequencies, RPO and locations are listed following type of services and ranges at [this link](/pages/public_cloud/data_analytics/analytics/information_05_automated_backups).
+Customer data backup health status is checked daily by OVHcloud.
+If you need to restore your data using a backup, you can follow [this guide](/pages/public_cloud/data_analytics/analytics/analytics_restore_backup) and create a new service for this purpose. + +## 5.Logs + +| **Source** | **Content** | **Documentation** | +| --- | --- | --- | +| Control Panel | Logs of interactions made by admin, technical or billing contacts in the Control Panel and services they have access to, using API calls. |- (see `/me/api/logs`)
- [List of API calls done with your account](https://api.ovh.com/console/#/me/api/logs/self~GET)
- [List of API calls done on services you have access to](https://api.ovh.com/console/#/me/api/logs/services~GET)
-[Get your audit logs](https://api.ovh.com/console/#/me/logs/audit~GET) | +| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Cassandra service as an example `/cloud/project/{serviceName}/database/cassandra/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | + +## 6.API + +| **Name** | **Capacity** | **Link** | +| --- | --- | --- | +| Control Panel and service | Manage customer accounts and services on which each account has access rights. | [https://ca.api.ovh.com/console/#/dbaas/logs](https://ca.api.ovh.com/console/#/dbaas/logs)) | + +## 7.Accounts - User + +### 7.1 Control plane + +Using your customer account on the OVHcloud Control Panel, you are able to manage your service using [three different contacts](/pages/account_and_service_management/account_information/managing_contacts).
+OVHcloud uses another account with an internal NIC to refer a customer having subscribed to several services. + +To enforce security access to your account on the Control Panel, we recommend activating a [two-factor authentication mechanism](/pages/account_and_service_management/account_information/secure-ovhcloud-account-with-2fa) or [SSO(Single Sign-On) authentication](/pages/account_and_service_management/account_information/ovhcloud-account-connect-saml-adfs). + +You can also [create your own IAM policy](/pages/account_and_service_management/account_information/iam-policy-ui) on the service, with a user interface or [via API](/pages/account_and_service_management/account_information/iam-policies-api), and manage your users and groups.
+You can troubleshoot your IAM policy configuration and analyse actions [by using API calls to get logs](/pages/manage_and_operate/iam/iam-troubleshooting). + +### 7.2 Data plane + +Once a VM is created by OVHcloud, on which the customer Analytics engines run, a TLS certificate is generated and used by the customer to access his DB. The certificate is renewed every three months. + +## 8.Features and options available at service delivery + +### 8.1 High availability + +Different plans are made available on the service: Essential, Business/Production and Enterprise/Advanced plans.
+You can choose a "Business/Production" or "Enterprise/Advanced" offer to benefit from a high availability service as your data will be replicated across multiple nodes following the chosen plan. + +### 8.2 Data encryption + +#### 8.2.1 Encryption made by the OVHcloud teams + +All network traffic on the infrastructure managing the Analytics service is encrypted. Services volumes are also encrypted with a unique key specific for each customer project.
+These operations are made, by default, by the OVHcloud operation team. + +> [!primary] +> +> Currently, OVHcloud does not offer KMS as a service, you cannot bring your own keys. KMIP is managed by OVHcloud. +> + +For a MongoDB engine : + +- **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. +The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. +We use the LUKS2 mode aes-cbc-essiv:sha256 with a 512-bit key. +- **Backups:** backups are encrypted with a randomly generated key. This key is Asymetric RSA4096. + +For all the Analytics engines such as Kafka, OpenSearch and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage: + +- **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. +The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. +We use the LUKS2 default mode aes-xts-plain64:sha256 with a 512-bit key. +- **Backups:** backups are encrypted with a randomly generated key per file. These keys are in turn encrypted with a RSA key-encryption key-pair and stored in the header section of each backup segment. +The file encryption is performed with AES-256 in CTR mode with HMAC-SHA256 for integrity protection. +The RSA key-pair is randomly generated for each service. The key lengths are 256-bit for block encryption, 512-bit for the integrity protection and 3072-bits for the RSA key. + + +#### 8.2.2 In-use encryption on client side + +> [!primary] +> +> Currently, OVHcloud does not offer a KMS as a service, you cannot bring your own keys. KMIP is managed by OVHcloud. +> + +Currently, we do not provide in-use encryption except for MongoDB Advanced plans, based on MongoDB Client-Side Field Level Encryption.
+Data is encrypted client-side with customer-controlled encryption keys, before being sent, stored, or retrieved from the service. + +### 8.3 CVE monitoring + +The OVHcloud operation team in charge of the maintenance of Public Cloud Analytics services is constantly monitoring CVE on the different DBMS available. This monitoring is done through different channels, official mailing lists, security community, internal security check...
+ +We are also in constant communication with the MongoDB team, in order to provide fast and smooth transition to the latest security version of MongoDB. + +### 8.4 vRack option + +You can activate the vRack option at the subscription step or afterwards and have your private network for your Analytics project. + +### 8.5 HDS option + +The HDS option can be activated on the service.
+This option is available only for "Business/Production" and "Enterprise/Advanced" plans for this service.
+The subscription to the Business support level is mandatory, at least to maintain necessary requirements. + +## 9.Reversibility + +You can import and export your data following recommendations provided by editors for each Analytics engine technology. + +### 9.1 Erasure of customer data + +Once you destroy your Public Cloud project (your Analytics project) in the OVHcloud Control Panel, all allocated resources are relased automtically, including used encryption keys.
+As the encryption keys are unique for each project, they will be deleted after service decommissioning. Data can not be retrieved after. + +## Go further + +[Public Cloud Analytics documentation](/products/public-cloud-data-analytics) + +Visit our dedicated Discord channel: . 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](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. diff --git a/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.fr-fr.md b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.fr-fr.md new file mode 100644 index 00000000000..aa4940ec82e --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.fr-fr.md @@ -0,0 +1,164 @@ +--- +title: Analytics Concepts - Présentation de la sécurité (EN) +excerpt: Analytics security overview +updated: 2025-11-04 +--- + +## Objective + +In addition to [the responsibility model for Analytics services](/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/), this security fact sheets aims at describing security features and functions associated to the service. It describes also best practices that customers can adopt to secure their services. + +## 1.Certifications + +- ISO/IEC 27001 +- ISO/IEC 27701 +- ISO/IEC 27017 +- ISO/IEC 27018 +- HDS +- SOC 1 type 1 +- SOC 2 type 1 +- CSA type 1 +- C5 type 1 + +## 2.Best pratices to be deployed on the service + +### 2.1 Recommandations once the service is delivered + +Once you have followed [these first steps to subscribe your service](/pages/public_cloud/data_analytics/analytics/analytics_getting_started) and reset the default password communicated to access to the service, you must filter connections by using iptables.
+You can also activate a private connection by using the vRack option. + +### 2.2 Vulnerability scans + +You are authorized to perform vulnerability scans on the service you have subscribed to. OVHcloud doesn't have to be previously informed.
+Security measures deployed by OVHcloud (especially network protection) aren't disabled, because such an audit's purpose is to demonstrate a clear vision of the security level of the customer's infrastructure.
+You are not authorized to use your service to scan other infrastructures. + +## 3.SLA + +SLA are available only for "Business/Production" and "Enterprise/Advanced" plans of this service.
+SLA for the Business/Production range in Single AZ are 99,90%.
+SLA for the Enterprise/Advanced range in Single AZ are 99,95%.
+SLA for the Production range in Multi AZ are 99,95%.
+SLA for the Advanced range in Multi AZ are 99,99%.
+The calculation method of SLA consists of the total number of minutes in the month in question deducted from the number of minutes of unavailability over the month in question. The total is divided by the total number of minutes in the month. +Service credits can be 10%, 25 % or 100% of the hourly cost per hour of unavailability of the affected Service. You can refer to the Particular Conditions of the service to get more details about the monthly available rate for each service range or plan and credits limitation. + +## 4.Backups + +### 4.1 Technical backups + +Technical backups are backups made by OVHcloud to maintain the Service Level Agreement. These backups can not be activated at customer request. + +### 4.2 Customer data backups + +Customer data (DB) is backed up, automated and operated following different frequencies. Those backups are encrypted and uploaded to a remote, replicated storage backend, in a different datacenter from the one the analytics service is hosted on. Details about frequencies, RPO and locations are listed following type of services and ranges at [this link](/pages/public_cloud/data_analytics/analytics/information_05_automated_backups).
+Customer data backup health status is checked daily by OVHcloud.
+If you need to restore your data using a backup, you can follow [this guide](/pages/public_cloud/data_analytics/analytics/analytics_restore_backup) and create a new service for this purpose. + +## 5.Logs + +| **Source** | **Content** | **Documentation** | +| --- | --- | --- | +| Control Panel | Logs of interactions made by admin, technical or billing contacts in the Control Panel and services they have access to, using API calls. |- (see `/me/api/logs`)
- [List of API calls done with your account](https://api.ovh.com/console/#/me/api/logs/self~GET)
- [List of API calls done on services you have access to](https://api.ovh.com/console/#/me/api/logs/services~GET)
-[Get your audit logs](https://api.ovh.com/console/#/me/logs/audit~GET) | +| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Cassandra service as an example `/cloud/project/{serviceName}/database/cassandra/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | + +## 6.API + +| **Name** | **Capacity** | **Link** | +| --- | --- | --- | +| Control Panel and service | Manage customer accounts and services on which each account has access rights. | [https://eu.api.ovh.com/console/#/dbaas/logs](https://eu.api.ovh.com/console/#/dbaas/logs)) | + +## 7.Accounts - User + +### 7.1 Control plane + +Using your customer account on the OVHcloud Control Panel, you are able to manage your service using [three different contacts](/pages/account_and_service_management/account_information/managing_contacts).
+OVHcloud uses another account with an internal NIC to refer a customer having subscribed to several services. + +To enforce security access to your account on the Control Panel, we recommend activating a [two-factor authentication mechanism](/pages/account_and_service_management/account_information/secure-ovhcloud-account-with-2fa) or [SSO(Single Sign-On) authentication](/pages/account_and_service_management/account_information/ovhcloud-account-connect-saml-adfs). + +You can also [create your own IAM policy](/pages/account_and_service_management/account_information/iam-policy-ui) on the service, with a user interface or [via API](/pages/account_and_service_management/account_information/iam-policies-api), and manage your users and groups.
+You can troubleshoot your IAM policy configuration and analyse actions [by using API calls to get logs](/pages/manage_and_operate/iam/iam-troubleshooting). + +### 7.2 Data plane + +Once a VM is created by OVHcloud, on which the customer Analytics engines run, a TLS certificate is generated and used by the customer to access his DB. The certificate is renewed every three months. + +## 8.Features and options available at service delivery + +### 8.1 High availability + +Different plans are made available on the service: Essential, Business/Production and Enterprise/Advanced plans.
+You can choose a "Business/Production" or "Enterprise/Advanced" offer to benefit from a high availability service as your data will be replicated across multiple nodes following the chosen plan. + +### 8.2 Data encryption + +#### 8.2.1 Encryption made by the OVHcloud teams + +All network traffic on the infrastructure managing the Analytics service is encrypted. Services volumes are also encrypted with a unique key specific for each customer project.
+These operations are made, by default, by the OVHcloud operation team. + +> [!primary] +> +> Currently, OVHcloud does not offer KMS as a service, you cannot bring your own keys. KMIP is managed by OVHcloud. +> + +For a MongoDB engine : + +- **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. +The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. +We use the LUKS2 mode aes-cbc-essiv:sha256 with a 512-bit key. +- **Backups:** backups are encrypted with a randomly generated key. This key is Asymetric RSA4096. + +For all the Analytics engines such as Kafka, OpenSearch and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage: + +- **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. +The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. +We use the LUKS2 default mode aes-xts-plain64:sha256 with a 512-bit key. +- **Backups:** backups are encrypted with a randomly generated key per file. These keys are in turn encrypted with a RSA key-encryption key-pair and stored in the header section of each backup segment. +The file encryption is performed with AES-256 in CTR mode with HMAC-SHA256 for integrity protection. +The RSA key-pair is randomly generated for each service. The key lengths are 256-bit for block encryption, 512-bit for the integrity protection and 3072-bits for the RSA key. + + +#### 8.2.2 In-use encryption on client side + +> [!primary] +> +> Currently, OVHcloud does not offer a KMS as a service, you cannot bring your own keys. KMIP is managed by OVHcloud. +> + +Currently, we do not provide in-use encryption except for MongoDB Advanced plans, based on MongoDB Client-Side Field Level Encryption.
+Data is encrypted client-side with customer-controlled encryption keys, before being sent, stored, or retrieved from the service. + +### 8.3 CVE monitoring + +The OVHcloud operation team in charge of the maintenance of Public Cloud Analytics services is constantly monitoring CVE on the different DBMS available. This monitoring is done through different channels, official mailing lists, security community, internal security check...
+ +We are also in constant communication with the MongoDB team, in order to provide fast and smooth transition to the latest security version of MongoDB. + +### 8.4 vRack option + +You can activate the vRack option at the subscription step or afterwards and have your private network for your Analytics project. + +### 8.5 HDS option + +The HDS option can be activated on the service.
+This option is available only for "Business/Production" and "Enterprise/Advanced" plans for this service.
+The subscription to the Business support level is mandatory, at least to maintain necessary requirements. + +## 9.Reversibility + +You can import and export your data following recommendations provided by editors for each Analytics engine technology. + +### 9.1 Erasure of customer data + +Once you destroy your Public Cloud project (your Analytics project) in the OVHcloud Control Panel, all allocated resources are relased automtically, including used encryption keys.
+As the encryption keys are unique for each project, they will be deleted after service decommissioning. Data can not be retrieved after. + +## Go further + +[Public Cloud Analytics documentation](/products/public-cloud-data-analytics) + +Visit our dedicated Discord channel: . 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](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. diff --git a/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.it-it.md b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.it-it.md new file mode 100644 index 00000000000..f0851db31d7 --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.it-it.md @@ -0,0 +1,164 @@ +--- +title: Analytics Concepts - Security overview +excerpt: Analytics security overview +updated: 2025-11-04 +--- + +## Objective + +In addition to [the responsibility model for Analytics services](/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/), this security fact sheets aims at describing security features and functions associated to the service. It describes also best practices that customers can adopt to secure their services. + +## 1.Certifications + +- ISO/IEC 27001 +- ISO/IEC 27701 +- ISO/IEC 27017 +- ISO/IEC 27018 +- HDS +- SOC 1 type 1 +- SOC 2 type 1 +- CSA type 1 +- C5 type 1 + +## 2.Best pratices to be deployed on the service + +### 2.1 Recommandations once the service is delivered + +Once you have followed [these first steps to subscribe your service](/pages/public_cloud/data_analytics/analytics/analytics_getting_started) and reset the default password communicated to access to the service, you must filter connections by using iptables.
+You can also activate a private connection by using the vRack option. + +### 2.2 Vulnerability scans + +You are authorized to perform vulnerability scans on the service you have subscribed to. OVHcloud doesn't have to be previously informed.
+Security measures deployed by OVHcloud (especially network protection) aren't disabled, because such an audit's purpose is to demonstrate a clear vision of the security level of the customer's infrastructure.
+You are not authorized to use your service to scan other infrastructures. + +## 3.SLA + +SLA are available only for "Business/Production" and "Enterprise/Advanced" plans of this service.
+SLA for the Business/Production range in Single AZ are 99,90%.
+SLA for the Enterprise/Advanced range in Single AZ are 99,95%.
+SLA for the Production range in Multi AZ are 99,95%.
+SLA for the Advanced range in Multi AZ are 99,99%.
+The calculation method of SLA consists of the total number of minutes in the month in question deducted from the number of minutes of unavailability over the month in question. The total is divided by the total number of minutes in the month. +Service credits can be 10%, 25 % or 100% of the hourly cost per hour of unavailability of the affected Service. You can refer to the Particular Conditions of the service to get more details about the monthly available rate for each service range or plan and credits limitation. + +## 4.Backups + +### 4.1 Technical backups + +Technical backups are backups made by OVHcloud to maintain the Service Level Agreement. These backups can not be activated at customer request. + +### 4.2 Customer data backups + +Customer data (DB) is backed up, automated and operated following different frequencies. Those backups are encrypted and uploaded to a remote, replicated storage backend, in a different datacenter from the one the analytics service is hosted on. Details about frequencies, RPO and locations are listed following type of services and ranges at [this link](/pages/public_cloud/data_analytics/analytics/information_05_automated_backups).
+Customer data backup health status is checked daily by OVHcloud.
+If you need to restore your data using a backup, you can follow [this guide](/pages/public_cloud/data_analytics/analytics/analytics_restore_backup) and create a new service for this purpose. + +## 5.Logs + +| **Source** | **Content** | **Documentation** | +| --- | --- | --- | +| Control Panel | Logs of interactions made by admin, technical or billing contacts in the Control Panel and services they have access to, using API calls. |- (see `/me/api/logs`)
- [List of API calls done with your account](https://api.ovh.com/console/#/me/api/logs/self~GET)
- [List of API calls done on services you have access to](https://api.ovh.com/console/#/me/api/logs/services~GET)
-[Get your audit logs](https://api.ovh.com/console/#/me/logs/audit~GET) | +| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Cassandra service as an example `/cloud/project/{serviceName}/database/cassandra/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | + +## 6.API + +| **Name** | **Capacity** | **Link** | +| --- | --- | --- | +| Control Panel and service | Manage customer accounts and services on which each account has access rights. | [https://eu.api.ovh.com/console/#/dbaas/logs](https://eu.api.ovh.com/console/#/dbaas/logs)) | + +## 7.Accounts - User + +### 7.1 Control plane + +Using your customer account on the OVHcloud Control Panel, you are able to manage your service using [three different contacts](/pages/account_and_service_management/account_information/managing_contacts).
+OVHcloud uses another account with an internal NIC to refer a customer having subscribed to several services. + +To enforce security access to your account on the Control Panel, we recommend activating a [two-factor authentication mechanism](/pages/account_and_service_management/account_information/secure-ovhcloud-account-with-2fa) or [SSO(Single Sign-On) authentication](/pages/account_and_service_management/account_information/ovhcloud-account-connect-saml-adfs). + +You can also [create your own IAM policy](/pages/account_and_service_management/account_information/iam-policy-ui) on the service, with a user interface or [via API](/pages/account_and_service_management/account_information/iam-policies-api), and manage your users and groups.
+You can troubleshoot your IAM policy configuration and analyse actions [by using API calls to get logs](/pages/manage_and_operate/iam/iam-troubleshooting). + +### 7.2 Data plane + +Once a VM is created by OVHcloud, on which the customer Analytics engines run, a TLS certificate is generated and used by the customer to access his DB. The certificate is renewed every three months. + +## 8.Features and options available at service delivery + +### 8.1 High availability + +Different plans are made available on the service: Essential, Business/Production and Enterprise/Advanced plans.
+You can choose a "Business/Production" or "Enterprise/Advanced" offer to benefit from a high availability service as your data will be replicated across multiple nodes following the chosen plan. + +### 8.2 Data encryption + +#### 8.2.1 Encryption made by the OVHcloud teams + +All network traffic on the infrastructure managing the Analytics service is encrypted. Services volumes are also encrypted with a unique key specific for each customer project.
+These operations are made, by default, by the OVHcloud operation team. + +> [!primary] +> +> Currently, OVHcloud does not offer KMS as a service, you cannot bring your own keys. KMIP is managed by OVHcloud. +> + +For a MongoDB engine : + +- **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. +The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. +We use the LUKS2 mode aes-cbc-essiv:sha256 with a 512-bit key. +- **Backups:** backups are encrypted with a randomly generated key. This key is Asymetric RSA4096. + +For all the Analytics engines such as Kafka, OpenSearch and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage: + +- **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. +The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. +We use the LUKS2 default mode aes-xts-plain64:sha256 with a 512-bit key. +- **Backups:** backups are encrypted with a randomly generated key per file. These keys are in turn encrypted with a RSA key-encryption key-pair and stored in the header section of each backup segment. +The file encryption is performed with AES-256 in CTR mode with HMAC-SHA256 for integrity protection. +The RSA key-pair is randomly generated for each service. The key lengths are 256-bit for block encryption, 512-bit for the integrity protection and 3072-bits for the RSA key. + + +#### 8.2.2 In-use encryption on client side + +> [!primary] +> +> Currently, OVHcloud does not offer a KMS as a service, you cannot bring your own keys. KMIP is managed by OVHcloud. +> + +Currently, we do not provide in-use encryption except for MongoDB Advanced plans, based on MongoDB Client-Side Field Level Encryption.
+Data is encrypted client-side with customer-controlled encryption keys, before being sent, stored, or retrieved from the service. + +### 8.3 CVE monitoring + +The OVHcloud operation team in charge of the maintenance of Public Cloud Analytics services is constantly monitoring CVE on the different DBMS available. This monitoring is done through different channels, official mailing lists, security community, internal security check...
+ +We are also in constant communication with the MongoDB team, in order to provide fast and smooth transition to the latest security version of MongoDB. + +### 8.4 vRack option + +You can activate the vRack option at the subscription step or afterwards and have your private network for your Analytics project. + +### 8.5 HDS option + +The HDS option can be activated on the service.
+This option is available only for "Business/Production" and "Enterprise/Advanced" plans for this service.
+The subscription to the Business support level is mandatory, at least to maintain necessary requirements. + +## 9.Reversibility + +You can import and export your data following recommendations provided by editors for each Analytics engine technology. + +### 9.1 Erasure of customer data + +Once you destroy your Public Cloud project (your Analytics project) in the OVHcloud Control Panel, all allocated resources are relased automtically, including used encryption keys.
+As the encryption keys are unique for each project, they will be deleted after service decommissioning. Data can not be retrieved after. + +## Go further + +[Public Cloud Analytics documentation](/products/public-cloud-data-analytics) + +Visit our dedicated Discord channel: . 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](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. diff --git a/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.pl-pl.md b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.pl-pl.md new file mode 100644 index 00000000000..f0851db31d7 --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.pl-pl.md @@ -0,0 +1,164 @@ +--- +title: Analytics Concepts - Security overview +excerpt: Analytics security overview +updated: 2025-11-04 +--- + +## Objective + +In addition to [the responsibility model for Analytics services](/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/), this security fact sheets aims at describing security features and functions associated to the service. It describes also best practices that customers can adopt to secure their services. + +## 1.Certifications + +- ISO/IEC 27001 +- ISO/IEC 27701 +- ISO/IEC 27017 +- ISO/IEC 27018 +- HDS +- SOC 1 type 1 +- SOC 2 type 1 +- CSA type 1 +- C5 type 1 + +## 2.Best pratices to be deployed on the service + +### 2.1 Recommandations once the service is delivered + +Once you have followed [these first steps to subscribe your service](/pages/public_cloud/data_analytics/analytics/analytics_getting_started) and reset the default password communicated to access to the service, you must filter connections by using iptables.
+You can also activate a private connection by using the vRack option. + +### 2.2 Vulnerability scans + +You are authorized to perform vulnerability scans on the service you have subscribed to. OVHcloud doesn't have to be previously informed.
+Security measures deployed by OVHcloud (especially network protection) aren't disabled, because such an audit's purpose is to demonstrate a clear vision of the security level of the customer's infrastructure.
+You are not authorized to use your service to scan other infrastructures. + +## 3.SLA + +SLA are available only for "Business/Production" and "Enterprise/Advanced" plans of this service.
+SLA for the Business/Production range in Single AZ are 99,90%.
+SLA for the Enterprise/Advanced range in Single AZ are 99,95%.
+SLA for the Production range in Multi AZ are 99,95%.
+SLA for the Advanced range in Multi AZ are 99,99%.
+The calculation method of SLA consists of the total number of minutes in the month in question deducted from the number of minutes of unavailability over the month in question. The total is divided by the total number of minutes in the month. +Service credits can be 10%, 25 % or 100% of the hourly cost per hour of unavailability of the affected Service. You can refer to the Particular Conditions of the service to get more details about the monthly available rate for each service range or plan and credits limitation. + +## 4.Backups + +### 4.1 Technical backups + +Technical backups are backups made by OVHcloud to maintain the Service Level Agreement. These backups can not be activated at customer request. + +### 4.2 Customer data backups + +Customer data (DB) is backed up, automated and operated following different frequencies. Those backups are encrypted and uploaded to a remote, replicated storage backend, in a different datacenter from the one the analytics service is hosted on. Details about frequencies, RPO and locations are listed following type of services and ranges at [this link](/pages/public_cloud/data_analytics/analytics/information_05_automated_backups).
+Customer data backup health status is checked daily by OVHcloud.
+If you need to restore your data using a backup, you can follow [this guide](/pages/public_cloud/data_analytics/analytics/analytics_restore_backup) and create a new service for this purpose. + +## 5.Logs + +| **Source** | **Content** | **Documentation** | +| --- | --- | --- | +| Control Panel | Logs of interactions made by admin, technical or billing contacts in the Control Panel and services they have access to, using API calls. |- (see `/me/api/logs`)
- [List of API calls done with your account](https://api.ovh.com/console/#/me/api/logs/self~GET)
- [List of API calls done on services you have access to](https://api.ovh.com/console/#/me/api/logs/services~GET)
-[Get your audit logs](https://api.ovh.com/console/#/me/logs/audit~GET) | +| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Cassandra service as an example `/cloud/project/{serviceName}/database/cassandra/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | + +## 6.API + +| **Name** | **Capacity** | **Link** | +| --- | --- | --- | +| Control Panel and service | Manage customer accounts and services on which each account has access rights. | [https://eu.api.ovh.com/console/#/dbaas/logs](https://eu.api.ovh.com/console/#/dbaas/logs)) | + +## 7.Accounts - User + +### 7.1 Control plane + +Using your customer account on the OVHcloud Control Panel, you are able to manage your service using [three different contacts](/pages/account_and_service_management/account_information/managing_contacts).
+OVHcloud uses another account with an internal NIC to refer a customer having subscribed to several services. + +To enforce security access to your account on the Control Panel, we recommend activating a [two-factor authentication mechanism](/pages/account_and_service_management/account_information/secure-ovhcloud-account-with-2fa) or [SSO(Single Sign-On) authentication](/pages/account_and_service_management/account_information/ovhcloud-account-connect-saml-adfs). + +You can also [create your own IAM policy](/pages/account_and_service_management/account_information/iam-policy-ui) on the service, with a user interface or [via API](/pages/account_and_service_management/account_information/iam-policies-api), and manage your users and groups.
+You can troubleshoot your IAM policy configuration and analyse actions [by using API calls to get logs](/pages/manage_and_operate/iam/iam-troubleshooting). + +### 7.2 Data plane + +Once a VM is created by OVHcloud, on which the customer Analytics engines run, a TLS certificate is generated and used by the customer to access his DB. The certificate is renewed every three months. + +## 8.Features and options available at service delivery + +### 8.1 High availability + +Different plans are made available on the service: Essential, Business/Production and Enterprise/Advanced plans.
+You can choose a "Business/Production" or "Enterprise/Advanced" offer to benefit from a high availability service as your data will be replicated across multiple nodes following the chosen plan. + +### 8.2 Data encryption + +#### 8.2.1 Encryption made by the OVHcloud teams + +All network traffic on the infrastructure managing the Analytics service is encrypted. Services volumes are also encrypted with a unique key specific for each customer project.
+These operations are made, by default, by the OVHcloud operation team. + +> [!primary] +> +> Currently, OVHcloud does not offer KMS as a service, you cannot bring your own keys. KMIP is managed by OVHcloud. +> + +For a MongoDB engine : + +- **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. +The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. +We use the LUKS2 mode aes-cbc-essiv:sha256 with a 512-bit key. +- **Backups:** backups are encrypted with a randomly generated key. This key is Asymetric RSA4096. + +For all the Analytics engines such as Kafka, OpenSearch and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage: + +- **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. +The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. +We use the LUKS2 default mode aes-xts-plain64:sha256 with a 512-bit key. +- **Backups:** backups are encrypted with a randomly generated key per file. These keys are in turn encrypted with a RSA key-encryption key-pair and stored in the header section of each backup segment. +The file encryption is performed with AES-256 in CTR mode with HMAC-SHA256 for integrity protection. +The RSA key-pair is randomly generated for each service. The key lengths are 256-bit for block encryption, 512-bit for the integrity protection and 3072-bits for the RSA key. + + +#### 8.2.2 In-use encryption on client side + +> [!primary] +> +> Currently, OVHcloud does not offer a KMS as a service, you cannot bring your own keys. KMIP is managed by OVHcloud. +> + +Currently, we do not provide in-use encryption except for MongoDB Advanced plans, based on MongoDB Client-Side Field Level Encryption.
+Data is encrypted client-side with customer-controlled encryption keys, before being sent, stored, or retrieved from the service. + +### 8.3 CVE monitoring + +The OVHcloud operation team in charge of the maintenance of Public Cloud Analytics services is constantly monitoring CVE on the different DBMS available. This monitoring is done through different channels, official mailing lists, security community, internal security check...
+ +We are also in constant communication with the MongoDB team, in order to provide fast and smooth transition to the latest security version of MongoDB. + +### 8.4 vRack option + +You can activate the vRack option at the subscription step or afterwards and have your private network for your Analytics project. + +### 8.5 HDS option + +The HDS option can be activated on the service.
+This option is available only for "Business/Production" and "Enterprise/Advanced" plans for this service.
+The subscription to the Business support level is mandatory, at least to maintain necessary requirements. + +## 9.Reversibility + +You can import and export your data following recommendations provided by editors for each Analytics engine technology. + +### 9.1 Erasure of customer data + +Once you destroy your Public Cloud project (your Analytics project) in the OVHcloud Control Panel, all allocated resources are relased automtically, including used encryption keys.
+As the encryption keys are unique for each project, they will be deleted after service decommissioning. Data can not be retrieved after. + +## Go further + +[Public Cloud Analytics documentation](/products/public-cloud-data-analytics) + +Visit our dedicated Discord channel: . 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](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. diff --git a/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.pt-pt.md b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.pt-pt.md new file mode 100644 index 00000000000..f0851db31d7 --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/guide.pt-pt.md @@ -0,0 +1,164 @@ +--- +title: Analytics Concepts - Security overview +excerpt: Analytics security overview +updated: 2025-11-04 +--- + +## Objective + +In addition to [the responsibility model for Analytics services](/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/), this security fact sheets aims at describing security features and functions associated to the service. It describes also best practices that customers can adopt to secure their services. + +## 1.Certifications + +- ISO/IEC 27001 +- ISO/IEC 27701 +- ISO/IEC 27017 +- ISO/IEC 27018 +- HDS +- SOC 1 type 1 +- SOC 2 type 1 +- CSA type 1 +- C5 type 1 + +## 2.Best pratices to be deployed on the service + +### 2.1 Recommandations once the service is delivered + +Once you have followed [these first steps to subscribe your service](/pages/public_cloud/data_analytics/analytics/analytics_getting_started) and reset the default password communicated to access to the service, you must filter connections by using iptables.
+You can also activate a private connection by using the vRack option. + +### 2.2 Vulnerability scans + +You are authorized to perform vulnerability scans on the service you have subscribed to. OVHcloud doesn't have to be previously informed.
+Security measures deployed by OVHcloud (especially network protection) aren't disabled, because such an audit's purpose is to demonstrate a clear vision of the security level of the customer's infrastructure.
+You are not authorized to use your service to scan other infrastructures. + +## 3.SLA + +SLA are available only for "Business/Production" and "Enterprise/Advanced" plans of this service.
+SLA for the Business/Production range in Single AZ are 99,90%.
+SLA for the Enterprise/Advanced range in Single AZ are 99,95%.
+SLA for the Production range in Multi AZ are 99,95%.
+SLA for the Advanced range in Multi AZ are 99,99%.
+The calculation method of SLA consists of the total number of minutes in the month in question deducted from the number of minutes of unavailability over the month in question. The total is divided by the total number of minutes in the month. +Service credits can be 10%, 25 % or 100% of the hourly cost per hour of unavailability of the affected Service. You can refer to the Particular Conditions of the service to get more details about the monthly available rate for each service range or plan and credits limitation. + +## 4.Backups + +### 4.1 Technical backups + +Technical backups are backups made by OVHcloud to maintain the Service Level Agreement. These backups can not be activated at customer request. + +### 4.2 Customer data backups + +Customer data (DB) is backed up, automated and operated following different frequencies. Those backups are encrypted and uploaded to a remote, replicated storage backend, in a different datacenter from the one the analytics service is hosted on. Details about frequencies, RPO and locations are listed following type of services and ranges at [this link](/pages/public_cloud/data_analytics/analytics/information_05_automated_backups).
+Customer data backup health status is checked daily by OVHcloud.
+If you need to restore your data using a backup, you can follow [this guide](/pages/public_cloud/data_analytics/analytics/analytics_restore_backup) and create a new service for this purpose. + +## 5.Logs + +| **Source** | **Content** | **Documentation** | +| --- | --- | --- | +| Control Panel | Logs of interactions made by admin, technical or billing contacts in the Control Panel and services they have access to, using API calls. |- (see `/me/api/logs`)
- [List of API calls done with your account](https://api.ovh.com/console/#/me/api/logs/self~GET)
- [List of API calls done on services you have access to](https://api.ovh.com/console/#/me/api/logs/services~GET)
-[Get your audit logs](https://api.ovh.com/console/#/me/logs/audit~GET) | +| Service | 1000 last logs for service usage | See Sheet 'log' in the Control Panel
- or via API (for Cassandra service as an example `/cloud/project/{serviceName}/database/cassandra/{clusterId}/logs`
- `/cloud/project/{serviceName}/database/{serviceType}/{clusterId}/logs` | + +## 6.API + +| **Name** | **Capacity** | **Link** | +| --- | --- | --- | +| Control Panel and service | Manage customer accounts and services on which each account has access rights. | [https://eu.api.ovh.com/console/#/dbaas/logs](https://eu.api.ovh.com/console/#/dbaas/logs)) | + +## 7.Accounts - User + +### 7.1 Control plane + +Using your customer account on the OVHcloud Control Panel, you are able to manage your service using [three different contacts](/pages/account_and_service_management/account_information/managing_contacts).
+OVHcloud uses another account with an internal NIC to refer a customer having subscribed to several services. + +To enforce security access to your account on the Control Panel, we recommend activating a [two-factor authentication mechanism](/pages/account_and_service_management/account_information/secure-ovhcloud-account-with-2fa) or [SSO(Single Sign-On) authentication](/pages/account_and_service_management/account_information/ovhcloud-account-connect-saml-adfs). + +You can also [create your own IAM policy](/pages/account_and_service_management/account_information/iam-policy-ui) on the service, with a user interface or [via API](/pages/account_and_service_management/account_information/iam-policies-api), and manage your users and groups.
+You can troubleshoot your IAM policy configuration and analyse actions [by using API calls to get logs](/pages/manage_and_operate/iam/iam-troubleshooting). + +### 7.2 Data plane + +Once a VM is created by OVHcloud, on which the customer Analytics engines run, a TLS certificate is generated and used by the customer to access his DB. The certificate is renewed every three months. + +## 8.Features and options available at service delivery + +### 8.1 High availability + +Different plans are made available on the service: Essential, Business/Production and Enterprise/Advanced plans.
+You can choose a "Business/Production" or "Enterprise/Advanced" offer to benefit from a high availability service as your data will be replicated across multiple nodes following the chosen plan. + +### 8.2 Data encryption + +#### 8.2.1 Encryption made by the OVHcloud teams + +All network traffic on the infrastructure managing the Analytics service is encrypted. Services volumes are also encrypted with a unique key specific for each customer project.
+These operations are made, by default, by the OVHcloud operation team. + +> [!primary] +> +> Currently, OVHcloud does not offer KMS as a service, you cannot bring your own keys. KMIP is managed by OVHcloud. +> + +For a MongoDB engine : + +- **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. +The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. +We use the LUKS2 mode aes-cbc-essiv:sha256 with a 512-bit key. +- **Backups:** backups are encrypted with a randomly generated key. This key is Asymetric RSA4096. + +For all the Analytics engines such as Kafka, OpenSearch and so on, at-rest data encryption covers both active service instances as well as service backups in cloud object storage: + +- **Nodes:** service instances and the underlying VMs use full volume encryption using [LUKS](https://en.wikipedia.org/wiki/Linux_Unified_Key_Setup) with a randomly generated ephemeral key for each instance and each volume. +The key is never re-used and will be trashed at the destruction of the instance, so there’s a natural key rotation with roll-forward upgrades. +We use the LUKS2 default mode aes-xts-plain64:sha256 with a 512-bit key. +- **Backups:** backups are encrypted with a randomly generated key per file. These keys are in turn encrypted with a RSA key-encryption key-pair and stored in the header section of each backup segment. +The file encryption is performed with AES-256 in CTR mode with HMAC-SHA256 for integrity protection. +The RSA key-pair is randomly generated for each service. The key lengths are 256-bit for block encryption, 512-bit for the integrity protection and 3072-bits for the RSA key. + + +#### 8.2.2 In-use encryption on client side + +> [!primary] +> +> Currently, OVHcloud does not offer a KMS as a service, you cannot bring your own keys. KMIP is managed by OVHcloud. +> + +Currently, we do not provide in-use encryption except for MongoDB Advanced plans, based on MongoDB Client-Side Field Level Encryption.
+Data is encrypted client-side with customer-controlled encryption keys, before being sent, stored, or retrieved from the service. + +### 8.3 CVE monitoring + +The OVHcloud operation team in charge of the maintenance of Public Cloud Analytics services is constantly monitoring CVE on the different DBMS available. This monitoring is done through different channels, official mailing lists, security community, internal security check...
+ +We are also in constant communication with the MongoDB team, in order to provide fast and smooth transition to the latest security version of MongoDB. + +### 8.4 vRack option + +You can activate the vRack option at the subscription step or afterwards and have your private network for your Analytics project. + +### 8.5 HDS option + +The HDS option can be activated on the service.
+This option is available only for "Business/Production" and "Enterprise/Advanced" plans for this service.
+The subscription to the Business support level is mandatory, at least to maintain necessary requirements. + +## 9.Reversibility + +You can import and export your data following recommendations provided by editors for each Analytics engine technology. + +### 9.1 Erasure of customer data + +Once you destroy your Public Cloud project (your Analytics project) in the OVHcloud Control Panel, all allocated resources are relased automtically, including used encryption keys.
+As the encryption keys are unique for each project, they will be deleted after service decommissioning. Data can not be retrieved after. + +## Go further + +[Public Cloud Analytics documentation](/products/public-cloud-data-analytics) + +Visit our dedicated Discord channel: . 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](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project. diff --git a/pages/public_cloud/data_analytics/analytics/information_01_security_overview/images/certificate_badge_hds.png b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/images/certificate_badge_hds.png new file mode 100644 index 00000000000..a0f4341f4e1 Binary files /dev/null and b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/images/certificate_badge_hds.png differ diff --git a/pages/public_cloud/data_analytics/analytics/information_01_security_overview/images/certificate_badge_iso.png b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/images/certificate_badge_iso.png new file mode 100644 index 00000000000..4fe0922ecb9 Binary files /dev/null and b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/images/certificate_badge_iso.png differ diff --git a/pages/public_cloud/data_analytics/analytics/information_01_security_overview/images/compliance_badge_gdpr.png b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/images/compliance_badge_gdpr.png new file mode 100644 index 00000000000..4e5d74e674e Binary files /dev/null and b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/images/compliance_badge_gdpr.png differ diff --git a/pages/public_cloud/data_analytics/analytics/information_01_security_overview/meta.yaml b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/meta.yaml new file mode 100644 index 00000000000..078ade5eb83 --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/information_01_security_overview/meta.yaml @@ -0,0 +1,5 @@ +id: 70d55a51-052c-4d85-8d53-1a9821754dfd +full_slug: public-cloud-data-analytics-concepts-security-overview +engine: all +section: dashboard +reference_category: public-cloud-data-analytics-common-security \ No newline at end of file diff --git a/pages/public_cloud/data_analytics/analytics/information_02_lifecycle_policy/meta.yaml b/pages/public_cloud/data_analytics/analytics/information_02_lifecycle_policy/meta.yaml index 2dbd5929454..4e4d4826c86 100644 --- a/pages/public_cloud/data_analytics/analytics/information_02_lifecycle_policy/meta.yaml +++ b/pages/public_cloud/data_analytics/analytics/information_02_lifecycle_policy/meta.yaml @@ -1,4 +1,4 @@ id: d30e89c8-23c7-4f8c-a61e-870a2638fe1a full_slug: data-analytics-lifecycle-policy engine: all -reference_category: data-analytics-general-information \ No newline at end of file +reference_category: public-cloud-data-analytics-common-key-concepts \ No newline at end of file diff --git a/pages/public_cloud/data_analytics/analytics/information_03_capabilities/meta.yaml b/pages/public_cloud/data_analytics/analytics/information_03_capabilities/meta.yaml index 3c7a3bd0eb6..d5ce51f57a7 100644 --- a/pages/public_cloud/data_analytics/analytics/information_03_capabilities/meta.yaml +++ b/pages/public_cloud/data_analytics/analytics/information_03_capabilities/meta.yaml @@ -1,3 +1,3 @@ id: dacbea7b-34b7-4f03-91b5-ad078bdbbbe7 full_slug: data-analytics-capabilities -reference_category: data-analytics-general-information \ No newline at end of file +reference_category: public-cloud-data-analytics-common-key-concepts \ No newline at end of file diff --git a/pages/public_cloud/data_analytics/analytics/information_04_maintenances/meta.yaml b/pages/public_cloud/data_analytics/analytics/information_04_maintenances/meta.yaml index b6ceae6f707..170065c6422 100644 --- a/pages/public_cloud/data_analytics/analytics/information_04_maintenances/meta.yaml +++ b/pages/public_cloud/data_analytics/analytics/information_04_maintenances/meta.yaml @@ -1,3 +1,3 @@ id: 60beaf94-4d8d-4fd6-80a4-f70ed5e2265d full_slug: data-analytics-maintenance -reference_category: data-analytics-general-information \ No newline at end of file +reference_category: public-cloud-data-analytics-common-key-concepts \ No newline at end of file diff --git a/pages/public_cloud/data_analytics/analytics/information_05_automated_backups/meta.yaml b/pages/public_cloud/data_analytics/analytics/information_05_automated_backups/meta.yaml index f19d0939e21..8ed5b9e22f8 100644 --- a/pages/public_cloud/data_analytics/analytics/information_05_automated_backups/meta.yaml +++ b/pages/public_cloud/data_analytics/analytics/information_05_automated_backups/meta.yaml @@ -1,3 +1,3 @@ id: e03163b1-a72a-4685-af33-88ede057329d full_slug: data-analytics-backups -reference_category: data-analytics-general-information \ No newline at end of file +reference_category: public-cloud-data-analytics-common-key-concepts \ No newline at end of file diff --git a/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.de-de.md b/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.de-de.md new file mode 100644 index 00000000000..244043a6a81 --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.de-de.md @@ -0,0 +1,164 @@ +--- +title: Analytics - Responsibility model +excerpt: 'Shared responsibilities between OVHcloud and the customer' +updated: 2025-11-04 +--- + +Public Cloud Analytics allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions. + +The RACI below details shared responsibilities between OVHcloud and the customer for Public Cloud Analytics services. +This shared model can help relieve the customer’s operational burden. + +## RACI definition + +| Roles | +| --- | +| R: Is in charge of carrying out the process | +| A: Guarantees the successful completion of the process | +| 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 Analytics service such as a Kafka or OpenSearch cluster. + +### 1. Before subscription + +#### 1.1. Specify service as needed + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Learn about the capabilities and limitations of the Services detailed in the OVHcloud documentation | RA | I | +| Choose service location | RA | I | +| Size services as needed | RA | I | +| Choose options as needed | RA | I | + +### 2. Service availability + +#### 2.1. Install service + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Produce, route, deliver and maintain physical machines, virtual machines and hosting buildings | | RA | +| Buy and hold licences and usage rights for software provided by OVHcloud | | RA | +| Buy and hold licences and usage rights for backup solutions provided by OVHcloud | | RA | + +#### 2.2. Reversibility model + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Offer standard solutions and protocols for importing and exporting data | I | RA | + +### 3. Service usage + +#### 3.1. Operations + +##### **3.1.1. Daily operations** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Use all virtual machines (nodes) deployed in the IaaS | | RA | +| Decide to add/delete resources to the existing service | RA | I | +| Add/delete resources to the existing service | I | RA | + +##### **3.1.2. Access management** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage access and security policy for Service users | RA | I | +| Managing OVHcloud teams’ physical access to infrastructures | | RA | +| Managing OVHcloud teams’ logical access to infrastructures | I | RA | +| Managing access to the OVHcloud Control Panel | RA | I | +| Manage access to management interfaces specific to the Service (command line, API, etc.) | RA | I | + +##### **3.1.3. Monitoring** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Monitor the proper functioning of physical devices (utilities) in support of the Platform as a Service | | RA | +| Monitor the proper functioning of virtual devices (utilities) in support of Platform as a Service | I | RA | +| Monitor physical and virtual resource performance | I | RA | +| Monitor service performance | RA | I | +| Process and pay for alarms from managed devices in the Public Cloud Analytics infrastructure | I | RA | +| Maintain logs generated by Public Cloud Analytics services | RA | RA | +| Keep logs of the Service hosted on Public Cloud Analytics | RA | + +##### **3.1.4. Storage** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Managing content hosted on Public Cloud Analytics services | RA | I | +| Ensuring data continuity and sustainability | RA | | +| Perform storage and backup device maintenance | | RA | +| Create, modify, control, restore, delete internal backup jobs | I | RA | + +##### **3.1.5. Connectivity** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Operate automatic network management systems (architecture, implementation, software and hardware maintenance for deployed public and private networks) | I | RA | +| Manage IP addressing plan | RA | | + +##### **3.1.6. Management** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Ensuring the security of management infrastructures (API, Control Panel) | I | RA | +| Ensure the security of the operating systems and software installed on the services | I | RA | +| Managing the physical security of equipment and infrastructures hosted at OVHcloud | I | RA | +| Maintain Public Cloud Analytics services and their extensions | C | RA | + +##### **3.1.7. Business continuity** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage automatic management systems for the infrastructure provided | I | RA | +| Maintain a business continuity and disaster recovery plan for hosted services | RA | I | + +#### 3.2. Event management + +##### **3.2.1. Incidents** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Intervening with Public Cloud Analytics managed elements | | RA | + +##### **3.2.2. Changes** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Comply with the Public Cloud Enterprise Lifecycle Policy | RA | | +| Deploy patches, update software and information systems hosted in Public Cloud Analytics | CI | RA | +| Confirm the customer's request to change the hardware or software for the Analytics service | A | R | +| Deploy patches, update and configure the information system using Public Cloud Analytics | RA | | +| Perform preventive interventions on managed elements of the Public Cloud Analytics | I | AR | + +### 4. Reverting + +#### 4.1. Reversibility model + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Schedule reversibility operations | RA | I | +| Choose fallback infrastructures | RA | + +#### 4.2. Data recovery + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage reversibility operations | RA | I | +| Migrate/transfer data | RA | + +### 5. End of service + +#### 5.1. Destroying configurations + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Delete Public Cloud project services | RA | I | + +## Go further + +Visit our dedicated Discord channel: . 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](/links/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 . diff --git a/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.en-asia.md b/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.en-asia.md new file mode 100644 index 00000000000..244043a6a81 --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.en-asia.md @@ -0,0 +1,164 @@ +--- +title: Analytics - Responsibility model +excerpt: 'Shared responsibilities between OVHcloud and the customer' +updated: 2025-11-04 +--- + +Public Cloud Analytics allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions. + +The RACI below details shared responsibilities between OVHcloud and the customer for Public Cloud Analytics services. +This shared model can help relieve the customer’s operational burden. + +## RACI definition + +| Roles | +| --- | +| R: Is in charge of carrying out the process | +| A: Guarantees the successful completion of the process | +| 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 Analytics service such as a Kafka or OpenSearch cluster. + +### 1. Before subscription + +#### 1.1. Specify service as needed + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Learn about the capabilities and limitations of the Services detailed in the OVHcloud documentation | RA | I | +| Choose service location | RA | I | +| Size services as needed | RA | I | +| Choose options as needed | RA | I | + +### 2. Service availability + +#### 2.1. Install service + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Produce, route, deliver and maintain physical machines, virtual machines and hosting buildings | | RA | +| Buy and hold licences and usage rights for software provided by OVHcloud | | RA | +| Buy and hold licences and usage rights for backup solutions provided by OVHcloud | | RA | + +#### 2.2. Reversibility model + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Offer standard solutions and protocols for importing and exporting data | I | RA | + +### 3. Service usage + +#### 3.1. Operations + +##### **3.1.1. Daily operations** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Use all virtual machines (nodes) deployed in the IaaS | | RA | +| Decide to add/delete resources to the existing service | RA | I | +| Add/delete resources to the existing service | I | RA | + +##### **3.1.2. Access management** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage access and security policy for Service users | RA | I | +| Managing OVHcloud teams’ physical access to infrastructures | | RA | +| Managing OVHcloud teams’ logical access to infrastructures | I | RA | +| Managing access to the OVHcloud Control Panel | RA | I | +| Manage access to management interfaces specific to the Service (command line, API, etc.) | RA | I | + +##### **3.1.3. Monitoring** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Monitor the proper functioning of physical devices (utilities) in support of the Platform as a Service | | RA | +| Monitor the proper functioning of virtual devices (utilities) in support of Platform as a Service | I | RA | +| Monitor physical and virtual resource performance | I | RA | +| Monitor service performance | RA | I | +| Process and pay for alarms from managed devices in the Public Cloud Analytics infrastructure | I | RA | +| Maintain logs generated by Public Cloud Analytics services | RA | RA | +| Keep logs of the Service hosted on Public Cloud Analytics | RA | + +##### **3.1.4. Storage** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Managing content hosted on Public Cloud Analytics services | RA | I | +| Ensuring data continuity and sustainability | RA | | +| Perform storage and backup device maintenance | | RA | +| Create, modify, control, restore, delete internal backup jobs | I | RA | + +##### **3.1.5. Connectivity** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Operate automatic network management systems (architecture, implementation, software and hardware maintenance for deployed public and private networks) | I | RA | +| Manage IP addressing plan | RA | | + +##### **3.1.6. Management** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Ensuring the security of management infrastructures (API, Control Panel) | I | RA | +| Ensure the security of the operating systems and software installed on the services | I | RA | +| Managing the physical security of equipment and infrastructures hosted at OVHcloud | I | RA | +| Maintain Public Cloud Analytics services and their extensions | C | RA | + +##### **3.1.7. Business continuity** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage automatic management systems for the infrastructure provided | I | RA | +| Maintain a business continuity and disaster recovery plan for hosted services | RA | I | + +#### 3.2. Event management + +##### **3.2.1. Incidents** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Intervening with Public Cloud Analytics managed elements | | RA | + +##### **3.2.2. Changes** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Comply with the Public Cloud Enterprise Lifecycle Policy | RA | | +| Deploy patches, update software and information systems hosted in Public Cloud Analytics | CI | RA | +| Confirm the customer's request to change the hardware or software for the Analytics service | A | R | +| Deploy patches, update and configure the information system using Public Cloud Analytics | RA | | +| Perform preventive interventions on managed elements of the Public Cloud Analytics | I | AR | + +### 4. Reverting + +#### 4.1. Reversibility model + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Schedule reversibility operations | RA | I | +| Choose fallback infrastructures | RA | + +#### 4.2. Data recovery + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage reversibility operations | RA | I | +| Migrate/transfer data | RA | + +### 5. End of service + +#### 5.1. Destroying configurations + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Delete Public Cloud project services | RA | I | + +## Go further + +Visit our dedicated Discord channel: . 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](/links/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 . diff --git a/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.en-au.md b/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.en-au.md new file mode 100644 index 00000000000..244043a6a81 --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.en-au.md @@ -0,0 +1,164 @@ +--- +title: Analytics - Responsibility model +excerpt: 'Shared responsibilities between OVHcloud and the customer' +updated: 2025-11-04 +--- + +Public Cloud Analytics allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions. + +The RACI below details shared responsibilities between OVHcloud and the customer for Public Cloud Analytics services. +This shared model can help relieve the customer’s operational burden. + +## RACI definition + +| Roles | +| --- | +| R: Is in charge of carrying out the process | +| A: Guarantees the successful completion of the process | +| 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 Analytics service such as a Kafka or OpenSearch cluster. + +### 1. Before subscription + +#### 1.1. Specify service as needed + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Learn about the capabilities and limitations of the Services detailed in the OVHcloud documentation | RA | I | +| Choose service location | RA | I | +| Size services as needed | RA | I | +| Choose options as needed | RA | I | + +### 2. Service availability + +#### 2.1. Install service + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Produce, route, deliver and maintain physical machines, virtual machines and hosting buildings | | RA | +| Buy and hold licences and usage rights for software provided by OVHcloud | | RA | +| Buy and hold licences and usage rights for backup solutions provided by OVHcloud | | RA | + +#### 2.2. Reversibility model + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Offer standard solutions and protocols for importing and exporting data | I | RA | + +### 3. Service usage + +#### 3.1. Operations + +##### **3.1.1. Daily operations** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Use all virtual machines (nodes) deployed in the IaaS | | RA | +| Decide to add/delete resources to the existing service | RA | I | +| Add/delete resources to the existing service | I | RA | + +##### **3.1.2. Access management** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage access and security policy for Service users | RA | I | +| Managing OVHcloud teams’ physical access to infrastructures | | RA | +| Managing OVHcloud teams’ logical access to infrastructures | I | RA | +| Managing access to the OVHcloud Control Panel | RA | I | +| Manage access to management interfaces specific to the Service (command line, API, etc.) | RA | I | + +##### **3.1.3. Monitoring** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Monitor the proper functioning of physical devices (utilities) in support of the Platform as a Service | | RA | +| Monitor the proper functioning of virtual devices (utilities) in support of Platform as a Service | I | RA | +| Monitor physical and virtual resource performance | I | RA | +| Monitor service performance | RA | I | +| Process and pay for alarms from managed devices in the Public Cloud Analytics infrastructure | I | RA | +| Maintain logs generated by Public Cloud Analytics services | RA | RA | +| Keep logs of the Service hosted on Public Cloud Analytics | RA | + +##### **3.1.4. Storage** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Managing content hosted on Public Cloud Analytics services | RA | I | +| Ensuring data continuity and sustainability | RA | | +| Perform storage and backup device maintenance | | RA | +| Create, modify, control, restore, delete internal backup jobs | I | RA | + +##### **3.1.5. Connectivity** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Operate automatic network management systems (architecture, implementation, software and hardware maintenance for deployed public and private networks) | I | RA | +| Manage IP addressing plan | RA | | + +##### **3.1.6. Management** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Ensuring the security of management infrastructures (API, Control Panel) | I | RA | +| Ensure the security of the operating systems and software installed on the services | I | RA | +| Managing the physical security of equipment and infrastructures hosted at OVHcloud | I | RA | +| Maintain Public Cloud Analytics services and their extensions | C | RA | + +##### **3.1.7. Business continuity** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage automatic management systems for the infrastructure provided | I | RA | +| Maintain a business continuity and disaster recovery plan for hosted services | RA | I | + +#### 3.2. Event management + +##### **3.2.1. Incidents** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Intervening with Public Cloud Analytics managed elements | | RA | + +##### **3.2.2. Changes** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Comply with the Public Cloud Enterprise Lifecycle Policy | RA | | +| Deploy patches, update software and information systems hosted in Public Cloud Analytics | CI | RA | +| Confirm the customer's request to change the hardware or software for the Analytics service | A | R | +| Deploy patches, update and configure the information system using Public Cloud Analytics | RA | | +| Perform preventive interventions on managed elements of the Public Cloud Analytics | I | AR | + +### 4. Reverting + +#### 4.1. Reversibility model + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Schedule reversibility operations | RA | I | +| Choose fallback infrastructures | RA | + +#### 4.2. Data recovery + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage reversibility operations | RA | I | +| Migrate/transfer data | RA | + +### 5. End of service + +#### 5.1. Destroying configurations + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Delete Public Cloud project services | RA | I | + +## Go further + +Visit our dedicated Discord channel: . 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](/links/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 . diff --git a/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.en-ca.md b/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.en-ca.md new file mode 100644 index 00000000000..244043a6a81 --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.en-ca.md @@ -0,0 +1,164 @@ +--- +title: Analytics - Responsibility model +excerpt: 'Shared responsibilities between OVHcloud and the customer' +updated: 2025-11-04 +--- + +Public Cloud Analytics allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions. + +The RACI below details shared responsibilities between OVHcloud and the customer for Public Cloud Analytics services. +This shared model can help relieve the customer’s operational burden. + +## RACI definition + +| Roles | +| --- | +| R: Is in charge of carrying out the process | +| A: Guarantees the successful completion of the process | +| 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 Analytics service such as a Kafka or OpenSearch cluster. + +### 1. Before subscription + +#### 1.1. Specify service as needed + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Learn about the capabilities and limitations of the Services detailed in the OVHcloud documentation | RA | I | +| Choose service location | RA | I | +| Size services as needed | RA | I | +| Choose options as needed | RA | I | + +### 2. Service availability + +#### 2.1. Install service + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Produce, route, deliver and maintain physical machines, virtual machines and hosting buildings | | RA | +| Buy and hold licences and usage rights for software provided by OVHcloud | | RA | +| Buy and hold licences and usage rights for backup solutions provided by OVHcloud | | RA | + +#### 2.2. Reversibility model + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Offer standard solutions and protocols for importing and exporting data | I | RA | + +### 3. Service usage + +#### 3.1. Operations + +##### **3.1.1. Daily operations** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Use all virtual machines (nodes) deployed in the IaaS | | RA | +| Decide to add/delete resources to the existing service | RA | I | +| Add/delete resources to the existing service | I | RA | + +##### **3.1.2. Access management** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage access and security policy for Service users | RA | I | +| Managing OVHcloud teams’ physical access to infrastructures | | RA | +| Managing OVHcloud teams’ logical access to infrastructures | I | RA | +| Managing access to the OVHcloud Control Panel | RA | I | +| Manage access to management interfaces specific to the Service (command line, API, etc.) | RA | I | + +##### **3.1.3. Monitoring** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Monitor the proper functioning of physical devices (utilities) in support of the Platform as a Service | | RA | +| Monitor the proper functioning of virtual devices (utilities) in support of Platform as a Service | I | RA | +| Monitor physical and virtual resource performance | I | RA | +| Monitor service performance | RA | I | +| Process and pay for alarms from managed devices in the Public Cloud Analytics infrastructure | I | RA | +| Maintain logs generated by Public Cloud Analytics services | RA | RA | +| Keep logs of the Service hosted on Public Cloud Analytics | RA | + +##### **3.1.4. Storage** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Managing content hosted on Public Cloud Analytics services | RA | I | +| Ensuring data continuity and sustainability | RA | | +| Perform storage and backup device maintenance | | RA | +| Create, modify, control, restore, delete internal backup jobs | I | RA | + +##### **3.1.5. Connectivity** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Operate automatic network management systems (architecture, implementation, software and hardware maintenance for deployed public and private networks) | I | RA | +| Manage IP addressing plan | RA | | + +##### **3.1.6. Management** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Ensuring the security of management infrastructures (API, Control Panel) | I | RA | +| Ensure the security of the operating systems and software installed on the services | I | RA | +| Managing the physical security of equipment and infrastructures hosted at OVHcloud | I | RA | +| Maintain Public Cloud Analytics services and their extensions | C | RA | + +##### **3.1.7. Business continuity** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage automatic management systems for the infrastructure provided | I | RA | +| Maintain a business continuity and disaster recovery plan for hosted services | RA | I | + +#### 3.2. Event management + +##### **3.2.1. Incidents** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Intervening with Public Cloud Analytics managed elements | | RA | + +##### **3.2.2. Changes** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Comply with the Public Cloud Enterprise Lifecycle Policy | RA | | +| Deploy patches, update software and information systems hosted in Public Cloud Analytics | CI | RA | +| Confirm the customer's request to change the hardware or software for the Analytics service | A | R | +| Deploy patches, update and configure the information system using Public Cloud Analytics | RA | | +| Perform preventive interventions on managed elements of the Public Cloud Analytics | I | AR | + +### 4. Reverting + +#### 4.1. Reversibility model + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Schedule reversibility operations | RA | I | +| Choose fallback infrastructures | RA | + +#### 4.2. Data recovery + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage reversibility operations | RA | I | +| Migrate/transfer data | RA | + +### 5. End of service + +#### 5.1. Destroying configurations + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Delete Public Cloud project services | RA | I | + +## Go further + +Visit our dedicated Discord channel: . 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](/links/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 . diff --git a/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.en-gb.md b/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.en-gb.md new file mode 100644 index 00000000000..244043a6a81 --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.en-gb.md @@ -0,0 +1,164 @@ +--- +title: Analytics - Responsibility model +excerpt: 'Shared responsibilities between OVHcloud and the customer' +updated: 2025-11-04 +--- + +Public Cloud Analytics allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions. + +The RACI below details shared responsibilities between OVHcloud and the customer for Public Cloud Analytics services. +This shared model can help relieve the customer’s operational burden. + +## RACI definition + +| Roles | +| --- | +| R: Is in charge of carrying out the process | +| A: Guarantees the successful completion of the process | +| 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 Analytics service such as a Kafka or OpenSearch cluster. + +### 1. Before subscription + +#### 1.1. Specify service as needed + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Learn about the capabilities and limitations of the Services detailed in the OVHcloud documentation | RA | I | +| Choose service location | RA | I | +| Size services as needed | RA | I | +| Choose options as needed | RA | I | + +### 2. Service availability + +#### 2.1. Install service + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Produce, route, deliver and maintain physical machines, virtual machines and hosting buildings | | RA | +| Buy and hold licences and usage rights for software provided by OVHcloud | | RA | +| Buy and hold licences and usage rights for backup solutions provided by OVHcloud | | RA | + +#### 2.2. Reversibility model + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Offer standard solutions and protocols for importing and exporting data | I | RA | + +### 3. Service usage + +#### 3.1. Operations + +##### **3.1.1. Daily operations** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Use all virtual machines (nodes) deployed in the IaaS | | RA | +| Decide to add/delete resources to the existing service | RA | I | +| Add/delete resources to the existing service | I | RA | + +##### **3.1.2. Access management** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage access and security policy for Service users | RA | I | +| Managing OVHcloud teams’ physical access to infrastructures | | RA | +| Managing OVHcloud teams’ logical access to infrastructures | I | RA | +| Managing access to the OVHcloud Control Panel | RA | I | +| Manage access to management interfaces specific to the Service (command line, API, etc.) | RA | I | + +##### **3.1.3. Monitoring** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Monitor the proper functioning of physical devices (utilities) in support of the Platform as a Service | | RA | +| Monitor the proper functioning of virtual devices (utilities) in support of Platform as a Service | I | RA | +| Monitor physical and virtual resource performance | I | RA | +| Monitor service performance | RA | I | +| Process and pay for alarms from managed devices in the Public Cloud Analytics infrastructure | I | RA | +| Maintain logs generated by Public Cloud Analytics services | RA | RA | +| Keep logs of the Service hosted on Public Cloud Analytics | RA | + +##### **3.1.4. Storage** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Managing content hosted on Public Cloud Analytics services | RA | I | +| Ensuring data continuity and sustainability | RA | | +| Perform storage and backup device maintenance | | RA | +| Create, modify, control, restore, delete internal backup jobs | I | RA | + +##### **3.1.5. Connectivity** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Operate automatic network management systems (architecture, implementation, software and hardware maintenance for deployed public and private networks) | I | RA | +| Manage IP addressing plan | RA | | + +##### **3.1.6. Management** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Ensuring the security of management infrastructures (API, Control Panel) | I | RA | +| Ensure the security of the operating systems and software installed on the services | I | RA | +| Managing the physical security of equipment and infrastructures hosted at OVHcloud | I | RA | +| Maintain Public Cloud Analytics services and their extensions | C | RA | + +##### **3.1.7. Business continuity** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage automatic management systems for the infrastructure provided | I | RA | +| Maintain a business continuity and disaster recovery plan for hosted services | RA | I | + +#### 3.2. Event management + +##### **3.2.1. Incidents** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Intervening with Public Cloud Analytics managed elements | | RA | + +##### **3.2.2. Changes** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Comply with the Public Cloud Enterprise Lifecycle Policy | RA | | +| Deploy patches, update software and information systems hosted in Public Cloud Analytics | CI | RA | +| Confirm the customer's request to change the hardware or software for the Analytics service | A | R | +| Deploy patches, update and configure the information system using Public Cloud Analytics | RA | | +| Perform preventive interventions on managed elements of the Public Cloud Analytics | I | AR | + +### 4. Reverting + +#### 4.1. Reversibility model + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Schedule reversibility operations | RA | I | +| Choose fallback infrastructures | RA | + +#### 4.2. Data recovery + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage reversibility operations | RA | I | +| Migrate/transfer data | RA | + +### 5. End of service + +#### 5.1. Destroying configurations + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Delete Public Cloud project services | RA | I | + +## Go further + +Visit our dedicated Discord channel: . 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](/links/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 . diff --git a/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.en-ie.md b/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.en-ie.md new file mode 100644 index 00000000000..244043a6a81 --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.en-ie.md @@ -0,0 +1,164 @@ +--- +title: Analytics - Responsibility model +excerpt: 'Shared responsibilities between OVHcloud and the customer' +updated: 2025-11-04 +--- + +Public Cloud Analytics allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions. + +The RACI below details shared responsibilities between OVHcloud and the customer for Public Cloud Analytics services. +This shared model can help relieve the customer’s operational burden. + +## RACI definition + +| Roles | +| --- | +| R: Is in charge of carrying out the process | +| A: Guarantees the successful completion of the process | +| 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 Analytics service such as a Kafka or OpenSearch cluster. + +### 1. Before subscription + +#### 1.1. Specify service as needed + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Learn about the capabilities and limitations of the Services detailed in the OVHcloud documentation | RA | I | +| Choose service location | RA | I | +| Size services as needed | RA | I | +| Choose options as needed | RA | I | + +### 2. Service availability + +#### 2.1. Install service + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Produce, route, deliver and maintain physical machines, virtual machines and hosting buildings | | RA | +| Buy and hold licences and usage rights for software provided by OVHcloud | | RA | +| Buy and hold licences and usage rights for backup solutions provided by OVHcloud | | RA | + +#### 2.2. Reversibility model + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Offer standard solutions and protocols for importing and exporting data | I | RA | + +### 3. Service usage + +#### 3.1. Operations + +##### **3.1.1. Daily operations** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Use all virtual machines (nodes) deployed in the IaaS | | RA | +| Decide to add/delete resources to the existing service | RA | I | +| Add/delete resources to the existing service | I | RA | + +##### **3.1.2. Access management** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage access and security policy for Service users | RA | I | +| Managing OVHcloud teams’ physical access to infrastructures | | RA | +| Managing OVHcloud teams’ logical access to infrastructures | I | RA | +| Managing access to the OVHcloud Control Panel | RA | I | +| Manage access to management interfaces specific to the Service (command line, API, etc.) | RA | I | + +##### **3.1.3. Monitoring** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Monitor the proper functioning of physical devices (utilities) in support of the Platform as a Service | | RA | +| Monitor the proper functioning of virtual devices (utilities) in support of Platform as a Service | I | RA | +| Monitor physical and virtual resource performance | I | RA | +| Monitor service performance | RA | I | +| Process and pay for alarms from managed devices in the Public Cloud Analytics infrastructure | I | RA | +| Maintain logs generated by Public Cloud Analytics services | RA | RA | +| Keep logs of the Service hosted on Public Cloud Analytics | RA | + +##### **3.1.4. Storage** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Managing content hosted on Public Cloud Analytics services | RA | I | +| Ensuring data continuity and sustainability | RA | | +| Perform storage and backup device maintenance | | RA | +| Create, modify, control, restore, delete internal backup jobs | I | RA | + +##### **3.1.5. Connectivity** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Operate automatic network management systems (architecture, implementation, software and hardware maintenance for deployed public and private networks) | I | RA | +| Manage IP addressing plan | RA | | + +##### **3.1.6. Management** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Ensuring the security of management infrastructures (API, Control Panel) | I | RA | +| Ensure the security of the operating systems and software installed on the services | I | RA | +| Managing the physical security of equipment and infrastructures hosted at OVHcloud | I | RA | +| Maintain Public Cloud Analytics services and their extensions | C | RA | + +##### **3.1.7. Business continuity** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage automatic management systems for the infrastructure provided | I | RA | +| Maintain a business continuity and disaster recovery plan for hosted services | RA | I | + +#### 3.2. Event management + +##### **3.2.1. Incidents** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Intervening with Public Cloud Analytics managed elements | | RA | + +##### **3.2.2. Changes** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Comply with the Public Cloud Enterprise Lifecycle Policy | RA | | +| Deploy patches, update software and information systems hosted in Public Cloud Analytics | CI | RA | +| Confirm the customer's request to change the hardware or software for the Analytics service | A | R | +| Deploy patches, update and configure the information system using Public Cloud Analytics | RA | | +| Perform preventive interventions on managed elements of the Public Cloud Analytics | I | AR | + +### 4. Reverting + +#### 4.1. Reversibility model + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Schedule reversibility operations | RA | I | +| Choose fallback infrastructures | RA | + +#### 4.2. Data recovery + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage reversibility operations | RA | I | +| Migrate/transfer data | RA | + +### 5. End of service + +#### 5.1. Destroying configurations + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Delete Public Cloud project services | RA | I | + +## Go further + +Visit our dedicated Discord channel: . 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](/links/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 . diff --git a/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.en-sg.md b/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.en-sg.md new file mode 100644 index 00000000000..244043a6a81 --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.en-sg.md @@ -0,0 +1,164 @@ +--- +title: Analytics - Responsibility model +excerpt: 'Shared responsibilities between OVHcloud and the customer' +updated: 2025-11-04 +--- + +Public Cloud Analytics allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions. + +The RACI below details shared responsibilities between OVHcloud and the customer for Public Cloud Analytics services. +This shared model can help relieve the customer’s operational burden. + +## RACI definition + +| Roles | +| --- | +| R: Is in charge of carrying out the process | +| A: Guarantees the successful completion of the process | +| 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 Analytics service such as a Kafka or OpenSearch cluster. + +### 1. Before subscription + +#### 1.1. Specify service as needed + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Learn about the capabilities and limitations of the Services detailed in the OVHcloud documentation | RA | I | +| Choose service location | RA | I | +| Size services as needed | RA | I | +| Choose options as needed | RA | I | + +### 2. Service availability + +#### 2.1. Install service + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Produce, route, deliver and maintain physical machines, virtual machines and hosting buildings | | RA | +| Buy and hold licences and usage rights for software provided by OVHcloud | | RA | +| Buy and hold licences and usage rights for backup solutions provided by OVHcloud | | RA | + +#### 2.2. Reversibility model + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Offer standard solutions and protocols for importing and exporting data | I | RA | + +### 3. Service usage + +#### 3.1. Operations + +##### **3.1.1. Daily operations** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Use all virtual machines (nodes) deployed in the IaaS | | RA | +| Decide to add/delete resources to the existing service | RA | I | +| Add/delete resources to the existing service | I | RA | + +##### **3.1.2. Access management** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage access and security policy for Service users | RA | I | +| Managing OVHcloud teams’ physical access to infrastructures | | RA | +| Managing OVHcloud teams’ logical access to infrastructures | I | RA | +| Managing access to the OVHcloud Control Panel | RA | I | +| Manage access to management interfaces specific to the Service (command line, API, etc.) | RA | I | + +##### **3.1.3. Monitoring** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Monitor the proper functioning of physical devices (utilities) in support of the Platform as a Service | | RA | +| Monitor the proper functioning of virtual devices (utilities) in support of Platform as a Service | I | RA | +| Monitor physical and virtual resource performance | I | RA | +| Monitor service performance | RA | I | +| Process and pay for alarms from managed devices in the Public Cloud Analytics infrastructure | I | RA | +| Maintain logs generated by Public Cloud Analytics services | RA | RA | +| Keep logs of the Service hosted on Public Cloud Analytics | RA | + +##### **3.1.4. Storage** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Managing content hosted on Public Cloud Analytics services | RA | I | +| Ensuring data continuity and sustainability | RA | | +| Perform storage and backup device maintenance | | RA | +| Create, modify, control, restore, delete internal backup jobs | I | RA | + +##### **3.1.5. Connectivity** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Operate automatic network management systems (architecture, implementation, software and hardware maintenance for deployed public and private networks) | I | RA | +| Manage IP addressing plan | RA | | + +##### **3.1.6. Management** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Ensuring the security of management infrastructures (API, Control Panel) | I | RA | +| Ensure the security of the operating systems and software installed on the services | I | RA | +| Managing the physical security of equipment and infrastructures hosted at OVHcloud | I | RA | +| Maintain Public Cloud Analytics services and their extensions | C | RA | + +##### **3.1.7. Business continuity** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage automatic management systems for the infrastructure provided | I | RA | +| Maintain a business continuity and disaster recovery plan for hosted services | RA | I | + +#### 3.2. Event management + +##### **3.2.1. Incidents** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Intervening with Public Cloud Analytics managed elements | | RA | + +##### **3.2.2. Changes** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Comply with the Public Cloud Enterprise Lifecycle Policy | RA | | +| Deploy patches, update software and information systems hosted in Public Cloud Analytics | CI | RA | +| Confirm the customer's request to change the hardware or software for the Analytics service | A | R | +| Deploy patches, update and configure the information system using Public Cloud Analytics | RA | | +| Perform preventive interventions on managed elements of the Public Cloud Analytics | I | AR | + +### 4. Reverting + +#### 4.1. Reversibility model + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Schedule reversibility operations | RA | I | +| Choose fallback infrastructures | RA | + +#### 4.2. Data recovery + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage reversibility operations | RA | I | +| Migrate/transfer data | RA | + +### 5. End of service + +#### 5.1. Destroying configurations + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Delete Public Cloud project services | RA | I | + +## Go further + +Visit our dedicated Discord channel: . 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](/links/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 . diff --git a/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.en-us.md b/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.en-us.md new file mode 100644 index 00000000000..244043a6a81 --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.en-us.md @@ -0,0 +1,164 @@ +--- +title: Analytics - Responsibility model +excerpt: 'Shared responsibilities between OVHcloud and the customer' +updated: 2025-11-04 +--- + +Public Cloud Analytics allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions. + +The RACI below details shared responsibilities between OVHcloud and the customer for Public Cloud Analytics services. +This shared model can help relieve the customer’s operational burden. + +## RACI definition + +| Roles | +| --- | +| R: Is in charge of carrying out the process | +| A: Guarantees the successful completion of the process | +| 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 Analytics service such as a Kafka or OpenSearch cluster. + +### 1. Before subscription + +#### 1.1. Specify service as needed + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Learn about the capabilities and limitations of the Services detailed in the OVHcloud documentation | RA | I | +| Choose service location | RA | I | +| Size services as needed | RA | I | +| Choose options as needed | RA | I | + +### 2. Service availability + +#### 2.1. Install service + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Produce, route, deliver and maintain physical machines, virtual machines and hosting buildings | | RA | +| Buy and hold licences and usage rights for software provided by OVHcloud | | RA | +| Buy and hold licences and usage rights for backup solutions provided by OVHcloud | | RA | + +#### 2.2. Reversibility model + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Offer standard solutions and protocols for importing and exporting data | I | RA | + +### 3. Service usage + +#### 3.1. Operations + +##### **3.1.1. Daily operations** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Use all virtual machines (nodes) deployed in the IaaS | | RA | +| Decide to add/delete resources to the existing service | RA | I | +| Add/delete resources to the existing service | I | RA | + +##### **3.1.2. Access management** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage access and security policy for Service users | RA | I | +| Managing OVHcloud teams’ physical access to infrastructures | | RA | +| Managing OVHcloud teams’ logical access to infrastructures | I | RA | +| Managing access to the OVHcloud Control Panel | RA | I | +| Manage access to management interfaces specific to the Service (command line, API, etc.) | RA | I | + +##### **3.1.3. Monitoring** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Monitor the proper functioning of physical devices (utilities) in support of the Platform as a Service | | RA | +| Monitor the proper functioning of virtual devices (utilities) in support of Platform as a Service | I | RA | +| Monitor physical and virtual resource performance | I | RA | +| Monitor service performance | RA | I | +| Process and pay for alarms from managed devices in the Public Cloud Analytics infrastructure | I | RA | +| Maintain logs generated by Public Cloud Analytics services | RA | RA | +| Keep logs of the Service hosted on Public Cloud Analytics | RA | + +##### **3.1.4. Storage** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Managing content hosted on Public Cloud Analytics services | RA | I | +| Ensuring data continuity and sustainability | RA | | +| Perform storage and backup device maintenance | | RA | +| Create, modify, control, restore, delete internal backup jobs | I | RA | + +##### **3.1.5. Connectivity** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Operate automatic network management systems (architecture, implementation, software and hardware maintenance for deployed public and private networks) | I | RA | +| Manage IP addressing plan | RA | | + +##### **3.1.6. Management** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Ensuring the security of management infrastructures (API, Control Panel) | I | RA | +| Ensure the security of the operating systems and software installed on the services | I | RA | +| Managing the physical security of equipment and infrastructures hosted at OVHcloud | I | RA | +| Maintain Public Cloud Analytics services and their extensions | C | RA | + +##### **3.1.7. Business continuity** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage automatic management systems for the infrastructure provided | I | RA | +| Maintain a business continuity and disaster recovery plan for hosted services | RA | I | + +#### 3.2. Event management + +##### **3.2.1. Incidents** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Intervening with Public Cloud Analytics managed elements | | RA | + +##### **3.2.2. Changes** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Comply with the Public Cloud Enterprise Lifecycle Policy | RA | | +| Deploy patches, update software and information systems hosted in Public Cloud Analytics | CI | RA | +| Confirm the customer's request to change the hardware or software for the Analytics service | A | R | +| Deploy patches, update and configure the information system using Public Cloud Analytics | RA | | +| Perform preventive interventions on managed elements of the Public Cloud Analytics | I | AR | + +### 4. Reverting + +#### 4.1. Reversibility model + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Schedule reversibility operations | RA | I | +| Choose fallback infrastructures | RA | + +#### 4.2. Data recovery + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage reversibility operations | RA | I | +| Migrate/transfer data | RA | + +### 5. End of service + +#### 5.1. Destroying configurations + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Delete Public Cloud project services | RA | I | + +## Go further + +Visit our dedicated Discord channel: . 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](/links/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 . diff --git a/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.es-es.md b/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.es-es.md new file mode 100644 index 00000000000..244043a6a81 --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.es-es.md @@ -0,0 +1,164 @@ +--- +title: Analytics - Responsibility model +excerpt: 'Shared responsibilities between OVHcloud and the customer' +updated: 2025-11-04 +--- + +Public Cloud Analytics allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions. + +The RACI below details shared responsibilities between OVHcloud and the customer for Public Cloud Analytics services. +This shared model can help relieve the customer’s operational burden. + +## RACI definition + +| Roles | +| --- | +| R: Is in charge of carrying out the process | +| A: Guarantees the successful completion of the process | +| 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 Analytics service such as a Kafka or OpenSearch cluster. + +### 1. Before subscription + +#### 1.1. Specify service as needed + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Learn about the capabilities and limitations of the Services detailed in the OVHcloud documentation | RA | I | +| Choose service location | RA | I | +| Size services as needed | RA | I | +| Choose options as needed | RA | I | + +### 2. Service availability + +#### 2.1. Install service + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Produce, route, deliver and maintain physical machines, virtual machines and hosting buildings | | RA | +| Buy and hold licences and usage rights for software provided by OVHcloud | | RA | +| Buy and hold licences and usage rights for backup solutions provided by OVHcloud | | RA | + +#### 2.2. Reversibility model + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Offer standard solutions and protocols for importing and exporting data | I | RA | + +### 3. Service usage + +#### 3.1. Operations + +##### **3.1.1. Daily operations** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Use all virtual machines (nodes) deployed in the IaaS | | RA | +| Decide to add/delete resources to the existing service | RA | I | +| Add/delete resources to the existing service | I | RA | + +##### **3.1.2. Access management** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage access and security policy for Service users | RA | I | +| Managing OVHcloud teams’ physical access to infrastructures | | RA | +| Managing OVHcloud teams’ logical access to infrastructures | I | RA | +| Managing access to the OVHcloud Control Panel | RA | I | +| Manage access to management interfaces specific to the Service (command line, API, etc.) | RA | I | + +##### **3.1.3. Monitoring** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Monitor the proper functioning of physical devices (utilities) in support of the Platform as a Service | | RA | +| Monitor the proper functioning of virtual devices (utilities) in support of Platform as a Service | I | RA | +| Monitor physical and virtual resource performance | I | RA | +| Monitor service performance | RA | I | +| Process and pay for alarms from managed devices in the Public Cloud Analytics infrastructure | I | RA | +| Maintain logs generated by Public Cloud Analytics services | RA | RA | +| Keep logs of the Service hosted on Public Cloud Analytics | RA | + +##### **3.1.4. Storage** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Managing content hosted on Public Cloud Analytics services | RA | I | +| Ensuring data continuity and sustainability | RA | | +| Perform storage and backup device maintenance | | RA | +| Create, modify, control, restore, delete internal backup jobs | I | RA | + +##### **3.1.5. Connectivity** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Operate automatic network management systems (architecture, implementation, software and hardware maintenance for deployed public and private networks) | I | RA | +| Manage IP addressing plan | RA | | + +##### **3.1.6. Management** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Ensuring the security of management infrastructures (API, Control Panel) | I | RA | +| Ensure the security of the operating systems and software installed on the services | I | RA | +| Managing the physical security of equipment and infrastructures hosted at OVHcloud | I | RA | +| Maintain Public Cloud Analytics services and their extensions | C | RA | + +##### **3.1.7. Business continuity** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage automatic management systems for the infrastructure provided | I | RA | +| Maintain a business continuity and disaster recovery plan for hosted services | RA | I | + +#### 3.2. Event management + +##### **3.2.1. Incidents** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Intervening with Public Cloud Analytics managed elements | | RA | + +##### **3.2.2. Changes** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Comply with the Public Cloud Enterprise Lifecycle Policy | RA | | +| Deploy patches, update software and information systems hosted in Public Cloud Analytics | CI | RA | +| Confirm the customer's request to change the hardware or software for the Analytics service | A | R | +| Deploy patches, update and configure the information system using Public Cloud Analytics | RA | | +| Perform preventive interventions on managed elements of the Public Cloud Analytics | I | AR | + +### 4. Reverting + +#### 4.1. Reversibility model + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Schedule reversibility operations | RA | I | +| Choose fallback infrastructures | RA | + +#### 4.2. Data recovery + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage reversibility operations | RA | I | +| Migrate/transfer data | RA | + +### 5. End of service + +#### 5.1. Destroying configurations + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Delete Public Cloud project services | RA | I | + +## Go further + +Visit our dedicated Discord channel: . 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](/links/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 . diff --git a/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.es-us.md b/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.es-us.md new file mode 100644 index 00000000000..244043a6a81 --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.es-us.md @@ -0,0 +1,164 @@ +--- +title: Analytics - Responsibility model +excerpt: 'Shared responsibilities between OVHcloud and the customer' +updated: 2025-11-04 +--- + +Public Cloud Analytics allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions. + +The RACI below details shared responsibilities between OVHcloud and the customer for Public Cloud Analytics services. +This shared model can help relieve the customer’s operational burden. + +## RACI definition + +| Roles | +| --- | +| R: Is in charge of carrying out the process | +| A: Guarantees the successful completion of the process | +| 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 Analytics service such as a Kafka or OpenSearch cluster. + +### 1. Before subscription + +#### 1.1. Specify service as needed + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Learn about the capabilities and limitations of the Services detailed in the OVHcloud documentation | RA | I | +| Choose service location | RA | I | +| Size services as needed | RA | I | +| Choose options as needed | RA | I | + +### 2. Service availability + +#### 2.1. Install service + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Produce, route, deliver and maintain physical machines, virtual machines and hosting buildings | | RA | +| Buy and hold licences and usage rights for software provided by OVHcloud | | RA | +| Buy and hold licences and usage rights for backup solutions provided by OVHcloud | | RA | + +#### 2.2. Reversibility model + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Offer standard solutions and protocols for importing and exporting data | I | RA | + +### 3. Service usage + +#### 3.1. Operations + +##### **3.1.1. Daily operations** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Use all virtual machines (nodes) deployed in the IaaS | | RA | +| Decide to add/delete resources to the existing service | RA | I | +| Add/delete resources to the existing service | I | RA | + +##### **3.1.2. Access management** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage access and security policy for Service users | RA | I | +| Managing OVHcloud teams’ physical access to infrastructures | | RA | +| Managing OVHcloud teams’ logical access to infrastructures | I | RA | +| Managing access to the OVHcloud Control Panel | RA | I | +| Manage access to management interfaces specific to the Service (command line, API, etc.) | RA | I | + +##### **3.1.3. Monitoring** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Monitor the proper functioning of physical devices (utilities) in support of the Platform as a Service | | RA | +| Monitor the proper functioning of virtual devices (utilities) in support of Platform as a Service | I | RA | +| Monitor physical and virtual resource performance | I | RA | +| Monitor service performance | RA | I | +| Process and pay for alarms from managed devices in the Public Cloud Analytics infrastructure | I | RA | +| Maintain logs generated by Public Cloud Analytics services | RA | RA | +| Keep logs of the Service hosted on Public Cloud Analytics | RA | + +##### **3.1.4. Storage** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Managing content hosted on Public Cloud Analytics services | RA | I | +| Ensuring data continuity and sustainability | RA | | +| Perform storage and backup device maintenance | | RA | +| Create, modify, control, restore, delete internal backup jobs | I | RA | + +##### **3.1.5. Connectivity** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Operate automatic network management systems (architecture, implementation, software and hardware maintenance for deployed public and private networks) | I | RA | +| Manage IP addressing plan | RA | | + +##### **3.1.6. Management** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Ensuring the security of management infrastructures (API, Control Panel) | I | RA | +| Ensure the security of the operating systems and software installed on the services | I | RA | +| Managing the physical security of equipment and infrastructures hosted at OVHcloud | I | RA | +| Maintain Public Cloud Analytics services and their extensions | C | RA | + +##### **3.1.7. Business continuity** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage automatic management systems for the infrastructure provided | I | RA | +| Maintain a business continuity and disaster recovery plan for hosted services | RA | I | + +#### 3.2. Event management + +##### **3.2.1. Incidents** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Intervening with Public Cloud Analytics managed elements | | RA | + +##### **3.2.2. Changes** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Comply with the Public Cloud Enterprise Lifecycle Policy | RA | | +| Deploy patches, update software and information systems hosted in Public Cloud Analytics | CI | RA | +| Confirm the customer's request to change the hardware or software for the Analytics service | A | R | +| Deploy patches, update and configure the information system using Public Cloud Analytics | RA | | +| Perform preventive interventions on managed elements of the Public Cloud Analytics | I | AR | + +### 4. Reverting + +#### 4.1. Reversibility model + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Schedule reversibility operations | RA | I | +| Choose fallback infrastructures | RA | + +#### 4.2. Data recovery + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage reversibility operations | RA | I | +| Migrate/transfer data | RA | + +### 5. End of service + +#### 5.1. Destroying configurations + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Delete Public Cloud project services | RA | I | + +## Go further + +Visit our dedicated Discord channel: . 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](/links/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 . diff --git a/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.fr-ca.md b/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.fr-ca.md new file mode 100644 index 00000000000..dfa40c4860f --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.fr-ca.md @@ -0,0 +1,164 @@ +--- +title: Analytics - Partage des responsabilités (EN) +excerpt: 'Shared responsibilities between OVHcloud and the customer' +updated: 2025-11-04 +--- + +Public Cloud Analytics allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions. + +The RACI below details shared responsibilities between OVHcloud and the customer for Public Cloud Analytics services. +This shared model can help relieve the customer’s operational burden. + +## RACI definition + +| Roles | +| --- | +| R: Is in charge of carrying out the process | +| A: Guarantees the successful completion of the process | +| 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 Analytics service such as a Kafka or OpenSearch cluster. + +### 1. Before subscription + +#### 1.1. Specify service as needed + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Learn about the capabilities and limitations of the Services detailed in the OVHcloud documentation | RA | I | +| Choose service location | RA | I | +| Size services as needed | RA | I | +| Choose options as needed | RA | I | + +### 2. Service availability + +#### 2.1. Install service + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Produce, route, deliver and maintain physical machines, virtual machines and hosting buildings | | RA | +| Buy and hold licences and usage rights for software provided by OVHcloud | | RA | +| Buy and hold licences and usage rights for backup solutions provided by OVHcloud | | RA | + +#### 2.2. Reversibility model + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Offer standard solutions and protocols for importing and exporting data | I | RA | + +### 3. Service usage + +#### 3.1. Operations + +##### **3.1.1. Daily operations** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Use all virtual machines (nodes) deployed in the IaaS | | RA | +| Decide to add/delete resources to the existing service | RA | I | +| Add/delete resources to the existing service | I | RA | + +##### **3.1.2. Access management** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage access and security policy for Service users | RA | I | +| Managing OVHcloud teams’ physical access to infrastructures | | RA | +| Managing OVHcloud teams’ logical access to infrastructures | I | RA | +| Managing access to the OVHcloud Control Panel | RA | I | +| Manage access to management interfaces specific to the Service (command line, API, etc.) | RA | I | + +##### **3.1.3. Monitoring** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Monitor the proper functioning of physical devices (utilities) in support of the Platform as a Service | | RA | +| Monitor the proper functioning of virtual devices (utilities) in support of Platform as a Service | I | RA | +| Monitor physical and virtual resource performance | I | RA | +| Monitor service performance | RA | I | +| Process and pay for alarms from managed devices in the Public Cloud Analytics infrastructure | I | RA | +| Maintain logs generated by Public Cloud Analytics services | RA | RA | +| Keep logs of the Service hosted on Public Cloud Analytics | RA | + +##### **3.1.4. Storage** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Managing content hosted on Public Cloud Analytics services | RA | I | +| Ensuring data continuity and sustainability | RA | | +| Perform storage and backup device maintenance | | RA | +| Create, modify, control, restore, delete internal backup jobs | I | RA | + +##### **3.1.5. Connectivity** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Operate automatic network management systems (architecture, implementation, software and hardware maintenance for deployed public and private networks) | I | RA | +| Manage IP addressing plan | RA | | + +##### **3.1.6. Management** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Ensuring the security of management infrastructures (API, Control Panel) | I | RA | +| Ensure the security of the operating systems and software installed on the services | I | RA | +| Managing the physical security of equipment and infrastructures hosted at OVHcloud | I | RA | +| Maintain Public Cloud Analytics services and their extensions | C | RA | + +##### **3.1.7. Business continuity** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage automatic management systems for the infrastructure provided | I | RA | +| Maintain a business continuity and disaster recovery plan for hosted services | RA | I | + +#### 3.2. Event management + +##### **3.2.1. Incidents** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Intervening with Public Cloud Analytics managed elements | | RA | + +##### **3.2.2. Changes** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Comply with the Public Cloud Enterprise Lifecycle Policy | RA | | +| Deploy patches, update software and information systems hosted in Public Cloud Analytics | CI | RA | +| Confirm the customer's request to change the hardware or software for the Analytics service | A | R | +| Deploy patches, update and configure the information system using Public Cloud Analytics | RA | | +| Perform preventive interventions on managed elements of the Public Cloud Analytics | I | AR | + +### 4. Reverting + +#### 4.1. Reversibility model + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Schedule reversibility operations | RA | I | +| Choose fallback infrastructures | RA | + +#### 4.2. Data recovery + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage reversibility operations | RA | I | +| Migrate/transfer data | RA | + +### 5. End of service + +#### 5.1. Destroying configurations + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Delete Public Cloud project services | RA | I | + +## Go further + +Visit our dedicated Discord channel: . 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](/links/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 . diff --git a/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.fr-fr.md b/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.fr-fr.md new file mode 100644 index 00000000000..dfa40c4860f --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.fr-fr.md @@ -0,0 +1,164 @@ +--- +title: Analytics - Partage des responsabilités (EN) +excerpt: 'Shared responsibilities between OVHcloud and the customer' +updated: 2025-11-04 +--- + +Public Cloud Analytics allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions. + +The RACI below details shared responsibilities between OVHcloud and the customer for Public Cloud Analytics services. +This shared model can help relieve the customer’s operational burden. + +## RACI definition + +| Roles | +| --- | +| R: Is in charge of carrying out the process | +| A: Guarantees the successful completion of the process | +| 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 Analytics service such as a Kafka or OpenSearch cluster. + +### 1. Before subscription + +#### 1.1. Specify service as needed + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Learn about the capabilities and limitations of the Services detailed in the OVHcloud documentation | RA | I | +| Choose service location | RA | I | +| Size services as needed | RA | I | +| Choose options as needed | RA | I | + +### 2. Service availability + +#### 2.1. Install service + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Produce, route, deliver and maintain physical machines, virtual machines and hosting buildings | | RA | +| Buy and hold licences and usage rights for software provided by OVHcloud | | RA | +| Buy and hold licences and usage rights for backup solutions provided by OVHcloud | | RA | + +#### 2.2. Reversibility model + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Offer standard solutions and protocols for importing and exporting data | I | RA | + +### 3. Service usage + +#### 3.1. Operations + +##### **3.1.1. Daily operations** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Use all virtual machines (nodes) deployed in the IaaS | | RA | +| Decide to add/delete resources to the existing service | RA | I | +| Add/delete resources to the existing service | I | RA | + +##### **3.1.2. Access management** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage access and security policy for Service users | RA | I | +| Managing OVHcloud teams’ physical access to infrastructures | | RA | +| Managing OVHcloud teams’ logical access to infrastructures | I | RA | +| Managing access to the OVHcloud Control Panel | RA | I | +| Manage access to management interfaces specific to the Service (command line, API, etc.) | RA | I | + +##### **3.1.3. Monitoring** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Monitor the proper functioning of physical devices (utilities) in support of the Platform as a Service | | RA | +| Monitor the proper functioning of virtual devices (utilities) in support of Platform as a Service | I | RA | +| Monitor physical and virtual resource performance | I | RA | +| Monitor service performance | RA | I | +| Process and pay for alarms from managed devices in the Public Cloud Analytics infrastructure | I | RA | +| Maintain logs generated by Public Cloud Analytics services | RA | RA | +| Keep logs of the Service hosted on Public Cloud Analytics | RA | + +##### **3.1.4. Storage** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Managing content hosted on Public Cloud Analytics services | RA | I | +| Ensuring data continuity and sustainability | RA | | +| Perform storage and backup device maintenance | | RA | +| Create, modify, control, restore, delete internal backup jobs | I | RA | + +##### **3.1.5. Connectivity** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Operate automatic network management systems (architecture, implementation, software and hardware maintenance for deployed public and private networks) | I | RA | +| Manage IP addressing plan | RA | | + +##### **3.1.6. Management** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Ensuring the security of management infrastructures (API, Control Panel) | I | RA | +| Ensure the security of the operating systems and software installed on the services | I | RA | +| Managing the physical security of equipment and infrastructures hosted at OVHcloud | I | RA | +| Maintain Public Cloud Analytics services and their extensions | C | RA | + +##### **3.1.7. Business continuity** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage automatic management systems for the infrastructure provided | I | RA | +| Maintain a business continuity and disaster recovery plan for hosted services | RA | I | + +#### 3.2. Event management + +##### **3.2.1. Incidents** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Intervening with Public Cloud Analytics managed elements | | RA | + +##### **3.2.2. Changes** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Comply with the Public Cloud Enterprise Lifecycle Policy | RA | | +| Deploy patches, update software and information systems hosted in Public Cloud Analytics | CI | RA | +| Confirm the customer's request to change the hardware or software for the Analytics service | A | R | +| Deploy patches, update and configure the information system using Public Cloud Analytics | RA | | +| Perform preventive interventions on managed elements of the Public Cloud Analytics | I | AR | + +### 4. Reverting + +#### 4.1. Reversibility model + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Schedule reversibility operations | RA | I | +| Choose fallback infrastructures | RA | + +#### 4.2. Data recovery + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage reversibility operations | RA | I | +| Migrate/transfer data | RA | + +### 5. End of service + +#### 5.1. Destroying configurations + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Delete Public Cloud project services | RA | I | + +## Go further + +Visit our dedicated Discord channel: . 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](/links/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 . diff --git a/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.it-it.md b/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.it-it.md new file mode 100644 index 00000000000..244043a6a81 --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.it-it.md @@ -0,0 +1,164 @@ +--- +title: Analytics - Responsibility model +excerpt: 'Shared responsibilities between OVHcloud and the customer' +updated: 2025-11-04 +--- + +Public Cloud Analytics allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions. + +The RACI below details shared responsibilities between OVHcloud and the customer for Public Cloud Analytics services. +This shared model can help relieve the customer’s operational burden. + +## RACI definition + +| Roles | +| --- | +| R: Is in charge of carrying out the process | +| A: Guarantees the successful completion of the process | +| 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 Analytics service such as a Kafka or OpenSearch cluster. + +### 1. Before subscription + +#### 1.1. Specify service as needed + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Learn about the capabilities and limitations of the Services detailed in the OVHcloud documentation | RA | I | +| Choose service location | RA | I | +| Size services as needed | RA | I | +| Choose options as needed | RA | I | + +### 2. Service availability + +#### 2.1. Install service + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Produce, route, deliver and maintain physical machines, virtual machines and hosting buildings | | RA | +| Buy and hold licences and usage rights for software provided by OVHcloud | | RA | +| Buy and hold licences and usage rights for backup solutions provided by OVHcloud | | RA | + +#### 2.2. Reversibility model + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Offer standard solutions and protocols for importing and exporting data | I | RA | + +### 3. Service usage + +#### 3.1. Operations + +##### **3.1.1. Daily operations** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Use all virtual machines (nodes) deployed in the IaaS | | RA | +| Decide to add/delete resources to the existing service | RA | I | +| Add/delete resources to the existing service | I | RA | + +##### **3.1.2. Access management** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage access and security policy for Service users | RA | I | +| Managing OVHcloud teams’ physical access to infrastructures | | RA | +| Managing OVHcloud teams’ logical access to infrastructures | I | RA | +| Managing access to the OVHcloud Control Panel | RA | I | +| Manage access to management interfaces specific to the Service (command line, API, etc.) | RA | I | + +##### **3.1.3. Monitoring** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Monitor the proper functioning of physical devices (utilities) in support of the Platform as a Service | | RA | +| Monitor the proper functioning of virtual devices (utilities) in support of Platform as a Service | I | RA | +| Monitor physical and virtual resource performance | I | RA | +| Monitor service performance | RA | I | +| Process and pay for alarms from managed devices in the Public Cloud Analytics infrastructure | I | RA | +| Maintain logs generated by Public Cloud Analytics services | RA | RA | +| Keep logs of the Service hosted on Public Cloud Analytics | RA | + +##### **3.1.4. Storage** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Managing content hosted on Public Cloud Analytics services | RA | I | +| Ensuring data continuity and sustainability | RA | | +| Perform storage and backup device maintenance | | RA | +| Create, modify, control, restore, delete internal backup jobs | I | RA | + +##### **3.1.5. Connectivity** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Operate automatic network management systems (architecture, implementation, software and hardware maintenance for deployed public and private networks) | I | RA | +| Manage IP addressing plan | RA | | + +##### **3.1.6. Management** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Ensuring the security of management infrastructures (API, Control Panel) | I | RA | +| Ensure the security of the operating systems and software installed on the services | I | RA | +| Managing the physical security of equipment and infrastructures hosted at OVHcloud | I | RA | +| Maintain Public Cloud Analytics services and their extensions | C | RA | + +##### **3.1.7. Business continuity** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage automatic management systems for the infrastructure provided | I | RA | +| Maintain a business continuity and disaster recovery plan for hosted services | RA | I | + +#### 3.2. Event management + +##### **3.2.1. Incidents** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Intervening with Public Cloud Analytics managed elements | | RA | + +##### **3.2.2. Changes** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Comply with the Public Cloud Enterprise Lifecycle Policy | RA | | +| Deploy patches, update software and information systems hosted in Public Cloud Analytics | CI | RA | +| Confirm the customer's request to change the hardware or software for the Analytics service | A | R | +| Deploy patches, update and configure the information system using Public Cloud Analytics | RA | | +| Perform preventive interventions on managed elements of the Public Cloud Analytics | I | AR | + +### 4. Reverting + +#### 4.1. Reversibility model + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Schedule reversibility operations | RA | I | +| Choose fallback infrastructures | RA | + +#### 4.2. Data recovery + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage reversibility operations | RA | I | +| Migrate/transfer data | RA | + +### 5. End of service + +#### 5.1. Destroying configurations + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Delete Public Cloud project services | RA | I | + +## Go further + +Visit our dedicated Discord channel: . 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](/links/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 . diff --git a/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.pl-pl.md b/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.pl-pl.md new file mode 100644 index 00000000000..244043a6a81 --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.pl-pl.md @@ -0,0 +1,164 @@ +--- +title: Analytics - Responsibility model +excerpt: 'Shared responsibilities between OVHcloud and the customer' +updated: 2025-11-04 +--- + +Public Cloud Analytics allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions. + +The RACI below details shared responsibilities between OVHcloud and the customer for Public Cloud Analytics services. +This shared model can help relieve the customer’s operational burden. + +## RACI definition + +| Roles | +| --- | +| R: Is in charge of carrying out the process | +| A: Guarantees the successful completion of the process | +| 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 Analytics service such as a Kafka or OpenSearch cluster. + +### 1. Before subscription + +#### 1.1. Specify service as needed + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Learn about the capabilities and limitations of the Services detailed in the OVHcloud documentation | RA | I | +| Choose service location | RA | I | +| Size services as needed | RA | I | +| Choose options as needed | RA | I | + +### 2. Service availability + +#### 2.1. Install service + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Produce, route, deliver and maintain physical machines, virtual machines and hosting buildings | | RA | +| Buy and hold licences and usage rights for software provided by OVHcloud | | RA | +| Buy and hold licences and usage rights for backup solutions provided by OVHcloud | | RA | + +#### 2.2. Reversibility model + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Offer standard solutions and protocols for importing and exporting data | I | RA | + +### 3. Service usage + +#### 3.1. Operations + +##### **3.1.1. Daily operations** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Use all virtual machines (nodes) deployed in the IaaS | | RA | +| Decide to add/delete resources to the existing service | RA | I | +| Add/delete resources to the existing service | I | RA | + +##### **3.1.2. Access management** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage access and security policy for Service users | RA | I | +| Managing OVHcloud teams’ physical access to infrastructures | | RA | +| Managing OVHcloud teams’ logical access to infrastructures | I | RA | +| Managing access to the OVHcloud Control Panel | RA | I | +| Manage access to management interfaces specific to the Service (command line, API, etc.) | RA | I | + +##### **3.1.3. Monitoring** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Monitor the proper functioning of physical devices (utilities) in support of the Platform as a Service | | RA | +| Monitor the proper functioning of virtual devices (utilities) in support of Platform as a Service | I | RA | +| Monitor physical and virtual resource performance | I | RA | +| Monitor service performance | RA | I | +| Process and pay for alarms from managed devices in the Public Cloud Analytics infrastructure | I | RA | +| Maintain logs generated by Public Cloud Analytics services | RA | RA | +| Keep logs of the Service hosted on Public Cloud Analytics | RA | + +##### **3.1.4. Storage** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Managing content hosted on Public Cloud Analytics services | RA | I | +| Ensuring data continuity and sustainability | RA | | +| Perform storage and backup device maintenance | | RA | +| Create, modify, control, restore, delete internal backup jobs | I | RA | + +##### **3.1.5. Connectivity** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Operate automatic network management systems (architecture, implementation, software and hardware maintenance for deployed public and private networks) | I | RA | +| Manage IP addressing plan | RA | | + +##### **3.1.6. Management** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Ensuring the security of management infrastructures (API, Control Panel) | I | RA | +| Ensure the security of the operating systems and software installed on the services | I | RA | +| Managing the physical security of equipment and infrastructures hosted at OVHcloud | I | RA | +| Maintain Public Cloud Analytics services and their extensions | C | RA | + +##### **3.1.7. Business continuity** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage automatic management systems for the infrastructure provided | I | RA | +| Maintain a business continuity and disaster recovery plan for hosted services | RA | I | + +#### 3.2. Event management + +##### **3.2.1. Incidents** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Intervening with Public Cloud Analytics managed elements | | RA | + +##### **3.2.2. Changes** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Comply with the Public Cloud Enterprise Lifecycle Policy | RA | | +| Deploy patches, update software and information systems hosted in Public Cloud Analytics | CI | RA | +| Confirm the customer's request to change the hardware or software for the Analytics service | A | R | +| Deploy patches, update and configure the information system using Public Cloud Analytics | RA | | +| Perform preventive interventions on managed elements of the Public Cloud Analytics | I | AR | + +### 4. Reverting + +#### 4.1. Reversibility model + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Schedule reversibility operations | RA | I | +| Choose fallback infrastructures | RA | + +#### 4.2. Data recovery + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage reversibility operations | RA | I | +| Migrate/transfer data | RA | + +### 5. End of service + +#### 5.1. Destroying configurations + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Delete Public Cloud project services | RA | I | + +## Go further + +Visit our dedicated Discord channel: . 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](/links/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 . diff --git a/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.pt-pt.md b/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.pt-pt.md new file mode 100644 index 00000000000..244043a6a81 --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/guide.pt-pt.md @@ -0,0 +1,164 @@ +--- +title: Analytics - Responsibility model +excerpt: 'Shared responsibilities between OVHcloud and the customer' +updated: 2025-11-04 +--- + +Public Cloud Analytics allow you to focus on building and deploying cloud applications while OVHcloud takes care of the database infrastructure and maintenance in operational conditions. + +The RACI below details shared responsibilities between OVHcloud and the customer for Public Cloud Analytics services. +This shared model can help relieve the customer’s operational burden. + +## RACI definition + +| Roles | +| --- | +| R: Is in charge of carrying out the process | +| A: Guarantees the successful completion of the process | +| 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 Analytics service such as a Kafka or OpenSearch cluster. + +### 1. Before subscription + +#### 1.1. Specify service as needed + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Learn about the capabilities and limitations of the Services detailed in the OVHcloud documentation | RA | I | +| Choose service location | RA | I | +| Size services as needed | RA | I | +| Choose options as needed | RA | I | + +### 2. Service availability + +#### 2.1. Install service + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Produce, route, deliver and maintain physical machines, virtual machines and hosting buildings | | RA | +| Buy and hold licences and usage rights for software provided by OVHcloud | | RA | +| Buy and hold licences and usage rights for backup solutions provided by OVHcloud | | RA | + +#### 2.2. Reversibility model + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Offer standard solutions and protocols for importing and exporting data | I | RA | + +### 3. Service usage + +#### 3.1. Operations + +##### **3.1.1. Daily operations** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Use all virtual machines (nodes) deployed in the IaaS | | RA | +| Decide to add/delete resources to the existing service | RA | I | +| Add/delete resources to the existing service | I | RA | + +##### **3.1.2. Access management** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage access and security policy for Service users | RA | I | +| Managing OVHcloud teams’ physical access to infrastructures | | RA | +| Managing OVHcloud teams’ logical access to infrastructures | I | RA | +| Managing access to the OVHcloud Control Panel | RA | I | +| Manage access to management interfaces specific to the Service (command line, API, etc.) | RA | I | + +##### **3.1.3. Monitoring** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Monitor the proper functioning of physical devices (utilities) in support of the Platform as a Service | | RA | +| Monitor the proper functioning of virtual devices (utilities) in support of Platform as a Service | I | RA | +| Monitor physical and virtual resource performance | I | RA | +| Monitor service performance | RA | I | +| Process and pay for alarms from managed devices in the Public Cloud Analytics infrastructure | I | RA | +| Maintain logs generated by Public Cloud Analytics services | RA | RA | +| Keep logs of the Service hosted on Public Cloud Analytics | RA | + +##### **3.1.4. Storage** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Managing content hosted on Public Cloud Analytics services | RA | I | +| Ensuring data continuity and sustainability | RA | | +| Perform storage and backup device maintenance | | RA | +| Create, modify, control, restore, delete internal backup jobs | I | RA | + +##### **3.1.5. Connectivity** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Operate automatic network management systems (architecture, implementation, software and hardware maintenance for deployed public and private networks) | I | RA | +| Manage IP addressing plan | RA | | + +##### **3.1.6. Management** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Ensuring the security of management infrastructures (API, Control Panel) | I | RA | +| Ensure the security of the operating systems and software installed on the services | I | RA | +| Managing the physical security of equipment and infrastructures hosted at OVHcloud | I | RA | +| Maintain Public Cloud Analytics services and their extensions | C | RA | + +##### **3.1.7. Business continuity** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage automatic management systems for the infrastructure provided | I | RA | +| Maintain a business continuity and disaster recovery plan for hosted services | RA | I | + +#### 3.2. Event management + +##### **3.2.1. Incidents** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Intervening with Public Cloud Analytics managed elements | | RA | + +##### **3.2.2. Changes** + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Comply with the Public Cloud Enterprise Lifecycle Policy | RA | | +| Deploy patches, update software and information systems hosted in Public Cloud Analytics | CI | RA | +| Confirm the customer's request to change the hardware or software for the Analytics service | A | R | +| Deploy patches, update and configure the information system using Public Cloud Analytics | RA | | +| Perform preventive interventions on managed elements of the Public Cloud Analytics | I | AR | + +### 4. Reverting + +#### 4.1. Reversibility model + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Schedule reversibility operations | RA | I | +| Choose fallback infrastructures | RA | + +#### 4.2. Data recovery + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Manage reversibility operations | RA | I | +| Migrate/transfer data | RA | + +### 5. End of service + +#### 5.1. Destroying configurations + +| **Activity** | **Customer** | **OVHcloud** | +| --- | --- | --- | +| Delete Public Cloud project services | RA | I | + +## Go further + +Visit our dedicated Discord channel: . 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](/links/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 . diff --git a/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/meta.yaml b/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/meta.yaml new file mode 100644 index 00000000000..7b82ad2c1e3 --- /dev/null +++ b/pages/public_cloud/data_analytics/analytics/information_06_shared_responsibility/meta.yaml @@ -0,0 +1,3 @@ +id: f325100d-58d5-4cf7-a9da-690c8c095c2f +full_slug: data-analytics-responsibility-model +reference_category: data-analytics-general-information \ No newline at end of file diff --git a/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel/meta.yaml b/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel/meta.yaml index b2402dacfb2..90ddf2f57fb 100755 --- a/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel/meta.yaml +++ b/pages/public_cloud/public_cloud_databases/databases_01_order_control_panel/meta.yaml @@ -2,4 +2,4 @@ id: c8c6cbfb-1855-4efb-8ff6-b865a4959ac0 full_slug: public-cloud-databases-getting-started engine: all section: onboarding -reference_category: public-cloud-databases-cassandra-guides \ No newline at end of file +reference_category: public-cloud-databases-common-getting-started \ No newline at end of file diff --git a/pages/public_cloud/public_cloud_databases/databases_02_order_api/meta.yaml b/pages/public_cloud/public_cloud_databases/databases_02_order_api/meta.yaml index 17e4aa633be..66ee7533914 100755 --- a/pages/public_cloud/public_cloud_databases/databases_02_order_api/meta.yaml +++ b/pages/public_cloud/public_cloud_databases/databases_02_order_api/meta.yaml @@ -1,3 +1,3 @@ id: 0aec99c6-5879-48f9-8280-cd1e76a37838 full_slug: public-cloud-databases-order-api -reference_category: public-cloud-databases-cassandra-guides \ No newline at end of file +reference_category: public-cloud-databases-common-getting-started \ No newline at end of file diff --git a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/meta.yaml b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/meta.yaml index ec5a72b57b6..204bf9e5b84 100644 --- a/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/meta.yaml +++ b/pages/public_cloud/public_cloud_databases/databases_03_advanced_configuration/meta.yaml @@ -2,4 +2,4 @@ id: dbbac3da-b325-431e-bae8-857eb6f41e13 full_slug: public-cloud-databases-advanced-configuration engine: all section: settings -reference_category: public-cloud-databases-cassandra-guides \ No newline at end of file +reference_category: public-cloud-databases-common-configuration \ No newline at end of file diff --git a/pages/public_cloud/public_cloud_databases/databases_04_troubleshooting/meta.yaml b/pages/public_cloud/public_cloud_databases/databases_04_troubleshooting/meta.yaml index 26fe9953bd8..43760af4357 100755 --- a/pages/public_cloud/public_cloud_databases/databases_04_troubleshooting/meta.yaml +++ b/pages/public_cloud/public_cloud_databases/databases_04_troubleshooting/meta.yaml @@ -2,4 +2,4 @@ id: c7197d7c-ef81-419b-804d-6edd56e6408f full_slug: public-cloud-databases-troubleshooting engine: all section: dashboard -reference_category: public-cloud-databases-general-guides \ No newline at end of file +reference_category: public-cloud-databases-troubleshooting \ No newline at end of file diff --git a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/meta.yaml b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/meta.yaml index 4957ae9028e..83b7dd8f137 100755 --- a/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/meta.yaml +++ b/pages/public_cloud/public_cloud_databases/databases_05_automated_backups/meta.yaml @@ -2,4 +2,4 @@ id: ce10baef-1c91-4dfc-b586-60dfedfba09b full_slug: public-cloud-databases-backups engine: all section: backups -reference_category: public-cloud-databases-general-guides \ No newline at end of file +reference_category: public-cloud-databases-common-key-concepts \ No newline at end of file diff --git a/pages/public_cloud/public_cloud_databases/databases_06_restore_backup/meta.yaml b/pages/public_cloud/public_cloud_databases/databases_06_restore_backup/meta.yaml index 83077c81418..751dd0bdf9d 100755 --- a/pages/public_cloud/public_cloud_databases/databases_06_restore_backup/meta.yaml +++ b/pages/public_cloud/public_cloud_databases/databases_06_restore_backup/meta.yaml @@ -2,4 +2,4 @@ id: f74be24d-7854-4986-9ff6-12b624b79427 full_slug: public-cloud-databases-restore-backup engine: all section: backups -reference_category: public-cloud-databases-general-guides \ No newline at end of file +reference_category: public-cloud-databases-common-configuration \ No newline at end of file diff --git a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/meta.yaml b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/meta.yaml index f15a8b0cc66..671b72b6489 100644 --- a/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/meta.yaml +++ b/pages/public_cloud/public_cloud_databases/databases_07_cross_service_integration/meta.yaml @@ -2,4 +2,4 @@ id: 23389a5a-3ce4-4c21-a932-befe9e66eb1f full_slug: public-cloud-databases-cross-service-integration engine: all section: integrations -reference_category: public-cloud-databases-general-guides \ No newline at end of file +reference_category: public-cloud-databases-common-configuration \ No newline at end of file diff --git a/pages/public_cloud/public_cloud_databases/databases_08_vrack/meta.yaml b/pages/public_cloud/public_cloud_databases/databases_08_vrack/meta.yaml index beec9b39484..3d544d3b5a0 100755 --- a/pages/public_cloud/public_cloud_databases/databases_08_vrack/meta.yaml +++ b/pages/public_cloud/public_cloud_databases/databases_08_vrack/meta.yaml @@ -2,4 +2,4 @@ id: 85e41673-3cb7-46ca-86b0-47103a6147d2 full_slug: public-cloud-databases-configure-vrack engine: all section: settings -reference_category: public-cloud-databases-general-guides \ No newline at end of file +reference_category: public-cloud-databases-common-configuration \ No newline at end of file diff --git a/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/meta.yaml b/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/meta.yaml index 98561cddfe6..9a256652008 100755 --- a/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/meta.yaml +++ b/pages/public_cloud/public_cloud_databases/databases_09_order_terraform/meta.yaml @@ -1,3 +1,3 @@ id: 47d1eb38-6557-4cfb-8c96-98eb6a31d33e full_slug: public-cloud-databases-order-terraform -reference_category: public-cloud-databases-general-guides \ No newline at end of file +reference_category: public-cloud-databases-common-getting-started \ No newline at end of file diff --git a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/meta.yaml b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/meta.yaml index 569f8bc1ed9..229bdc4c7c2 100644 --- a/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/meta.yaml +++ b/pages/public_cloud/public_cloud_databases/databases_10_full_disk_handling/meta.yaml @@ -1,3 +1,3 @@ id: 9a73a2be-30b7-4c4c-8c53-5f6f6fb6838c full_slug: public-cloud-databases-handling-disk-full -reference_category: public-cloud-databases-general-guides \ No newline at end of file +reference_category: public-cloud-databases-troubleshooting \ No newline at end of file diff --git a/pages/public_cloud/public_cloud_databases/databases_11_resize_your_cluster_storage/meta.yaml b/pages/public_cloud/public_cloud_databases/databases_11_resize_your_cluster_storage/meta.yaml index 244a4f85fc6..6216ddc5d8a 100644 --- a/pages/public_cloud/public_cloud_databases/databases_11_resize_your_cluster_storage/meta.yaml +++ b/pages/public_cloud/public_cloud_databases/databases_11_resize_your_cluster_storage/meta.yaml @@ -1,3 +1,3 @@ id: f6b017f8-17ef-47ed-b5af-a51ad0b23844 full_slug: public-cloud-databases-resize-cluster-storage -reference_category: public-cloud-databases-general-guides \ No newline at end of file +reference_category: public-cloud-databases-common-configuration \ No newline at end of file diff --git a/pages/public_cloud/public_cloud_databases/databases_12_operator/meta.yaml b/pages/public_cloud/public_cloud_databases/databases_12_operator/meta.yaml index 96f53511896..eb36ba2c99a 100644 --- a/pages/public_cloud/public_cloud_databases/databases_12_operator/meta.yaml +++ b/pages/public_cloud/public_cloud_databases/databases_12_operator/meta.yaml @@ -1,3 +1,3 @@ id: eb06c906-ff8a-4a5b-a10b-1b06ac2be771 full_slug: public-cloud-databases-database-operator -reference_category: public-cloud-databases-general-guides \ No newline at end of file +reference_category: public-cloud-databases-common-configuration \ No newline at end of file diff --git a/pages/public_cloud/public_cloud_databases/databases_13_update_your_cluster_flavor/meta.yaml b/pages/public_cloud/public_cloud_databases/databases_13_update_your_cluster_flavor/meta.yaml index cba9bc858d5..138f0ea03de 100644 --- a/pages/public_cloud/public_cloud_databases/databases_13_update_your_cluster_flavor/meta.yaml +++ b/pages/public_cloud/public_cloud_databases/databases_13_update_your_cluster_flavor/meta.yaml @@ -1,3 +1,3 @@ id: 9edf3314-206b-4976-ad97-570c275aab6f full_slug: public-cloud-databases-update-cluster-flavor -reference_category: public-cloud-databases-general-guides \ No newline at end of file +reference_category: public-cloud-databases-common-configuration \ No newline at end of file diff --git a/pages/public_cloud/public_cloud_databases/databases_14_upgrade_your_cluster_plan/meta.yaml b/pages/public_cloud/public_cloud_databases/databases_14_upgrade_your_cluster_plan/meta.yaml index c7dee2ba0e8..b706aaa681e 100644 --- a/pages/public_cloud/public_cloud_databases/databases_14_upgrade_your_cluster_plan/meta.yaml +++ b/pages/public_cloud/public_cloud_databases/databases_14_upgrade_your_cluster_plan/meta.yaml @@ -1,3 +1,3 @@ id: 325eb89c-c933-44c6-83c6-8f4f54e680c9 full_slug: public-cloud-databases-update-cluster-plan -reference_category: public-cloud-databases-general-guides \ No newline at end of file +reference_category: public-cloud-databases-common-configuration \ No newline at end of file diff --git a/pages/public_cloud/public_cloud_databases/databases_15_maintenances/meta.yaml b/pages/public_cloud/public_cloud_databases/databases_15_maintenances/meta.yaml index cf554acabba..1e658dd92d0 100644 --- a/pages/public_cloud/public_cloud_databases/databases_15_maintenances/meta.yaml +++ b/pages/public_cloud/public_cloud_databases/databases_15_maintenances/meta.yaml @@ -2,4 +2,4 @@ id: 60467c92-8af6-4721-b72c-9f4917c05b1d full_slug: public-cloud-databases-maintenance engine: all section: settings -reference_category: public-cloud-databases-general-information \ No newline at end of file +reference_category: public-cloud-databases-common-configuration \ No newline at end of file diff --git a/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer/meta.yaml b/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer/meta.yaml index 07b1a9ae85c..802b7ca1b14 100644 --- a/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer/meta.yaml +++ b/pages/public_cloud/public_cloud_databases/databases_16_logs_to_customer/meta.yaml @@ -2,4 +2,4 @@ id: 86be8acc-e6bf-4144-843d-71da48c71e93 full_slug: public-cloud-databases-logs-to-customers engine: all section: logs -reference_category: public-cloud-databases-general-guides \ No newline at end of file +reference_category: public-cloud-databases-common-configuration \ No newline at end of file diff --git a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/meta.yaml b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/meta.yaml index 572f1bbf5ef..b5b78824407 100644 --- a/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/meta.yaml +++ b/pages/public_cloud/public_cloud_databases/databases_17_metrics_via_prometheus/meta.yaml @@ -1,3 +1,3 @@ id: 93f0972f-f0ec-40a3-bc8d-dc6e07263105 full_slug: public-cloud-databases-service-metrics-with-prometheus -reference_category: public-cloud-databases-general-guides +reference_category: public-cloud-databases-common-configuration diff --git a/pages/public_cloud/public_cloud_databases/databases_18_regions_comparison/meta.yaml b/pages/public_cloud/public_cloud_databases/databases_18_regions_comparison/meta.yaml index f95743e8d00..6df149d8d3d 100644 --- a/pages/public_cloud/public_cloud_databases/databases_18_regions_comparison/meta.yaml +++ b/pages/public_cloud/public_cloud_databases/databases_18_regions_comparison/meta.yaml @@ -1,3 +1,3 @@ id: 7f1ac99b-28a7-464f-ad68-05f5d83a4a61 full_slug: public-cloud-databases-regions-comparison -reference_category: public-cloud-databases-general-information \ No newline at end of file +reference_category: public-cloud-databases-common-key-concepts \ No newline at end of file diff --git a/pages/public_cloud/public_cloud_databases/databases_19_deletion_protection/meta.yaml b/pages/public_cloud/public_cloud_databases/databases_19_deletion_protection/meta.yaml index 5526f1fa8ba..aa9cd892163 100644 --- a/pages/public_cloud/public_cloud_databases/databases_19_deletion_protection/meta.yaml +++ b/pages/public_cloud/public_cloud_databases/databases_19_deletion_protection/meta.yaml @@ -1,4 +1,4 @@ id: 880a4ef7-fa8c-42b3-bd30-f4bd6c49be3d full_slug: public-cloud-databases-deletion-protection engine: all -reference_category: public-cloud-databases-general-guides +reference_category: public-cloud-databases-common-configuration diff --git a/pages/public_cloud/public_cloud_databases/databases_19_migrate_from_1AZ_to_3AZ/meta.yaml b/pages/public_cloud/public_cloud_databases/databases_19_migrate_from_1AZ_to_3AZ/meta.yaml index 897d03a9ac1..91fbbfe7c9d 100644 --- a/pages/public_cloud/public_cloud_databases/databases_19_migrate_from_1AZ_to_3AZ/meta.yaml +++ b/pages/public_cloud/public_cloud_databases/databases_19_migrate_from_1AZ_to_3AZ/meta.yaml @@ -1,3 +1,3 @@ id: 44005693-bc5e-4fb9-9117-c9245596ef89 full_slug: public-cloud-databases-migrate-1az-to-3az -reference_category: public-cloud-databases-general-guides \ No newline at end of file +reference_category: public-cloud-databases-common-migration \ No newline at end of file diff --git a/pages/public_cloud/public_cloud_databases/databases_20_migrate_from_gen2_to_gen3/meta.yaml b/pages/public_cloud/public_cloud_databases/databases_20_migrate_from_gen2_to_gen3/meta.yaml index 7b16f6a1808..080772889c6 100644 --- a/pages/public_cloud/public_cloud_databases/databases_20_migrate_from_gen2_to_gen3/meta.yaml +++ b/pages/public_cloud/public_cloud_databases/databases_20_migrate_from_gen2_to_gen3/meta.yaml @@ -1,3 +1,3 @@ id: 096e6a78-d5f7-4650-a16b-fdfa4aa5e803 full_slug: public-cloud-databases-migrate-gen2-to-gen3 -reference_category: public-cloud-databases-general-guides \ No newline at end of file +reference_category: public-cloud-databases-common-migration \ No newline at end of file diff --git a/pages/public_cloud/public_cloud_databases/databases_20_move_to_cloud/meta.yaml b/pages/public_cloud/public_cloud_databases/databases_20_move_to_cloud/meta.yaml index fdc752f0858..bbf9f18b6fc 100644 --- a/pages/public_cloud/public_cloud_databases/databases_20_move_to_cloud/meta.yaml +++ b/pages/public_cloud/public_cloud_databases/databases_20_move_to_cloud/meta.yaml @@ -1,2 +1,3 @@ id: b759edb2-8985-403b-81ad-7f9718270f7e -full_slug: public-cloud-databases-move-to-cloud \ No newline at end of file +full_slug: public-cloud-databases-move-to-cloud +reference_category: public-cloud-databases-common-migration \ No newline at end of file diff --git a/pages/public_cloud/public_cloud_databases/information_01_security_overview/meta.yaml b/pages/public_cloud/public_cloud_databases/information_01_security_overview/meta.yaml index 81f020557a8..a6e7d26c4bf 100755 --- a/pages/public_cloud/public_cloud_databases/information_01_security_overview/meta.yaml +++ b/pages/public_cloud/public_cloud_databases/information_01_security_overview/meta.yaml @@ -2,4 +2,4 @@ id: 5d63e515-9ca0-454a-803f-3dd61be5bf94 full_slug: public-cloud-databases-concepts-security-overview engine: all section: dashboard -reference_category: public-cloud-databases-general-information \ No newline at end of file +reference_category: public-cloud-databases-common-security \ No newline at end of file diff --git a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/meta.yaml b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/meta.yaml index d905f45222c..c1d4a0f66be 100755 --- a/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/meta.yaml +++ b/pages/public_cloud/public_cloud_databases/information_02_lifecycle_policy/meta.yaml @@ -2,4 +2,4 @@ id: ac56f39e-b948-421a-a76e-f739de6585f6 full_slug: public-cloud-databases-lifecycle-policy engine: all section: dashboard -reference_category: public-cloud-databases-general-information \ No newline at end of file +reference_category: public-cloud-databases-common-key-concepts \ No newline at end of file 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 4e47d2a6a86..d8f84655325 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 @@ -1,7 +1,7 @@ --- title: Public Cloud Databases - Responsibility model excerpt: 'Shared responsibilities between OVHcloud and the customer' -updated: 2021-09-28 +updated: 2025-11-04 --- 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. @@ -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, Valkey, Kafka, or Cassandra cluster. +For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Valkey 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 4e47d2a6a86..d8f84655325 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 @@ -1,7 +1,7 @@ --- title: Public Cloud Databases - Responsibility model excerpt: 'Shared responsibilities between OVHcloud and the customer' -updated: 2021-09-28 +updated: 2025-11-04 --- 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. @@ -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, Valkey, Kafka, or Cassandra cluster. +For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Valkey 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 4e47d2a6a86..d8f84655325 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 @@ -1,7 +1,7 @@ --- title: Public Cloud Databases - Responsibility model excerpt: 'Shared responsibilities between OVHcloud and the customer' -updated: 2021-09-28 +updated: 2025-11-04 --- 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. @@ -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, Valkey, Kafka, or Cassandra cluster. +For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Valkey 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 4e47d2a6a86..d8f84655325 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 @@ -1,7 +1,7 @@ --- title: Public Cloud Databases - Responsibility model excerpt: 'Shared responsibilities between OVHcloud and the customer' -updated: 2021-09-28 +updated: 2025-11-04 --- 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. @@ -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, Valkey, Kafka, or Cassandra cluster. +For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Valkey 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 4e47d2a6a86..d8f84655325 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 @@ -1,7 +1,7 @@ --- title: Public Cloud Databases - Responsibility model excerpt: 'Shared responsibilities between OVHcloud and the customer' -updated: 2021-09-28 +updated: 2025-11-04 --- 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. @@ -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, Valkey, Kafka, or Cassandra cluster. +For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Valkey 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 4e47d2a6a86..d8f84655325 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 @@ -1,7 +1,7 @@ --- title: Public Cloud Databases - Responsibility model excerpt: 'Shared responsibilities between OVHcloud and the customer' -updated: 2021-09-28 +updated: 2025-11-04 --- 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. @@ -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, Valkey, Kafka, or Cassandra cluster. +For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Valkey 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 4e47d2a6a86..d8f84655325 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 @@ -1,7 +1,7 @@ --- title: Public Cloud Databases - Responsibility model excerpt: 'Shared responsibilities between OVHcloud and the customer' -updated: 2021-09-28 +updated: 2025-11-04 --- 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. @@ -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, Valkey, Kafka, or Cassandra cluster. +For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Valkey 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 4e47d2a6a86..d8f84655325 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 @@ -1,7 +1,7 @@ --- title: Public Cloud Databases - Responsibility model excerpt: 'Shared responsibilities between OVHcloud and the customer' -updated: 2021-09-28 +updated: 2025-11-04 --- 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. @@ -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, Valkey, Kafka, or Cassandra cluster. +For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Valkey 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 4e47d2a6a86..d8f84655325 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 @@ -1,7 +1,7 @@ --- title: Public Cloud Databases - Responsibility model excerpt: 'Shared responsibilities between OVHcloud and the customer' -updated: 2021-09-28 +updated: 2025-11-04 --- 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. @@ -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, Valkey, Kafka, or Cassandra cluster. +For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Valkey 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 4e47d2a6a86..d8f84655325 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 @@ -1,7 +1,7 @@ --- title: Public Cloud Databases - Responsibility model excerpt: 'Shared responsibilities between OVHcloud and the customer' -updated: 2021-09-28 +updated: 2025-11-04 --- 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. @@ -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, Valkey, Kafka, or Cassandra cluster. +For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Valkey 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 8f66ee561c0..f5bcdc01fc3 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 @@ -1,7 +1,7 @@ --- title: Public Cloud Databases - Partage des responsabilités (EN) excerpt: 'Shared responsibilities between OVHcloud and the customer' -updated: 2021-09-28 +updated: 2025-11-04 --- 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. @@ -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, Valkey, Kafka, or Cassandra cluster. +For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Valkey 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 8f66ee561c0..f5bcdc01fc3 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 @@ -1,7 +1,7 @@ --- title: Public Cloud Databases - Partage des responsabilités (EN) excerpt: 'Shared responsibilities between OVHcloud and the customer' -updated: 2021-09-28 +updated: 2025-11-04 --- 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. @@ -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, Valkey, Kafka, or Cassandra cluster. +For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Valkey 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 4e47d2a6a86..d8f84655325 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 @@ -1,7 +1,7 @@ --- title: Public Cloud Databases - Responsibility model excerpt: 'Shared responsibilities between OVHcloud and the customer' -updated: 2021-09-28 +updated: 2025-11-04 --- 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. @@ -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, Valkey, Kafka, or Cassandra cluster. +For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Valkey 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 4e47d2a6a86..d8f84655325 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 @@ -1,7 +1,7 @@ --- title: Public Cloud Databases - Responsibility model excerpt: 'Shared responsibilities between OVHcloud and the customer' -updated: 2021-09-28 +updated: 2025-11-04 --- 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. @@ -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, Valkey, Kafka, or Cassandra cluster. +For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Valkey 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 4e47d2a6a86..d8f84655325 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 @@ -1,7 +1,7 @@ --- title: Public Cloud Databases - Responsibility model excerpt: 'Shared responsibilities between OVHcloud and the customer' -updated: 2021-09-28 +updated: 2025-11-04 --- 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. @@ -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, Valkey, Kafka, or Cassandra cluster. +For your information, a **Service** is considered a Public Cloud Databases service such as a MySQL, PostgreSQL, MongoDB, Valkey or Cassandra cluster. ### 1. Before subscription diff --git a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/meta.yaml b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/meta.yaml index d028e72c398..2cf342cc459 100755 --- a/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/meta.yaml +++ b/pages/public_cloud/public_cloud_databases/information_03_shared_responsibility/meta.yaml @@ -1,3 +1,3 @@ id: 39319d01-daeb-4eed-8b36-3ef9498ad1bf full_slug: public-cloud-databases-responsibility-model -reference_category: public-cloud-databases-general-information \ No newline at end of file +reference_category: public-cloud-databases-common-security \ No newline at end of file diff --git a/pages/public_cloud/public_cloud_databases/information_04_faq/meta.yaml b/pages/public_cloud/public_cloud_databases/information_04_faq/meta.yaml index f108387a9e1..368220dc3f9 100755 --- a/pages/public_cloud/public_cloud_databases/information_04_faq/meta.yaml +++ b/pages/public_cloud/public_cloud_databases/information_04_faq/meta.yaml @@ -2,4 +2,4 @@ id: a8fd3cd7-01cb-4b19-9882-c85ec86ba49d full_slug: public-cloud-databases-faq engine: all section: dashboard -reference_category: public-cloud-databases-general-information \ No newline at end of file +reference_category: public-cloud-databases-common-key-concepts \ No newline at end of file diff --git a/pages/public_cloud/public_cloud_databases/information_05_capabilities/meta.yaml b/pages/public_cloud/public_cloud_databases/information_05_capabilities/meta.yaml index 2051beb731f..1af606f6355 100755 --- a/pages/public_cloud/public_cloud_databases/information_05_capabilities/meta.yaml +++ b/pages/public_cloud/public_cloud_databases/information_05_capabilities/meta.yaml @@ -1,3 +1,3 @@ id: 31f1eaf8-d85a-4f28-9f98-56e24184781c full_slug: public-cloud-databases-capabilities -reference_category: public-cloud-databases-general-information \ No newline at end of file +reference_category: public-cloud-databases-common-key-concepts \ No newline at end of file