diff --git a/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.de-de.md b/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.de-de.md
index 01498adcc1b..a91eebcbf37 100644
--- a/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.de-de.md
+++ b/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.de-de.md
@@ -67,7 +67,7 @@ OVHcloud console GUI (also called "Control Panel" or "Manager") hides some backg
 | --- | --- | --- |
 | Block Storage  | openstack | [blockstorage_volume_v3](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/blockstorage_volume_v3)|
 | Object Storage (Swift) | openstack | [objectstorage_object_v1](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_object_v1) |
-| Object Storage | Hashicorp aws | [aws_s3_bucket](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket)|
+| Object Storage | ovh | [cloud_project_storage](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage)|
 | Object Storage users | ovh | [ovh_cloud_project_user](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_user) with *objectstore_operator* role|
 | Cloud Archive | openstack | [objectstorage_object_v1](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_object_v1) with [storage_policy](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_container_v1#storage_policy) set to “PCA” in order to create an “archive” swift container |
 | Cold Archive | Hashicorp aws | [aws_s3_bucket](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket)|
diff --git a/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.en-asia.md b/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.en-asia.md
index 78775f5fd1b..6dd62508caf 100644
--- a/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.en-asia.md
+++ b/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.en-asia.md
@@ -67,7 +67,7 @@ OVHcloud console GUI (also called "Control Panel" or "Manager") hides some backg
 | --- | --- | --- |
 | Block Storage  | openstack | [blockstorage_volume_v3](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/blockstorage_volume_v3)|
 | Object Storage (Swift) | openstack | [objectstorage_object_v1](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_object_v1) |
-| Object Storage | Hashicorp aws | [aws_s3_bucket](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket)|
+| Object Storage | ovh | [cloud_project_storage](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage)|
 | Object Storage users | ovh | [ovh_cloud_project_user](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_user) with *objectstore_operator* role|
 | Cloud Archive | openstack | [objectstorage_object_v1](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_object_v1) with [storage_policy](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_container_v1#storage_policy) set to “PCA” in order to create an “archive” swift container |
 | Cold Archive | Hashicorp aws | [aws_s3_bucket](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket)|
diff --git a/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.en-au.md b/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.en-au.md
index 3e163c13175..25febf65810 100644
--- a/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.en-au.md
+++ b/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.en-au.md
@@ -67,7 +67,7 @@ OVHcloud console GUI (also called "Control Panel" or "Manager") hides some backg
 | --- | --- | --- |
 | Block Storage  | openstack | [blockstorage_volume_v3](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/blockstorage_volume_v3)|
 | Object Storage (Swift) | openstack | [objectstorage_object_v1](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_object_v1) |
-| Object Storage | Hashicorp aws | [aws_s3_bucket](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket)|
+| Object Storage | ovh | [cloud_project_storage](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage)|
 | Object Storage users | ovh | [ovh_cloud_project_user](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_user) with *objectstore_operator* role|
 | Cloud Archive | openstack | [objectstorage_object_v1](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_object_v1) with [storage_policy](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_container_v1#storage_policy) set to “PCA” in order to create an “archive” swift container |
 | Cold Archive | Hashicorp aws | [aws_s3_bucket](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket)|
diff --git a/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.en-ca.md b/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.en-ca.md
index 05890c3c59d..feefcfbcf38 100644
--- a/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.en-ca.md
+++ b/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.en-ca.md
@@ -67,7 +67,7 @@ OVHcloud console GUI (also called "Control Panel" or "Manager") hides some backg
 | --- | --- | --- |
 | Block Storage  | openstack | [blockstorage_volume_v3](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/blockstorage_volume_v3)|
 | Object Storage (Swift) | openstack | [objectstorage_object_v1](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_object_v1) |
-| Object Storage | Hashicorp aws | [aws_s3_bucket](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket)|
+| Object Storage | ovh | [cloud_project_storage](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage)|
 | Object Storage users | ovh | [ovh_cloud_project_user](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_user) with *objectstore_operator* role|
 | Cloud Archive | openstack | [objectstorage_object_v1](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_object_v1) with [storage_policy](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_container_v1#storage_policy) set to “PCA” in order to create an “archive” swift container |
 | Cold Archive | Hashicorp aws | [aws_s3_bucket](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket)|
diff --git a/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.en-gb.md b/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.en-gb.md
index 02dffbacc3f..470bb897330 100644
--- a/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.en-gb.md
+++ b/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.en-gb.md
@@ -67,7 +67,7 @@ OVHcloud console GUI (also called "Control Panel" or "Manager") hides some backg
 | --- | --- | --- |
 | Block Storage  | openstack | [blockstorage_volume_v3](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/blockstorage_volume_v3)|
 | Object Storage (Swift) | openstack | [objectstorage_object_v1](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_object_v1) |
-| Object Storage | Hashicorp aws | [aws_s3_bucket](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket)|
+| Object Storage | ovh | [cloud_project_storage](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage)|
 | Object Storage users | ovh | [ovh_cloud_project_user](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_user) with *objectstore_operator* role|
 | Cloud Archive | openstack | [objectstorage_object_v1](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_object_v1) with [storage_policy](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_container_v1#storage_policy) set to “PCA” in order to create an “archive” swift container |
 | Cold Archive | Hashicorp aws | [aws_s3_bucket](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket)|
diff --git a/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.en-ie.md b/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.en-ie.md
index 2ed5928afb8..10949d3dfff 100644
--- a/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.en-ie.md
+++ b/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.en-ie.md
@@ -67,7 +67,7 @@ OVHcloud console GUI (also called "Control Panel" or "Manager") hides some backg
 | --- | --- | --- |
 | Block Storage  | openstack | [blockstorage_volume_v3](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/blockstorage_volume_v3)|
 | Object Storage (Swift) | openstack | [objectstorage_object_v1](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_object_v1) |
-| Object Storage | Hashicorp aws | [aws_s3_bucket](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket)|
+| Object Storage | ovh | [cloud_project_storage](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage)|
 | Object Storage users | ovh | [ovh_cloud_project_user](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_user) with *objectstore_operator* role|
 | Cloud Archive | openstack | [objectstorage_object_v1](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_object_v1) with [storage_policy](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_container_v1#storage_policy) set to “PCA” in order to create an “archive” swift container |
 | Cold Archive | Hashicorp aws | [aws_s3_bucket](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket)|
diff --git a/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.en-sg.md b/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.en-sg.md
index e31a97be7eb..9d9df612dc1 100644
--- a/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.en-sg.md
+++ b/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.en-sg.md
@@ -67,7 +67,7 @@ OVHcloud console GUI (also called "Control Panel" or "Manager") hides some backg
 | --- | --- | --- |
 | Block Storage  | openstack | [blockstorage_volume_v3](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/blockstorage_volume_v3)|
 | Object Storage (Swift) | openstack | [objectstorage_object_v1](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_object_v1) |
-| Object Storage | Hashicorp aws | [aws_s3_bucket](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket)|
+| Object Storage | ovh | [cloud_project_storage](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage)|
 | Object Storage users | ovh | [ovh_cloud_project_user](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_user) with *objectstore_operator* role|
 | Cloud Archive | openstack | [objectstorage_object_v1](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_object_v1) with [storage_policy](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_container_v1#storage_policy) set to “PCA” in order to create an “archive” swift container |
 | Cold Archive | Hashicorp aws | [aws_s3_bucket](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket)|
diff --git a/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.en-us.md b/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.en-us.md
index 32c7c2ce935..0b29a6db968 100644
--- a/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.en-us.md
+++ b/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.en-us.md
@@ -67,7 +67,7 @@ OVHcloud console GUI (also called "Control Panel" or "Manager") hides some backg
 | --- | --- | --- |
 | Block Storage  | openstack | [blockstorage_volume_v3](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/blockstorage_volume_v3)|
 | Object Storage (Swift) | openstack | [objectstorage_object_v1](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_object_v1) |
-| Object Storage | Hashicorp aws | [aws_s3_bucket](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket)|
+| Object Storage | ovh | [cloud_project_storage](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage)|
 | Object Storage users | ovh | [ovh_cloud_project_user](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_user) with *objectstore_operator* role|
 | Cloud Archive | openstack | [objectstorage_object_v1](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_object_v1) with [storage_policy](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_container_v1#storage_policy) set to “PCA” in order to create an “archive” swift container |
 | Cold Archive | Hashicorp aws | [aws_s3_bucket](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket)|
diff --git a/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.es-es.md b/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.es-es.md
index 715d4e53cc5..85f63f716ce 100644
--- a/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.es-es.md
+++ b/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.es-es.md
@@ -67,7 +67,7 @@ OVHcloud console GUI (also called "Control Panel" or "Manager") hides some backg
 | --- | --- | --- |
 | Block Storage  | openstack | [blockstorage_volume_v3](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/blockstorage_volume_v3)|
 | Object Storage (Swift) | openstack | [objectstorage_object_v1](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_object_v1) |
-| Object Storage | Hashicorp aws | [aws_s3_bucket](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket)|
+| Object Storage | ovh | [cloud_project_storage](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage)|
 | Object Storage users | ovh | [ovh_cloud_project_user](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_user) with *objectstore_operator* role|
 | Cloud Archive | openstack | [objectstorage_object_v1](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_object_v1) with [storage_policy](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_container_v1#storage_policy) set to “PCA” in order to create an “archive” swift container |
 | Cold Archive | Hashicorp aws | [aws_s3_bucket](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket)|
diff --git a/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.es-us.md b/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.es-us.md
index 9cb8de1e991..8fd61dd7088 100644
--- a/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.es-us.md
+++ b/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.es-us.md
@@ -67,7 +67,7 @@ OVHcloud console GUI (also called "Control Panel" or "Manager") hides some backg
 | --- | --- | --- |
 | Block Storage  | openstack | [blockstorage_volume_v3](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/blockstorage_volume_v3)|
 | Object Storage (Swift) | openstack | [objectstorage_object_v1](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_object_v1) |
-| Object Storage | Hashicorp aws | [aws_s3_bucket](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket)|
+| Object Storage | ovh | [cloud_project_storage](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage)|
 | Object Storage users | ovh | [ovh_cloud_project_user](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_user) with *objectstore_operator* role|
 | Cloud Archive | openstack | [objectstorage_object_v1](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_object_v1) with [storage_policy](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_container_v1#storage_policy) set to “PCA” in order to create an “archive” swift container |
 | Cold Archive | Hashicorp aws | [aws_s3_bucket](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket)|
diff --git a/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.fr-ca.md b/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.fr-ca.md
index 6dcb0821df5..b74a364e982 100644
--- a/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.fr-ca.md
+++ b/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.fr-ca.md
@@ -67,7 +67,7 @@ OVHcloud console GUI (also called "Control Panel" or "Manager") hides some backg
 | --- | --- | --- |
 | Block Storage  | openstack | [blockstorage_volume_v3](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/blockstorage_volume_v3)|
 | Object Storage (Swift) | openstack | [objectstorage_object_v1](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_object_v1) |
-| Object Storage | Hashicorp aws | [aws_s3_bucket](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket)|
+| Object Storage | ovh | [cloud_project_storage](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage)|
 | Object Storage users | ovh | [ovh_cloud_project_user](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_user) with *objectstore_operator* role|
 | Cloud Archive | openstack | [objectstorage_object_v1](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_object_v1) with [storage_policy](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_container_v1#storage_policy) set to “PCA” in order to create an “archive” swift container |
 | Cold Archive | Hashicorp aws | [aws_s3_bucket](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket)|
diff --git a/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.fr-fr.md b/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.fr-fr.md
index 55f4702164f..2e9c9e8bca2 100644
--- a/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.fr-fr.md
+++ b/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.fr-fr.md
@@ -67,7 +67,7 @@ OVHcloud console GUI (also called "Control Panel" or "Manager") hides some backg
 | --- | --- | --- |
 | Block Storage  | openstack | [blockstorage_volume_v3](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/blockstorage_volume_v3)|
 | Object Storage (Swift) | openstack | [objectstorage_object_v1](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_object_v1) |
-| Object Storage | Hashicorp aws | [aws_s3_bucket](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket)|
+| Object Storage | ovh | [cloud_project_storage](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage)|
 | Object Storage users | ovh | [ovh_cloud_project_user](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_user) with *objectstore_operator* role|
 | Cloud Archive | openstack | [objectstorage_object_v1](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_object_v1) with [storage_policy](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_container_v1#storage_policy) set to “PCA” in order to create an “archive” swift container |
 | Cold Archive | Hashicorp aws | [aws_s3_bucket](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket)|
diff --git a/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.it-it.md b/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.it-it.md
index d79f3922d66..9854cfbca76 100644
--- a/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.it-it.md
+++ b/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.it-it.md
@@ -67,7 +67,7 @@ OVHcloud console GUI (also called "Control Panel" or "Manager") hides some backg
 | --- | --- | --- |
 | Block Storage  | openstack | [blockstorage_volume_v3](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/blockstorage_volume_v3)|
 | Object Storage (Swift) | openstack | [objectstorage_object_v1](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_object_v1) |
-| Object Storage | Hashicorp aws | [aws_s3_bucket](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket)|
+| Object Storage | ovh | [cloud_project_storage](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage)|
 | Object Storage users | ovh | [ovh_cloud_project_user](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_user) with *objectstore_operator* role|
 | Cloud Archive | openstack | [objectstorage_object_v1](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_object_v1) with [storage_policy](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_container_v1#storage_policy) set to “PCA” in order to create an “archive” swift container |
 | Cold Archive | Hashicorp aws | [aws_s3_bucket](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket)|
diff --git a/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.pl-pl.md b/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.pl-pl.md
index 15751a67356..4ed362a23cf 100644
--- a/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.pl-pl.md
+++ b/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.pl-pl.md
@@ -67,7 +67,7 @@ OVHcloud console GUI (also called "Control Panel" or "Manager") hides some backg
 | --- | --- | --- |
 | Block Storage  | openstack | [blockstorage_volume_v3](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/blockstorage_volume_v3)|
 | Object Storage (Swift) | openstack | [objectstorage_object_v1](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_object_v1) |
-| Object Storage | Hashicorp aws | [aws_s3_bucket](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket)|
+| Object Storage | ovh | [cloud_project_storage](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage)|
 | Object Storage users | ovh | [ovh_cloud_project_user](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_user) with *objectstore_operator* role|
 | Cloud Archive | openstack | [objectstorage_object_v1](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_object_v1) with [storage_policy](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_container_v1#storage_policy) set to “PCA” in order to create an “archive” swift container |
 | Cold Archive | Hashicorp aws | [aws_s3_bucket](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket)|
diff --git a/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.pt-pt.md b/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.pt-pt.md
index f7c4afb45ab..9a35c41d71a 100644
--- a/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.pt-pt.md
+++ b/pages/manage_and_operate/terraform/terraform-at-ovhcloud/guide.pt-pt.md
@@ -67,7 +67,7 @@ OVHcloud console GUI (also called "Control Panel" or "Manager") hides some backg
 | --- | --- | --- |
 | Block Storage  | openstack | [blockstorage_volume_v3](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/blockstorage_volume_v3)|
 | Object Storage (Swift) | openstack | [objectstorage_object_v1](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_object_v1) |
-| Object Storage | Hashicorp aws | [aws_s3_bucket](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket)|
+| Object Storage | ovh | [cloud_project_storage](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage)|
 | Object Storage users | ovh | [ovh_cloud_project_user](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_user) with *objectstore_operator* role|
 | Cloud Archive | openstack | [objectstorage_object_v1](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_object_v1) with [storage_policy](https://registry.terraform.io/providers/terraform-provider-openstack/openstack/latest/docs/resources/objectstorage_container_v1#storage_policy) set to “PCA” in order to create an “archive” swift container |
 | Cold Archive | Hashicorp aws | [aws_s3_bucket](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket)|
diff --git a/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.de-de.md b/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.de-de.md
index 0bcf13d777d..da54e5a811b 100644
--- a/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.de-de.md
+++ b/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.de-de.md
@@ -1,7 +1,7 @@
 ---
 title: Object Storage - Erste Schritte mit Object Storage (EN)
 excerpt: This guide is designed to familiarise you with the management of your containers/objects
-updated: 2025-03-17
+updated: 2025-05-05
 ---
 
 <style>
@@ -42,6 +42,11 @@ This guide is designed to familiarise you with the management of your containers
 
 ## Instructions
 
+> [!primary]
+>
+> If you wish to use the OVHcloud Terraform provider, you can follow [this guide](/pages/storage_and_backup/object_storage/s3_terraform).
+>
+
 ### Preparation
 
 /// details | To use the AWS CLI
@@ -284,6 +289,7 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >> Congratulations, your bucket is created:
 >>
 >> ![Result](images/01-object-storage-bucket-listing.png)
+>>
 
 #### Uploading your files as objects in your bucket
 
@@ -428,23 +434,6 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >
 
 > [!tabs]
-> Via the OVHcloud Control Panel
->> **Deleting a bucket:**
->>
->> In the list of object storage containers, click on the `...`{.action} button on the containers line, then click `Delete`{.action}.
->>
->> ![Delete bucket](images/delete-bucket.png){.thumbnail}
->>
->> Click on `Confirm`{.action}.
->>
->> **Deleting objects:**
->>
->> Go to the relevant bucket and click on the `...`{.action} button on the object line, then click `Delete`{.action}.
->>
->> ![Delete file](images/delete-file.png){.thumbnail}
->>
->> Click on `Confirm`{.action}.
->>
 > Via AWS CLI
 >> /// details | **Via AWS s3**
 >>
@@ -516,6 +505,24 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >> > If your bucket has Object Lock enabled, you will not be able to permanently delete your objects. See our [documentation](/pages/storage_and_backup/object_storage/s3_managing_object_lock) to learn more about Object Lock.
 >> > If you use Object Lock in GOVERNANCE mode and have the permission to bypass GOVERNANCE mode, you will have to add the `--bypass-governance-retention` option to your delete commands.
 >> >
+>>
+> Via the OVHcloud Control Panel
+>> **Deleting a bucket:**
+>>
+>> In the list of object storage containers, click on the `...`{.action} button on the containers line, then click `Delete`{.action}.
+>>
+>> ![Delete bucket](images/delete-bucket.png){.thumbnail}
+>>
+>> Click on `Confirm`{.action}.
+>>
+>> **Deleting objects:**
+>>
+>> Go to the relevant bucket and click on the `...`{.action} button on the object line, then click `Delete`{.action}.
+>>
+>> ![Delete file](images/delete-file.png){.thumbnail}
+>>
+>> Click on `Confirm`{.action}.
+>>
 
 **Manage tags**
 
diff --git a/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.en-asia.md b/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.en-asia.md
index 568cb2d219a..f451ae99c28 100644
--- a/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.en-asia.md
+++ b/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.en-asia.md
@@ -1,7 +1,7 @@
 ---
 title: Object Storage - Getting started with Object Storage
 excerpt: This guide is designed to familiarise you with the management of your containers/objects
-updated: 2025-03-17
+updated: 2025-05-05
 ---
 
 <style>
@@ -42,6 +42,11 @@ This guide is designed to familiarise you with the management of your containers
 
 ## Instructions
 
+> [!primary]
+>
+> If you wish to use the OVHcloud Terraform provider, you can follow [this guide](/pages/storage_and_backup/object_storage/s3_terraform).
+>
+
 ### Preparation
 
 /// details | To use the AWS CLI
@@ -284,6 +289,7 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >> Congratulations, your bucket is created:
 >>
 >> ![Result](images/01-object-storage-bucket-listing.png)
+>>
 
 #### Uploading your files as objects in your bucket
 
@@ -428,23 +434,6 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >
 
 > [!tabs]
-> Via the OVHcloud Control Panel
->> **Deleting a bucket:**
->>
->> In the list of object storage containers, click on the `...`{.action} button on the containers line, then click `Delete`{.action}.
->>
->> ![Delete bucket](images/delete-bucket.png){.thumbnail}
->>
->> Click on `Confirm`{.action}.
->>
->> **Deleting objects:**
->>
->> Go to the relevant bucket and click on the `...`{.action} button on the object line, then click `Delete`{.action}.
->>
->> ![Delete file](images/delete-file.png){.thumbnail}
->>
->> Click on `Confirm`{.action}.
->>
 > Via AWS CLI
 >> /// details | **Via AWS s3**
 >>
@@ -516,6 +505,24 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >> > If your bucket has Object Lock enabled, you will not be able to permanently delete your objects. See our [documentation](/pages/storage_and_backup/object_storage/s3_managing_object_lock) to learn more about Object Lock.
 >> > If you use Object Lock in GOVERNANCE mode and have the permission to bypass GOVERNANCE mode, you will have to add the `--bypass-governance-retention` option to your delete commands.
 >> >
+>>
+> Via the OVHcloud Control Panel
+>> **Deleting a bucket:**
+>>
+>> In the list of object storage containers, click on the `...`{.action} button on the containers line, then click `Delete`{.action}.
+>>
+>> ![Delete bucket](images/delete-bucket.png){.thumbnail}
+>>
+>> Click on `Confirm`{.action}.
+>>
+>> **Deleting objects:**
+>>
+>> Go to the relevant bucket and click on the `...`{.action} button on the object line, then click `Delete`{.action}.
+>>
+>> ![Delete file](images/delete-file.png){.thumbnail}
+>>
+>> Click on `Confirm`{.action}.
+>>
 
 **Manage tags**
 
diff --git a/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.en-au.md b/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.en-au.md
index 568cb2d219a..f451ae99c28 100644
--- a/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.en-au.md
+++ b/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.en-au.md
@@ -1,7 +1,7 @@
 ---
 title: Object Storage - Getting started with Object Storage
 excerpt: This guide is designed to familiarise you with the management of your containers/objects
-updated: 2025-03-17
+updated: 2025-05-05
 ---
 
 <style>
@@ -42,6 +42,11 @@ This guide is designed to familiarise you with the management of your containers
 
 ## Instructions
 
+> [!primary]
+>
+> If you wish to use the OVHcloud Terraform provider, you can follow [this guide](/pages/storage_and_backup/object_storage/s3_terraform).
+>
+
 ### Preparation
 
 /// details | To use the AWS CLI
@@ -284,6 +289,7 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >> Congratulations, your bucket is created:
 >>
 >> ![Result](images/01-object-storage-bucket-listing.png)
+>>
 
 #### Uploading your files as objects in your bucket
 
@@ -428,23 +434,6 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >
 
 > [!tabs]
-> Via the OVHcloud Control Panel
->> **Deleting a bucket:**
->>
->> In the list of object storage containers, click on the `...`{.action} button on the containers line, then click `Delete`{.action}.
->>
->> ![Delete bucket](images/delete-bucket.png){.thumbnail}
->>
->> Click on `Confirm`{.action}.
->>
->> **Deleting objects:**
->>
->> Go to the relevant bucket and click on the `...`{.action} button on the object line, then click `Delete`{.action}.
->>
->> ![Delete file](images/delete-file.png){.thumbnail}
->>
->> Click on `Confirm`{.action}.
->>
 > Via AWS CLI
 >> /// details | **Via AWS s3**
 >>
@@ -516,6 +505,24 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >> > If your bucket has Object Lock enabled, you will not be able to permanently delete your objects. See our [documentation](/pages/storage_and_backup/object_storage/s3_managing_object_lock) to learn more about Object Lock.
 >> > If you use Object Lock in GOVERNANCE mode and have the permission to bypass GOVERNANCE mode, you will have to add the `--bypass-governance-retention` option to your delete commands.
 >> >
+>>
+> Via the OVHcloud Control Panel
+>> **Deleting a bucket:**
+>>
+>> In the list of object storage containers, click on the `...`{.action} button on the containers line, then click `Delete`{.action}.
+>>
+>> ![Delete bucket](images/delete-bucket.png){.thumbnail}
+>>
+>> Click on `Confirm`{.action}.
+>>
+>> **Deleting objects:**
+>>
+>> Go to the relevant bucket and click on the `...`{.action} button on the object line, then click `Delete`{.action}.
+>>
+>> ![Delete file](images/delete-file.png){.thumbnail}
+>>
+>> Click on `Confirm`{.action}.
+>>
 
 **Manage tags**
 
diff --git a/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.en-ca.md b/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.en-ca.md
index 568cb2d219a..f451ae99c28 100644
--- a/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.en-ca.md
+++ b/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.en-ca.md
@@ -1,7 +1,7 @@
 ---
 title: Object Storage - Getting started with Object Storage
 excerpt: This guide is designed to familiarise you with the management of your containers/objects
-updated: 2025-03-17
+updated: 2025-05-05
 ---
 
 <style>
@@ -42,6 +42,11 @@ This guide is designed to familiarise you with the management of your containers
 
 ## Instructions
 
+> [!primary]
+>
+> If you wish to use the OVHcloud Terraform provider, you can follow [this guide](/pages/storage_and_backup/object_storage/s3_terraform).
+>
+
 ### Preparation
 
 /// details | To use the AWS CLI
@@ -284,6 +289,7 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >> Congratulations, your bucket is created:
 >>
 >> ![Result](images/01-object-storage-bucket-listing.png)
+>>
 
 #### Uploading your files as objects in your bucket
 
@@ -428,23 +434,6 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >
 
 > [!tabs]
-> Via the OVHcloud Control Panel
->> **Deleting a bucket:**
->>
->> In the list of object storage containers, click on the `...`{.action} button on the containers line, then click `Delete`{.action}.
->>
->> ![Delete bucket](images/delete-bucket.png){.thumbnail}
->>
->> Click on `Confirm`{.action}.
->>
->> **Deleting objects:**
->>
->> Go to the relevant bucket and click on the `...`{.action} button on the object line, then click `Delete`{.action}.
->>
->> ![Delete file](images/delete-file.png){.thumbnail}
->>
->> Click on `Confirm`{.action}.
->>
 > Via AWS CLI
 >> /// details | **Via AWS s3**
 >>
@@ -516,6 +505,24 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >> > If your bucket has Object Lock enabled, you will not be able to permanently delete your objects. See our [documentation](/pages/storage_and_backup/object_storage/s3_managing_object_lock) to learn more about Object Lock.
 >> > If you use Object Lock in GOVERNANCE mode and have the permission to bypass GOVERNANCE mode, you will have to add the `--bypass-governance-retention` option to your delete commands.
 >> >
+>>
+> Via the OVHcloud Control Panel
+>> **Deleting a bucket:**
+>>
+>> In the list of object storage containers, click on the `...`{.action} button on the containers line, then click `Delete`{.action}.
+>>
+>> ![Delete bucket](images/delete-bucket.png){.thumbnail}
+>>
+>> Click on `Confirm`{.action}.
+>>
+>> **Deleting objects:**
+>>
+>> Go to the relevant bucket and click on the `...`{.action} button on the object line, then click `Delete`{.action}.
+>>
+>> ![Delete file](images/delete-file.png){.thumbnail}
+>>
+>> Click on `Confirm`{.action}.
+>>
 
 **Manage tags**
 
diff --git a/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.en-gb.md b/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.en-gb.md
index 576d4b071fb..efa35cfe7ab 100644
--- a/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.en-gb.md
+++ b/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.en-gb.md
@@ -1,7 +1,7 @@
 ---
 title: Object Storage - Getting started with Object Storage
 excerpt: This guide is designed to familiarise you with the management of your containers/objects
-updated: 2025-03-17
+updated: 2025-05-05
 ---
 
 <style>
@@ -42,6 +42,11 @@ This guide is designed to familiarise you with the management of your containers
 
 ## Instructions
 
+> [!primary]
+>
+> If you wish to use the OVHcloud Terraform provider, you can follow [this guide](/pages/storage_and_backup/object_storage/s3_terraform).
+>
+
 ### Preparation
 
 /// details | To use the AWS CLI
@@ -284,6 +289,7 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >> Congratulations, your bucket is created:
 >>
 >> ![Result](images/01-object-storage-bucket-listing.png)
+>>
 
 #### Uploading your files as objects in your bucket
 
@@ -428,23 +434,6 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >
 
 > [!tabs]
-> Via the OVHcloud Control Panel
->> **Deleting a bucket:**
->>
->> In the list of object storage containers, click on the `...`{.action} button on the containers line, then click `Delete`{.action}.
->>
->> ![Delete bucket](images/delete-bucket.png){.thumbnail}
->>
->> Click on `Confirm`{.action}.
->>
->> **Deleting objects:**
->>
->> Go to the relevant bucket and click on the `...`{.action} button on the object line, then click `Delete`{.action}.
->>
->> ![Delete file](images/delete-file.png){.thumbnail}
->>
->> Click on `Confirm`{.action}.
->>
 > Via AWS CLI
 >> /// details | **Via AWS s3**
 >>
@@ -516,6 +505,24 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >> > If your bucket has Object Lock enabled, you will not be able to permanently delete your objects. See our [documentation](/pages/storage_and_backup/object_storage/s3_managing_object_lock) to learn more about Object Lock.
 >> > If you use Object Lock in GOVERNANCE mode and have the permission to bypass GOVERNANCE mode, you will have to add the `--bypass-governance-retention` option to your delete commands.
 >> >
+>>
+> Via the OVHcloud Control Panel
+>> **Deleting a bucket:**
+>>
+>> In the list of object storage containers, click on the `...`{.action} button on the containers line, then click `Delete`{.action}.
+>>
+>> ![Delete bucket](images/delete-bucket.png){.thumbnail}
+>>
+>> Click on `Confirm`{.action}.
+>>
+>> **Deleting objects:**
+>>
+>> Go to the relevant bucket and click on the `...`{.action} button on the object line, then click `Delete`{.action}.
+>>
+>> ![Delete file](images/delete-file.png){.thumbnail}
+>>
+>> Click on `Confirm`{.action}.
+>>
 
 **Manage tags**
 
diff --git a/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.en-ie.md b/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.en-ie.md
index 568cb2d219a..f451ae99c28 100644
--- a/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.en-ie.md
+++ b/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.en-ie.md
@@ -1,7 +1,7 @@
 ---
 title: Object Storage - Getting started with Object Storage
 excerpt: This guide is designed to familiarise you with the management of your containers/objects
-updated: 2025-03-17
+updated: 2025-05-05
 ---
 
 <style>
@@ -42,6 +42,11 @@ This guide is designed to familiarise you with the management of your containers
 
 ## Instructions
 
+> [!primary]
+>
+> If you wish to use the OVHcloud Terraform provider, you can follow [this guide](/pages/storage_and_backup/object_storage/s3_terraform).
+>
+
 ### Preparation
 
 /// details | To use the AWS CLI
@@ -284,6 +289,7 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >> Congratulations, your bucket is created:
 >>
 >> ![Result](images/01-object-storage-bucket-listing.png)
+>>
 
 #### Uploading your files as objects in your bucket
 
@@ -428,23 +434,6 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >
 
 > [!tabs]
-> Via the OVHcloud Control Panel
->> **Deleting a bucket:**
->>
->> In the list of object storage containers, click on the `...`{.action} button on the containers line, then click `Delete`{.action}.
->>
->> ![Delete bucket](images/delete-bucket.png){.thumbnail}
->>
->> Click on `Confirm`{.action}.
->>
->> **Deleting objects:**
->>
->> Go to the relevant bucket and click on the `...`{.action} button on the object line, then click `Delete`{.action}.
->>
->> ![Delete file](images/delete-file.png){.thumbnail}
->>
->> Click on `Confirm`{.action}.
->>
 > Via AWS CLI
 >> /// details | **Via AWS s3**
 >>
@@ -516,6 +505,24 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >> > If your bucket has Object Lock enabled, you will not be able to permanently delete your objects. See our [documentation](/pages/storage_and_backup/object_storage/s3_managing_object_lock) to learn more about Object Lock.
 >> > If you use Object Lock in GOVERNANCE mode and have the permission to bypass GOVERNANCE mode, you will have to add the `--bypass-governance-retention` option to your delete commands.
 >> >
+>>
+> Via the OVHcloud Control Panel
+>> **Deleting a bucket:**
+>>
+>> In the list of object storage containers, click on the `...`{.action} button on the containers line, then click `Delete`{.action}.
+>>
+>> ![Delete bucket](images/delete-bucket.png){.thumbnail}
+>>
+>> Click on `Confirm`{.action}.
+>>
+>> **Deleting objects:**
+>>
+>> Go to the relevant bucket and click on the `...`{.action} button on the object line, then click `Delete`{.action}.
+>>
+>> ![Delete file](images/delete-file.png){.thumbnail}
+>>
+>> Click on `Confirm`{.action}.
+>>
 
 **Manage tags**
 
diff --git a/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.en-sg.md b/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.en-sg.md
index 568cb2d219a..f451ae99c28 100644
--- a/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.en-sg.md
+++ b/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.en-sg.md
@@ -1,7 +1,7 @@
 ---
 title: Object Storage - Getting started with Object Storage
 excerpt: This guide is designed to familiarise you with the management of your containers/objects
-updated: 2025-03-17
+updated: 2025-05-05
 ---
 
 <style>
@@ -42,6 +42,11 @@ This guide is designed to familiarise you with the management of your containers
 
 ## Instructions
 
+> [!primary]
+>
+> If you wish to use the OVHcloud Terraform provider, you can follow [this guide](/pages/storage_and_backup/object_storage/s3_terraform).
+>
+
 ### Preparation
 
 /// details | To use the AWS CLI
@@ -284,6 +289,7 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >> Congratulations, your bucket is created:
 >>
 >> ![Result](images/01-object-storage-bucket-listing.png)
+>>
 
 #### Uploading your files as objects in your bucket
 
@@ -428,23 +434,6 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >
 
 > [!tabs]
-> Via the OVHcloud Control Panel
->> **Deleting a bucket:**
->>
->> In the list of object storage containers, click on the `...`{.action} button on the containers line, then click `Delete`{.action}.
->>
->> ![Delete bucket](images/delete-bucket.png){.thumbnail}
->>
->> Click on `Confirm`{.action}.
->>
->> **Deleting objects:**
->>
->> Go to the relevant bucket and click on the `...`{.action} button on the object line, then click `Delete`{.action}.
->>
->> ![Delete file](images/delete-file.png){.thumbnail}
->>
->> Click on `Confirm`{.action}.
->>
 > Via AWS CLI
 >> /// details | **Via AWS s3**
 >>
@@ -516,6 +505,24 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >> > If your bucket has Object Lock enabled, you will not be able to permanently delete your objects. See our [documentation](/pages/storage_and_backup/object_storage/s3_managing_object_lock) to learn more about Object Lock.
 >> > If you use Object Lock in GOVERNANCE mode and have the permission to bypass GOVERNANCE mode, you will have to add the `--bypass-governance-retention` option to your delete commands.
 >> >
+>>
+> Via the OVHcloud Control Panel
+>> **Deleting a bucket:**
+>>
+>> In the list of object storage containers, click on the `...`{.action} button on the containers line, then click `Delete`{.action}.
+>>
+>> ![Delete bucket](images/delete-bucket.png){.thumbnail}
+>>
+>> Click on `Confirm`{.action}.
+>>
+>> **Deleting objects:**
+>>
+>> Go to the relevant bucket and click on the `...`{.action} button on the object line, then click `Delete`{.action}.
+>>
+>> ![Delete file](images/delete-file.png){.thumbnail}
+>>
+>> Click on `Confirm`{.action}.
+>>
 
 **Manage tags**
 
diff --git a/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.en-us.md b/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.en-us.md
index 568cb2d219a..f451ae99c28 100644
--- a/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.en-us.md
+++ b/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.en-us.md
@@ -1,7 +1,7 @@
 ---
 title: Object Storage - Getting started with Object Storage
 excerpt: This guide is designed to familiarise you with the management of your containers/objects
-updated: 2025-03-17
+updated: 2025-05-05
 ---
 
 <style>
@@ -42,6 +42,11 @@ This guide is designed to familiarise you with the management of your containers
 
 ## Instructions
 
+> [!primary]
+>
+> If you wish to use the OVHcloud Terraform provider, you can follow [this guide](/pages/storage_and_backup/object_storage/s3_terraform).
+>
+
 ### Preparation
 
 /// details | To use the AWS CLI
@@ -284,6 +289,7 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >> Congratulations, your bucket is created:
 >>
 >> ![Result](images/01-object-storage-bucket-listing.png)
+>>
 
 #### Uploading your files as objects in your bucket
 
@@ -428,23 +434,6 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >
 
 > [!tabs]
-> Via the OVHcloud Control Panel
->> **Deleting a bucket:**
->>
->> In the list of object storage containers, click on the `...`{.action} button on the containers line, then click `Delete`{.action}.
->>
->> ![Delete bucket](images/delete-bucket.png){.thumbnail}
->>
->> Click on `Confirm`{.action}.
->>
->> **Deleting objects:**
->>
->> Go to the relevant bucket and click on the `...`{.action} button on the object line, then click `Delete`{.action}.
->>
->> ![Delete file](images/delete-file.png){.thumbnail}
->>
->> Click on `Confirm`{.action}.
->>
 > Via AWS CLI
 >> /// details | **Via AWS s3**
 >>
@@ -516,6 +505,24 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >> > If your bucket has Object Lock enabled, you will not be able to permanently delete your objects. See our [documentation](/pages/storage_and_backup/object_storage/s3_managing_object_lock) to learn more about Object Lock.
 >> > If you use Object Lock in GOVERNANCE mode and have the permission to bypass GOVERNANCE mode, you will have to add the `--bypass-governance-retention` option to your delete commands.
 >> >
+>>
+> Via the OVHcloud Control Panel
+>> **Deleting a bucket:**
+>>
+>> In the list of object storage containers, click on the `...`{.action} button on the containers line, then click `Delete`{.action}.
+>>
+>> ![Delete bucket](images/delete-bucket.png){.thumbnail}
+>>
+>> Click on `Confirm`{.action}.
+>>
+>> **Deleting objects:**
+>>
+>> Go to the relevant bucket and click on the `...`{.action} button on the object line, then click `Delete`{.action}.
+>>
+>> ![Delete file](images/delete-file.png){.thumbnail}
+>>
+>> Click on `Confirm`{.action}.
+>>
 
 **Manage tags**
 
diff --git a/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.es-es.md b/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.es-es.md
index 432f9b6900d..a265794f5c0 100644
--- a/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.es-es.md
+++ b/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.es-es.md
@@ -1,7 +1,7 @@
 ---
 title: Object Storage - Introducción al Object Storage (EN)
 excerpt: This guide is designed to familiarise you with the management of your containers/objects
-updated: 2025-03-17
+updated: 2025-05-05
 ---
 
 <style>
@@ -42,6 +42,11 @@ This guide is designed to familiarise you with the management of your containers
 
 ## Instructions
 
+> [!primary]
+>
+> If you wish to use the OVHcloud Terraform provider, you can follow [this guide](/pages/storage_and_backup/object_storage/s3_terraform).
+>
+
 ### Preparation
 
 /// details | To use the AWS CLI
@@ -284,6 +289,7 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >> Congratulations, your bucket is created:
 >>
 >> ![Result](images/01-object-storage-bucket-listing.png)
+>>
 
 #### Uploading your files as objects in your bucket
 
@@ -428,23 +434,6 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >
 
 > [!tabs]
-> Via the OVHcloud Control Panel
->> **Deleting a bucket:**
->>
->> In the list of object storage containers, click on the `...`{.action} button on the containers line, then click `Delete`{.action}.
->>
->> ![Delete bucket](images/delete-bucket.png){.thumbnail}
->>
->> Click on `Confirm`{.action}.
->>
->> **Deleting objects:**
->>
->> Go to the relevant bucket and click on the `...`{.action} button on the object line, then click `Delete`{.action}.
->>
->> ![Delete file](images/delete-file.png){.thumbnail}
->>
->> Click on `Confirm`{.action}.
->>
 > Via AWS CLI
 >> /// details | **Via AWS s3**
 >>
@@ -516,6 +505,24 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >> > If your bucket has Object Lock enabled, you will not be able to permanently delete your objects. See our [documentation](/pages/storage_and_backup/object_storage/s3_managing_object_lock) to learn more about Object Lock.
 >> > If you use Object Lock in GOVERNANCE mode and have the permission to bypass GOVERNANCE mode, you will have to add the `--bypass-governance-retention` option to your delete commands.
 >> >
+>>
+> Via the OVHcloud Control Panel
+>> **Deleting a bucket:**
+>>
+>> In the list of object storage containers, click on the `...`{.action} button on the containers line, then click `Delete`{.action}.
+>>
+>> ![Delete bucket](images/delete-bucket.png){.thumbnail}
+>>
+>> Click on `Confirm`{.action}.
+>>
+>> **Deleting objects:**
+>>
+>> Go to the relevant bucket and click on the `...`{.action} button on the object line, then click `Delete`{.action}.
+>>
+>> ![Delete file](images/delete-file.png){.thumbnail}
+>>
+>> Click on `Confirm`{.action}.
+>>
 
 **Manage tags**
 
diff --git a/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.es-us.md b/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.es-us.md
index 432f9b6900d..a265794f5c0 100644
--- a/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.es-us.md
+++ b/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.es-us.md
@@ -1,7 +1,7 @@
 ---
 title: Object Storage - Introducción al Object Storage (EN)
 excerpt: This guide is designed to familiarise you with the management of your containers/objects
-updated: 2025-03-17
+updated: 2025-05-05
 ---
 
 <style>
@@ -42,6 +42,11 @@ This guide is designed to familiarise you with the management of your containers
 
 ## Instructions
 
+> [!primary]
+>
+> If you wish to use the OVHcloud Terraform provider, you can follow [this guide](/pages/storage_and_backup/object_storage/s3_terraform).
+>
+
 ### Preparation
 
 /// details | To use the AWS CLI
@@ -284,6 +289,7 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >> Congratulations, your bucket is created:
 >>
 >> ![Result](images/01-object-storage-bucket-listing.png)
+>>
 
 #### Uploading your files as objects in your bucket
 
@@ -428,23 +434,6 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >
 
 > [!tabs]
-> Via the OVHcloud Control Panel
->> **Deleting a bucket:**
->>
->> In the list of object storage containers, click on the `...`{.action} button on the containers line, then click `Delete`{.action}.
->>
->> ![Delete bucket](images/delete-bucket.png){.thumbnail}
->>
->> Click on `Confirm`{.action}.
->>
->> **Deleting objects:**
->>
->> Go to the relevant bucket and click on the `...`{.action} button on the object line, then click `Delete`{.action}.
->>
->> ![Delete file](images/delete-file.png){.thumbnail}
->>
->> Click on `Confirm`{.action}.
->>
 > Via AWS CLI
 >> /// details | **Via AWS s3**
 >>
@@ -516,6 +505,24 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >> > If your bucket has Object Lock enabled, you will not be able to permanently delete your objects. See our [documentation](/pages/storage_and_backup/object_storage/s3_managing_object_lock) to learn more about Object Lock.
 >> > If you use Object Lock in GOVERNANCE mode and have the permission to bypass GOVERNANCE mode, you will have to add the `--bypass-governance-retention` option to your delete commands.
 >> >
+>>
+> Via the OVHcloud Control Panel
+>> **Deleting a bucket:**
+>>
+>> In the list of object storage containers, click on the `...`{.action} button on the containers line, then click `Delete`{.action}.
+>>
+>> ![Delete bucket](images/delete-bucket.png){.thumbnail}
+>>
+>> Click on `Confirm`{.action}.
+>>
+>> **Deleting objects:**
+>>
+>> Go to the relevant bucket and click on the `...`{.action} button on the object line, then click `Delete`{.action}.
+>>
+>> ![Delete file](images/delete-file.png){.thumbnail}
+>>
+>> Click on `Confirm`{.action}.
+>>
 
 **Manage tags**
 
diff --git a/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.fr-ca.md b/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.fr-ca.md
index 9ad50a96c7a..7ed7f8b55b5 100644
--- a/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.fr-ca.md
+++ b/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.fr-ca.md
@@ -1,7 +1,7 @@
 ---
 title: Object Storage - Premiers pas avec Object Storage
 excerpt: Ce guide a pour objectif de vous familiariser avec la gestion de vos conteneurs / objets
-updated: 2025-03-17
+updated: 2025-05-05
 ---
 
 <style>
@@ -42,6 +42,11 @@ Ce guide a pour objectif de vous familiariser avec la gestion de vos conteneurs/
 
 ## En pratique
 
+> [!primary]
+>
+> Si vous souhaitez utiliser le provider Terraform OVHcloud, vous pouvez suivre [ce guide](/pages/storage_and_backup/object_storage/s3_terraform).
+>
+
 ### Préparation
 
 /// details | Pour utiliser l'AWS CLI
@@ -283,6 +288,7 @@ Pour gérer un bucket Object Storage, connectez-vous d'abord à votre [espace cl
 >> Félicitations, votre bucket est créé :
 >>
 >> ![Result](images/01-object-storage-bucket-listing.png)
+>>
 
 #### Télécharger vos fichiers en tant qu'objets dans votre bucket
 
@@ -422,23 +428,6 @@ Pour gérer un bucket Object Storage, connectez-vous d'abord à votre [espace cl
 >
 
 > [!tabs]
-> Via l'espace client OVHcloud
->> **Suppression d'un bucket**
->>
->> Dans la liste des conteneurs Object Storage, cliquez sur le bouton `...`{.action} sur la ligne des conteneurs, puis sur `Supprimer`{.action}.
->>
->> ![Delete bucket](images/delete-bucket.png){.thumbnail}
->>
->> Cliquez sur `Confirmer`{.action}.
->>
->> **Suppression d'objets**
->>
->> Allez dans le bucket concerné et cliquez sur le bouton `...`{.action} sur la ligne de l'objet, puis sur `Supprimer`{.action}.
->>
->> ![Delete file](images/delete-file.png){.thumbnail}
->>
->> Cliquez sur `Confirmer`{.action}.
->>
 > Via AWS CLI
 >>
 >> /// details | **Avec AWS s3**
@@ -511,6 +500,24 @@ Pour gérer un bucket Object Storage, connectez-vous d'abord à votre [espace cl
 >> > Si le verrouillage d'objet est activé dans votre bucket, vous ne pourrez pas supprimer définitivement vos objets. Consultez notre [documentation](/pages/storage_and_backup/object_storage/s3_managing_object_lock) pour en savoir plus sur le verrouillage d'objet.
 >> > Si vous utilisez le verrouillage d'objet en mode GOUVERNANCE et que vous avez la permission de contourner le mode GOUVERNANCE, vous devrez ajouter l'option `--bypass-governance-retention` à vos commandes de suppression.
 >> >
+>>
+> Via l'espace client OVHcloud
+>> **Suppression d'un bucket**
+>>
+>> Dans la liste des conteneurs Object Storage, cliquez sur le bouton `...`{.action} sur la ligne des conteneurs, puis sur `Supprimer`{.action}.
+>>
+>> ![Delete bucket](images/delete-bucket.png){.thumbnail}
+>>
+>> Cliquez sur `Confirmer`{.action}.
+>>
+>> **Suppression d'objets**
+>>
+>> Allez dans le bucket concerné et cliquez sur le bouton `...`{.action} sur la ligne de l'objet, puis sur `Supprimer`{.action}.
+>>
+>> ![Delete file](images/delete-file.png){.thumbnail}
+>>
+>> Cliquez sur `Confirmer`{.action}.
+>>
 
 **Gérer les tags**
 
diff --git a/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.fr-fr.md b/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.fr-fr.md
index d54cbdffeb1..8bdf2d0b9be 100644
--- a/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.fr-fr.md
+++ b/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.fr-fr.md
@@ -1,7 +1,7 @@
 ---
 title: Object Storage - Premiers pas avec Object Storage
 excerpt: Ce guide a pour objectif de vous familiariser avec la gestion de vos conteneurs / objets
-updated: 2025-03-17
+updated: 2025-05-05
 ---
 
 <style>
@@ -42,6 +42,11 @@ Ce guide a pour objectif de vous familiariser avec la gestion de vos conteneurs/
 
 ## En pratique
 
+> [!primary]
+>
+> Si vous souhaitez utiliser le provider Terraform OVHcloud, vous pouvez suivre [ce guide](/pages/storage_and_backup/object_storage/s3_terraform).
+>
+
 ### Préparation
 
 /// details | Pour utiliser l'AWS CLI
@@ -283,6 +288,7 @@ Pour gérer un bucket Object Storage, connectez-vous d'abord à votre [espace cl
 >> Félicitations, votre bucket est créé :
 >>
 >> ![Result](images/01-object-storage-bucket-listing.png)
+>>
 
 #### Télécharger vos fichiers en tant qu'objets dans votre bucket
 
@@ -422,23 +428,6 @@ Pour gérer un bucket Object Storage, connectez-vous d'abord à votre [espace cl
 >
 
 > [!tabs]
-> Via l'espace client OVHcloud
->> **Suppression d'un bucket**
->>
->> Dans la liste des conteneurs Object Storage, cliquez sur le bouton `...`{.action} sur la ligne des conteneurs, puis sur `Supprimer`{.action}.
->>
->> ![Delete bucket](images/delete-bucket.png){.thumbnail}
->>
->> Cliquez sur `Confirmer`{.action}.
->>
->> **Suppression d'objets**
->>
->> Allez dans le bucket concerné et cliquez sur le bouton `...`{.action} sur la ligne de l'objet, puis sur `Supprimer`{.action}.
->>
->> ![Delete file](images/delete-file.png){.thumbnail}
->>
->> Cliquez sur `Confirmer`{.action}.
->>
 > Via AWS CLI
 >>
 >> /// details | **Avec AWS s3**
@@ -511,6 +500,24 @@ Pour gérer un bucket Object Storage, connectez-vous d'abord à votre [espace cl
 >> > Si le verrouillage d'objet est activé dans votre bucket, vous ne pourrez pas supprimer définitivement vos objets. Consultez notre [documentation](/pages/storage_and_backup/object_storage/s3_managing_object_lock) pour en savoir plus sur le verrouillage d'objet.
 >> > Si vous utilisez le verrouillage d'objet en mode GOUVERNANCE et que vous avez la permission de contourner le mode GOUVERNANCE, vous devrez ajouter l'option `--bypass-governance-retention` à vos commandes de suppression.
 >> >
+>>
+> Via l'espace client OVHcloud
+>> **Suppression d'un bucket**
+>>
+>> Dans la liste des conteneurs Object Storage, cliquez sur le bouton `...`{.action} sur la ligne des conteneurs, puis sur `Supprimer`{.action}.
+>>
+>> ![Delete bucket](images/delete-bucket.png){.thumbnail}
+>>
+>> Cliquez sur `Confirmer`{.action}.
+>>
+>> **Suppression d'objets**
+>>
+>> Allez dans le bucket concerné et cliquez sur le bouton `...`{.action} sur la ligne de l'objet, puis sur `Supprimer`{.action}.
+>>
+>> ![Delete file](images/delete-file.png){.thumbnail}
+>>
+>> Cliquez sur `Confirmer`{.action}.
+>>
 
 **Gérer les tags**
 
diff --git a/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.it-it.md b/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.it-it.md
index b1642b5aded..8be819e6060 100644
--- a/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.it-it.md
+++ b/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.it-it.md
@@ -1,7 +1,7 @@
 ---
 title: Object Storage - Come iniziare con Object Storage (EN)
 excerpt: This guide is designed to familiarise you with the management of your containers/objects
-updated: 2025-03-17
+updated: 2025-05-05
 ---
 
 <style>
@@ -42,6 +42,11 @@ This guide is designed to familiarise you with the management of your containers
 
 ## Instructions
 
+> [!primary]
+>
+> If you wish to use the OVHcloud Terraform provider, you can follow [this guide](/pages/storage_and_backup/object_storage/s3_terraform).
+>
+
 ### Preparation
 
 /// details | To use the AWS CLI
@@ -284,6 +289,7 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >> Congratulations, your bucket is created:
 >>
 >> ![Result](images/01-object-storage-bucket-listing.png)
+>>
 
 #### Uploading your files as objects in your bucket
 
@@ -428,23 +434,6 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >
 
 > [!tabs]
-> Via the OVHcloud Control Panel
->> **Deleting a bucket:**
->>
->> In the list of object storage containers, click on the `...`{.action} button on the containers line, then click `Delete`{.action}.
->>
->> ![Delete bucket](images/delete-bucket.png){.thumbnail}
->>
->> Click on `Confirm`{.action}.
->>
->> **Deleting objects:**
->>
->> Go to the relevant bucket and click on the `...`{.action} button on the object line, then click `Delete`{.action}.
->>
->> ![Delete file](images/delete-file.png){.thumbnail}
->>
->> Click on `Confirm`{.action}.
->>
 > Via AWS CLI
 >> /// details | **Via AWS s3**
 >>
@@ -516,6 +505,24 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >> > If your bucket has Object Lock enabled, you will not be able to permanently delete your objects. See our [documentation](/pages/storage_and_backup/object_storage/s3_managing_object_lock) to learn more about Object Lock.
 >> > If you use Object Lock in GOVERNANCE mode and have the permission to bypass GOVERNANCE mode, you will have to add the `--bypass-governance-retention` option to your delete commands.
 >> >
+>>
+> Via the OVHcloud Control Panel
+>> **Deleting a bucket:**
+>>
+>> In the list of object storage containers, click on the `...`{.action} button on the containers line, then click `Delete`{.action}.
+>>
+>> ![Delete bucket](images/delete-bucket.png){.thumbnail}
+>>
+>> Click on `Confirm`{.action}.
+>>
+>> **Deleting objects:**
+>>
+>> Go to the relevant bucket and click on the `...`{.action} button on the object line, then click `Delete`{.action}.
+>>
+>> ![Delete file](images/delete-file.png){.thumbnail}
+>>
+>> Click on `Confirm`{.action}.
+>>
 
 **Manage tags**
 
diff --git a/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.pl-pl.md b/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.pl-pl.md
index 01bd8788cd7..c289522ad6a 100644
--- a/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.pl-pl.md
+++ b/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.pl-pl.md
@@ -1,7 +1,7 @@
 ---
 title: Object Storage - Pierwsze kroki z Object Storage (EN)
 excerpt: This guide is designed to familiarise you with the management of your containers/objects
-updated: 2025-03-17
+updated: 2025-05-05
 ---
 
 <style>
@@ -42,6 +42,11 @@ This guide is designed to familiarise you with the management of your containers
 
 ## Instructions
 
+> [!primary]
+>
+> If you wish to use the OVHcloud Terraform provider, you can follow [this guide](/pages/storage_and_backup/object_storage/s3_terraform).
+>
+
 ### Preparation
 
 /// details | To use the AWS CLI
@@ -284,6 +289,7 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >> Congratulations, your bucket is created:
 >>
 >> ![Result](images/01-object-storage-bucket-listing.png)
+>>
 
 #### Uploading your files as objects in your bucket
 
@@ -428,23 +434,6 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >
 
 > [!tabs]
-> Via the OVHcloud Control Panel
->> **Deleting a bucket:**
->>
->> In the list of object storage containers, click on the `...`{.action} button on the containers line, then click `Delete`{.action}.
->>
->> ![Delete bucket](images/delete-bucket.png){.thumbnail}
->>
->> Click on `Confirm`{.action}.
->>
->> **Deleting objects:**
->>
->> Go to the relevant bucket and click on the `...`{.action} button on the object line, then click `Delete`{.action}.
->>
->> ![Delete file](images/delete-file.png){.thumbnail}
->>
->> Click on `Confirm`{.action}.
->>
 > Via AWS CLI
 >> /// details | **Via AWS s3**
 >>
@@ -516,6 +505,24 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >> > If your bucket has Object Lock enabled, you will not be able to permanently delete your objects. See our [documentation](/pages/storage_and_backup/object_storage/s3_managing_object_lock) to learn more about Object Lock.
 >> > If you use Object Lock in GOVERNANCE mode and have the permission to bypass GOVERNANCE mode, you will have to add the `--bypass-governance-retention` option to your delete commands.
 >> >
+>>
+> Via the OVHcloud Control Panel
+>> **Deleting a bucket:**
+>>
+>> In the list of object storage containers, click on the `...`{.action} button on the containers line, then click `Delete`{.action}.
+>>
+>> ![Delete bucket](images/delete-bucket.png){.thumbnail}
+>>
+>> Click on `Confirm`{.action}.
+>>
+>> **Deleting objects:**
+>>
+>> Go to the relevant bucket and click on the `...`{.action} button on the object line, then click `Delete`{.action}.
+>>
+>> ![Delete file](images/delete-file.png){.thumbnail}
+>>
+>> Click on `Confirm`{.action}.
+>>
 
 **Manage tags**
 
diff --git a/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.pt-pt.md b/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.pt-pt.md
index 0001a79f338..157eafba9be 100644
--- a/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.pt-pt.md
+++ b/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage/guide.pt-pt.md
@@ -1,7 +1,7 @@
 ---
 title: Object Storage - Introdução ao Object Storage (EN)
 excerpt: This guide is designed to familiarise you with the management of your containers/objects
-updated: 2025-03-17
+updated: 2025-05-05
 ---
 
 <style>
@@ -42,6 +42,11 @@ This guide is designed to familiarise you with the management of your containers
 
 ## Instructions
 
+> [!primary]
+>
+> If you wish to use the OVHcloud Terraform provider, you can follow [this guide](/pages/storage_and_backup/object_storage/s3_terraform).
+>
+
 ### Preparation
 
 /// details | To use the AWS CLI
@@ -284,6 +289,7 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >> Congratulations, your bucket is created:
 >>
 >> ![Result](images/01-object-storage-bucket-listing.png)
+>>
 
 #### Uploading your files as objects in your bucket
 
@@ -428,23 +434,6 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >
 
 > [!tabs]
-> Via the OVHcloud Control Panel
->> **Deleting a bucket:**
->>
->> In the list of object storage containers, click on the `...`{.action} button on the containers line, then click `Delete`{.action}.
->>
->> ![Delete bucket](images/delete-bucket.png){.thumbnail}
->>
->> Click on `Confirm`{.action}.
->>
->> **Deleting objects:**
->>
->> Go to the relevant bucket and click on the `...`{.action} button on the object line, then click `Delete`{.action}.
->>
->> ![Delete file](images/delete-file.png){.thumbnail}
->>
->> Click on `Confirm`{.action}.
->>
 > Via AWS CLI
 >> /// details | **Via AWS s3**
 >>
@@ -516,6 +505,24 @@ To manage an Object Storage bucket, first log in to your [OVHcloud Control Panel
 >> > If your bucket has Object Lock enabled, you will not be able to permanently delete your objects. See our [documentation](/pages/storage_and_backup/object_storage/s3_managing_object_lock) to learn more about Object Lock.
 >> > If you use Object Lock in GOVERNANCE mode and have the permission to bypass GOVERNANCE mode, you will have to add the `--bypass-governance-retention` option to your delete commands.
 >> >
+>>
+> Via the OVHcloud Control Panel
+>> **Deleting a bucket:**
+>>
+>> In the list of object storage containers, click on the `...`{.action} button on the containers line, then click `Delete`{.action}.
+>>
+>> ![Delete bucket](images/delete-bucket.png){.thumbnail}
+>>
+>> Click on `Confirm`{.action}.
+>>
+>> **Deleting objects:**
+>>
+>> Go to the relevant bucket and click on the `...`{.action} button on the object line, then click `Delete`{.action}.
+>>
+>> ![Delete file](images/delete-file.png){.thumbnail}
+>>
+>> Click on `Confirm`{.action}.
+>>
 
 **Manage tags**
 
diff --git a/pages/storage_and_backup/object_storage/s3_terraform/guide.de-de.md b/pages/storage_and_backup/object_storage/s3_terraform/guide.de-de.md
index 0e689d132e0..5c512e04cc4 100644
--- a/pages/storage_and_backup/object_storage/s3_terraform/guide.de-de.md
+++ b/pages/storage_and_backup/object_storage/s3_terraform/guide.de-de.md
@@ -1,145 +1,116 @@
 ---
 title: Object Storage - Verwalten Sie einen Object Storage Bucket mit Terraform (EN)
-updated: 2024-08-27
+updated: 2025-05-05
 ---
 
 ## Objective
 
-This tutorial will show you how to automate some actions on Object Storage with Terraform which is an open source tool to automate infrastructure provisioning. The following actions will be automated:
-
-- Object Storage user creation
-- bucket creation
-- file copy into the bucket
-- S3 **\*** policies and assignment
+This tutorial will help you automate and orchestrate actions to use the [Object Storage](/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage) - S3* API with Terraform. Terraform is an open source tool for orchestrating the provisioning of resources.
 
 ## Requirements
 
-- Have terraform command line installed (see this [tutorial](https://developer.hashicorp.com/terraform/tutorials/aws-get-started/install-cli) from Hashicorp, the company behind Terraform). 
-- Have git command line installed
-- You will need to have set up an account to interact with the OVHcloud API (see this [tutorial](/pages/manage_and_operate/api/first-steps)). Depending on your needs in terms of permissions (http verbs PUT/GET/POST/DELETE), enter the route `/cloud/project/{serviceName}/region/{regionName}/storage/` to target object storage where *{serviceName}* corresponds to your Public Cloud project id and *{regionName}* corresponds to the region where your resources will be located. From the application keys created, you will need to export the 4 environment variables :
-
-```bash
-$ export OVH_ENDPOINT=ovh-eu
-$ export OVH_APPLICATION_KEY=Your_key_application_OVH(or_AK)
-$ export OVH_APPLICATION_SECRET=Your_secret_application_key_OVH(or_AS)
-$ export OVH_CONSUMER_KEY=Your_token(or_CK)
-```   
-
-- A Public Cloud project, with the ID exported as the variable `TF_VAR_OVH_PUBLIC_CLOUD_PROJECT_ID`
-
-```bash
-$ export TF_VAR_OVH_PUBLIC_CLOUD_PROJECT_ID=Your_public_cloud_project_id
-```
-
-**If you do not have your AWS CLI** configured, you should set dummy values with the following. This is due to a limitation in Terraform dependency graph for providers initialization (see this long lasting terraform [issue)](https://github.com/hashicorp/terraform/issues/2430)):
-
-```bash
-$ export AWS_ACCESS_KEY_ID="no_need_to_define_an_access_key"  
-$ export AWS_SECRET_ACCESS_KEY="no_need_to_define_a_secret_key"
-```
-
-## Instructions
+- Installation of the [Terraform CLI](https://www.terraform.io/downloads.html){.external}
+- Access to the [OVHcloud API](/links/api) (create your login by consulting [this guide](/pages/manage_and_operate/api/first-steps))
+- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account.
+- OVHcloud provides a [Terraform provider](https://registry.terraform.io/providers/ovh/ovh/latest){.external} which is available in the official Terraform registry. You must have installed a version >= 2.0. You can follow this guide [How to use Terraform on the OVHcloud Public Cloud](/pages/public_cloud/compute/how_to_use_terraform).
 
-### Manage an Object Storage bucket with terraform @OVHcloud
+## Getting information on your cluster/API tokens
 
-#### Initialize
+The “OVH provider” must be configured with a set of credentials:
 
-Clone the repository:
+- an `application_key`
+- an `application_secret`
+- a `consumer_key`
 
-```bash
-git clone https://github.com/yomovh/tf-at-ovhcloud && cd tf-at-ovhcloud/s3_bucket_only
-```
+Why?
 
-Initialize Terraform:
+Because, behind the scenes, the OVH Terraform provider makes requests to the OVHcloud APIs.
 
-```bash
-$ terraform init
-```
+To retrieve this necessary information, please follow the tutorial [First steps with the OVHcloud APIs](/pages/manage_and_operate/api/first-steps).
 
-#### Plan
+Once you've successfully generated your OVHcloud tokens, keep them. You'll need to set them in the next few minutes.
 
-With the following command, you will see what are the actions that Terraform is going to perform:
+The last piece of information you'll need is the `service_name`: this is the ID of your Public Cloud project.
 
-```bash
-$ terraform plan
-```
-
-Now let's have a look at the content of the `main.tf` file:
+How do I get it?
 
-- The *variable* block defines the region and s3 endpoint that are used to create the bucket. You can update it according to your needs : check this [page](/pages/storage_and_backup/object_storage/s3_location) to know what region / endpoints are available.
-- The *Providers* block defines 2 providers : ovh and Hashicorp AWS one. The first one is necessary to create the user whose identity / credentials will be used for the latest.
-- The *User / Credential* block defines the user & credential that are visible in the Settings > Users & Roles tab. They are needed to configure the Hashicorp AWS provider.
-- The Bucket block defines the bucket itself.
-- The Output defines the access & secret key that may be useful for CLI usage.
+In the Public Cloud section, you can retrieve your service name ID using the `Copy to clipboard`{.action} button.
 
-#### Run
+![Copy paste service name](images/get-service-name.png){.thumbnail}
 
-```bash
-$ terraform apply
-```
+You can also use this information in Terraform resource definition files.
 
-Now you can go in the Console and check the "Object Storage" tab. Your bucket is created.
-
-#### Destroy
+## Instructions
 
-With the following command you will be back to your original state: Terraform will destroy all the resources that were previously created.
+If you would like to access the provider's documentation on Object Storage, [click here](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage.){.external}
 
-```bash
-$ terraform destroy
-```
+### Configuration
 
-> [!primary]
->
-> - This script does not follow Terraform best practices to split the project in multiple files e.g. **`provider.tf`, `main.tf`, `variables.tf`, `outputs.tf`**, ... This has been done intentionnaly to avoid switching into multiples files for what is a really simple example.
-> - The secret that is created by this script is stored in the [local](https://developer.hashicorp.com/terraform/language/settings/backends/local) state back-end. If you use this back-end in production, make sure to consider the state file as a secret.
+First, create a `provider.tf` file with the minimum version, the European endpoint (“ovh-eu”) and the keys you obtained in this guide.
 
-### Automating Object Storage policies with Terraform
-
-#### Initialize
-
-Clone the repository:
+Terraform:
 
 ```bash
-git clone https://github.com/yomovh/tf-at-ovhcloud && cd tf-at-ovhcloud/s3_policy
+terraform {
+  required_providers {
+    ovh = {
+      source  = "ovh/ovh"
+      version = "2.1.0" # greater than or equal to 2.0
+    }
+  }
+}
+
+provider "ovh" {
+  endpoint           = "ovh-eu"
+  application_key    = "<your_access_key>"
+  application_secret = "<your_application_secret>"
+  consumer_key       = "<your_consumer_key>"
+}
 ```
 
-Initialize Terraform:
-
-```bash
-$ terraform init
+Here, we've defined the `ovh-eu` endpoint because we want to call the OVHcloud Europe API, but other endpoints exist, depending on your needs:
+
+- `ovh-eu` pour OVHcloud Europe API
+- `ovh-us` pour OVHcloud US API
+- `ovh-ca` pour OVHcloud North-America API
+
+### Create a bucket
+
+You can create a file named 'object_storage_simple.tf' and write the following:
+
+```python
+# Create an Object Storage bucket
+resource "ovh_cloud_project_storage" "my-bucket" {
+ service_name = "my_service_name" # Replace with your OVHcloud project ID
+ region_name = "GRA" # Replace with the desired region in uppercase.
+  name = "object-storage-simple"
+  versioning = {
+    status = "enabled"
+  }
+  encryption = {
+    sse_algorithm = "AES256"
+  }
+}
 ```
 
-#### Plan
-
-With the following command, you will see what are the actions that Terraform is going to perform:
+You can create your resource by entering the following command:
 
 ```bash
-$ terraform plan
+terraform apply
 ```
 
-Now let's have a look at the content of the `main.tf` file and compare it with the previous example:
+### Delete a bucket
 
-- The *User / Credential* block defines 3 users and credentials : one user will be administrator of the bucket and create it, the two others will have read/write & read-only access.
-- In the *Bucket* block we have added the creation of a file into the bucket
-- The *Policy* block defines 2 policies, one for read/write and the other for read-only on the bucket.
-
-#### Run
+You can delete your bucket and all the objects it contains by entering the following command:
 
 ```bash
-$ terraform apply
+terraform destroy
 ```
 
-Now you can go in the Console and check the "Object Storage" tab. You will see the bucket and the file.
-
-You can also check the access right by using the AWS CLI with the 2 users that have the read / write & read-only access
-
-#### Destroy
-
-With the following command you will be back to your original state: Terraform will destroy all the resources that were previously created.
-
-```bash
-$ terraform destroy
-```
+> [!primary]
+>
+> This process may fail if the bucket contains locked objects. In this case, you'll need to delete these objects manually before you can run the command again.
+>
 
 ## Go further
 
diff --git a/pages/storage_and_backup/object_storage/s3_terraform/guide.en-asia.md b/pages/storage_and_backup/object_storage/s3_terraform/guide.en-asia.md
index cfcf00711ba..70caaa12e80 100644
--- a/pages/storage_and_backup/object_storage/s3_terraform/guide.en-asia.md
+++ b/pages/storage_and_backup/object_storage/s3_terraform/guide.en-asia.md
@@ -1,145 +1,116 @@
 ---
 title: Object Storage - Manage an Object Storage bucket with Terraform
-updated: 2024-08-27
+updated: 2025-05-05
 ---
 
 ## Objective
 
-This tutorial will show you how to automate some actions on Object Storage with Terraform which is an open source tool to automate infrastructure provisioning. The following actions will be automated:
-
-- Object Storage user creation
-- bucket creation
-- file copy into the bucket
-- S3 **\*** policies and assignment
+This tutorial will help you automate and orchestrate actions to use the [Object Storage](/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage) - S3* API with Terraform. Terraform is an open source tool for orchestrating the provisioning of resources.
 
 ## Requirements
 
-- Have terraform command line installed (see this [tutorial](https://developer.hashicorp.com/terraform/tutorials/aws-get-started/install-cli) from Hashicorp, the company behind Terraform). 
-- Have git command line installed
-- You will need to have set up an account to interact with the OVHcloud API (see this [tutorial](/pages/manage_and_operate/api/first-steps)). Depending on your needs in terms of permissions (http verbs PUT/GET/POST/DELETE), enter the route `/cloud/project/{serviceName}/region/{regionName}/storage/` to target object storage where *{serviceName}* corresponds to your Public Cloud project id and *{regionName}* corresponds to the region where your resources will be located. From the application keys created, you will need to export the 4 environment variables :
-
-```bash
-$ export OVH_ENDPOINT=ovh-eu
-$ export OVH_APPLICATION_KEY=Your_key_application_OVH(or_AK)
-$ export OVH_APPLICATION_SECRET=Your_secret_application_key_OVH(or_AS)
-$ export OVH_CONSUMER_KEY=Your_token(or_CK)
-```   
-
-- A Public Cloud project, with the ID exported as the variable `TF_VAR_OVH_PUBLIC_CLOUD_PROJECT_ID`
-
-```bash
-$ export TF_VAR_OVH_PUBLIC_CLOUD_PROJECT_ID=Your_public_cloud_project_id
-```
-
-**If you do not have your AWS CLI** configured, you should set dummy values with the following. This is due to a limitation in Terraform dependency graph for providers initialization (see this long lasting terraform [issue)](https://github.com/hashicorp/terraform/issues/2430)):
-
-```bash
-$ export AWS_ACCESS_KEY_ID="no_need_to_define_an_access_key"  
-$ export AWS_SECRET_ACCESS_KEY="no_need_to_define_a_secret_key"
-```
-
-## Instructions
+- Installation of the [Terraform CLI](https://www.terraform.io/downloads.html){.external}
+- Access to the [OVHcloud API](/links/api) (create your login by consulting [this guide](/pages/manage_and_operate/api/first-steps))
+- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account.
+- OVHcloud provides a [Terraform provider](https://registry.terraform.io/providers/ovh/ovh/latest){.external} which is available in the official Terraform registry. You must have installed a version >= 2.0. You can follow this guide [How to use Terraform on the OVHcloud Public Cloud](/pages/public_cloud/compute/how_to_use_terraform).
 
-### Manage an Object Storage bucket with terraform @OVHcloud
+## Getting information on your cluster/API tokens
 
-#### Initialize
+The “OVH provider” must be configured with a set of credentials:
 
-Clone the repository:
+- an `application_key`
+- an `application_secret`
+- a `consumer_key`
 
-```bash
-git clone https://github.com/yomovh/tf-at-ovhcloud && cd tf-at-ovhcloud/s3_bucket_only
-```
+Why?
 
-Initialize Terraform:
+Because, behind the scenes, the OVH Terraform provider makes requests to the OVHcloud APIs.
 
-```bash
-$ terraform init
-```
+To retrieve this necessary information, please follow the tutorial [First steps with the OVHcloud APIs](/pages/manage_and_operate/api/first-steps).
 
-#### Plan
+Once you've successfully generated your OVHcloud tokens, keep them. You'll need to set them in the next few minutes.
 
-With the following command, you will see what are the actions that Terraform is going to perform:
+The last piece of information you'll need is the `service_name`: this is the ID of your Public Cloud project.
 
-```bash
-$ terraform plan
-```
-
-Now let's have a look at the content of the `main.tf` file:
+How do I get it?
 
-- The *variable* block defines the region and s3 endpoint that are used to create the bucket. You can update it according to your needs : check this [page](/pages/storage_and_backup/object_storage/s3_location) to know what region / endpoints are available.
-- The *Providers* block defines 2 providers : ovh and Hashicorp AWS one. The first one is necessary to create the user whose identity / credentials will be used for the latest.
-- The *User / Credential* block defines the user & credential that are visible in the Settings > Users & Roles tab. They are needed to configure the Hashicorp AWS provider.
-- The Bucket block defines the bucket itself.
-- The Output defines the access & secret key that may be useful for CLI usage.
+In the Public Cloud section, you can retrieve your service name ID using the `Copy to clipboard`{.action} button.
 
-#### Run
+![Copy paste service name](images/get-service-name.png){.thumbnail}
 
-```bash
-$ terraform apply
-```
+You can also use this information in Terraform resource definition files.
 
-Now you can go in the Console and check the "Object Storage" tab. Your bucket is created.
-
-#### Destroy
+## Instructions
 
-With the following command you will be back to your original state: Terraform will destroy all the resources that were previously created.
+If you would like to access the provider's documentation on Object Storage, [click here](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage.){.external}
 
-```bash
-$ terraform destroy
-```
+### Configuration
 
-> [!primary]
->
-> - This script does not follow Terraform best practices to split the project in multiple files e.g. **`provider.tf`, `main.tf`, `variables.tf`, `outputs.tf`**, ... This has been done intentionnaly to avoid switching into multiples files for what is a really simple example.
-> - The secret that is created by this script is stored in the [local](https://developer.hashicorp.com/terraform/language/settings/backends/local) state back-end. If you use this back-end in production, make sure to consider the state file as a secret.
+First, create a `provider.tf` file with the minimum version, the European endpoint (“ovh-eu”) and the keys you obtained in this guide.
 
-### Automating Object Storage policies with Terraform
-
-#### Initialize
-
-Clone the repository:
+Terraform:
 
 ```bash
-git clone https://github.com/yomovh/tf-at-ovhcloud && cd tf-at-ovhcloud/s3_policy
+terraform {
+  required_providers {
+    ovh = {
+      source  = "ovh/ovh"
+      version = "2.1.0" # greater than or equal to 2.0
+    }
+  }
+}
+
+provider "ovh" {
+  endpoint           = "ovh-eu"
+  application_key    = "<your_access_key>"
+  application_secret = "<your_application_secret>"
+  consumer_key       = "<your_consumer_key>"
+}
 ```
 
-Initialize Terraform:
-
-```bash
-$ terraform init
+Here, we've defined the `ovh-eu` endpoint because we want to call the OVHcloud Europe API, but other endpoints exist, depending on your needs:
+
+- `ovh-eu` pour OVHcloud Europe API
+- `ovh-us` pour OVHcloud US API
+- `ovh-ca` pour OVHcloud North-America API
+
+### Create a bucket
+
+You can create a file named 'object_storage_simple.tf' and write the following:
+
+```python
+# Create an Object Storage bucket
+resource "ovh_cloud_project_storage" "my-bucket" {
+ service_name = "my_service_name" # Replace with your OVHcloud project ID
+ region_name = "GRA" # Replace with the desired region in uppercase.
+  name = "object-storage-simple"
+  versioning = {
+    status = "enabled"
+  }
+  encryption = {
+    sse_algorithm = "AES256"
+  }
+}
 ```
 
-#### Plan
-
-With the following command, you will see what are the actions that Terraform is going to perform:
+You can create your resource by entering the following command:
 
 ```bash
-$ terraform plan
+terraform apply
 ```
 
-Now let's have a look at the content of the `main.tf` file and compare it with the previous example:
+### Delete a bucket
 
-- The *User / Credential* block defines 3 users and credentials : one user will be administrator of the bucket and create it, the two others will have read/write & read-only access.
-- In the *Bucket* block we have added the creation of a file into the bucket
-- The *Policy* block defines 2 policies, one for read/write and the other for read-only on the bucket.
-
-#### Run
+You can delete your bucket and all the objects it contains by entering the following command:
 
 ```bash
-$ terraform apply
+terraform destroy
 ```
 
-Now you can go in the Console and check the "Object Storage" tab. You will see the bucket and the file.
-
-You can also check the access right by using the AWS CLI with the 2 users that have the read / write & read-only access
-
-#### Destroy
-
-With the following command you will be back to your original state: Terraform will destroy all the resources that were previously created.
-
-```bash
-$ terraform destroy
-```
+> [!primary]
+>
+> This process may fail if the bucket contains locked objects. In this case, you'll need to delete these objects manually before you can run the command again.
+>
 
 ## Go further
 
diff --git a/pages/storage_and_backup/object_storage/s3_terraform/guide.en-au.md b/pages/storage_and_backup/object_storage/s3_terraform/guide.en-au.md
index cfcf00711ba..70caaa12e80 100644
--- a/pages/storage_and_backup/object_storage/s3_terraform/guide.en-au.md
+++ b/pages/storage_and_backup/object_storage/s3_terraform/guide.en-au.md
@@ -1,145 +1,116 @@
 ---
 title: Object Storage - Manage an Object Storage bucket with Terraform
-updated: 2024-08-27
+updated: 2025-05-05
 ---
 
 ## Objective
 
-This tutorial will show you how to automate some actions on Object Storage with Terraform which is an open source tool to automate infrastructure provisioning. The following actions will be automated:
-
-- Object Storage user creation
-- bucket creation
-- file copy into the bucket
-- S3 **\*** policies and assignment
+This tutorial will help you automate and orchestrate actions to use the [Object Storage](/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage) - S3* API with Terraform. Terraform is an open source tool for orchestrating the provisioning of resources.
 
 ## Requirements
 
-- Have terraform command line installed (see this [tutorial](https://developer.hashicorp.com/terraform/tutorials/aws-get-started/install-cli) from Hashicorp, the company behind Terraform). 
-- Have git command line installed
-- You will need to have set up an account to interact with the OVHcloud API (see this [tutorial](/pages/manage_and_operate/api/first-steps)). Depending on your needs in terms of permissions (http verbs PUT/GET/POST/DELETE), enter the route `/cloud/project/{serviceName}/region/{regionName}/storage/` to target object storage where *{serviceName}* corresponds to your Public Cloud project id and *{regionName}* corresponds to the region where your resources will be located. From the application keys created, you will need to export the 4 environment variables :
-
-```bash
-$ export OVH_ENDPOINT=ovh-eu
-$ export OVH_APPLICATION_KEY=Your_key_application_OVH(or_AK)
-$ export OVH_APPLICATION_SECRET=Your_secret_application_key_OVH(or_AS)
-$ export OVH_CONSUMER_KEY=Your_token(or_CK)
-```   
-
-- A Public Cloud project, with the ID exported as the variable `TF_VAR_OVH_PUBLIC_CLOUD_PROJECT_ID`
-
-```bash
-$ export TF_VAR_OVH_PUBLIC_CLOUD_PROJECT_ID=Your_public_cloud_project_id
-```
-
-**If you do not have your AWS CLI** configured, you should set dummy values with the following. This is due to a limitation in Terraform dependency graph for providers initialization (see this long lasting terraform [issue)](https://github.com/hashicorp/terraform/issues/2430)):
-
-```bash
-$ export AWS_ACCESS_KEY_ID="no_need_to_define_an_access_key"  
-$ export AWS_SECRET_ACCESS_KEY="no_need_to_define_a_secret_key"
-```
-
-## Instructions
+- Installation of the [Terraform CLI](https://www.terraform.io/downloads.html){.external}
+- Access to the [OVHcloud API](/links/api) (create your login by consulting [this guide](/pages/manage_and_operate/api/first-steps))
+- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account.
+- OVHcloud provides a [Terraform provider](https://registry.terraform.io/providers/ovh/ovh/latest){.external} which is available in the official Terraform registry. You must have installed a version >= 2.0. You can follow this guide [How to use Terraform on the OVHcloud Public Cloud](/pages/public_cloud/compute/how_to_use_terraform).
 
-### Manage an Object Storage bucket with terraform @OVHcloud
+## Getting information on your cluster/API tokens
 
-#### Initialize
+The “OVH provider” must be configured with a set of credentials:
 
-Clone the repository:
+- an `application_key`
+- an `application_secret`
+- a `consumer_key`
 
-```bash
-git clone https://github.com/yomovh/tf-at-ovhcloud && cd tf-at-ovhcloud/s3_bucket_only
-```
+Why?
 
-Initialize Terraform:
+Because, behind the scenes, the OVH Terraform provider makes requests to the OVHcloud APIs.
 
-```bash
-$ terraform init
-```
+To retrieve this necessary information, please follow the tutorial [First steps with the OVHcloud APIs](/pages/manage_and_operate/api/first-steps).
 
-#### Plan
+Once you've successfully generated your OVHcloud tokens, keep them. You'll need to set them in the next few minutes.
 
-With the following command, you will see what are the actions that Terraform is going to perform:
+The last piece of information you'll need is the `service_name`: this is the ID of your Public Cloud project.
 
-```bash
-$ terraform plan
-```
-
-Now let's have a look at the content of the `main.tf` file:
+How do I get it?
 
-- The *variable* block defines the region and s3 endpoint that are used to create the bucket. You can update it according to your needs : check this [page](/pages/storage_and_backup/object_storage/s3_location) to know what region / endpoints are available.
-- The *Providers* block defines 2 providers : ovh and Hashicorp AWS one. The first one is necessary to create the user whose identity / credentials will be used for the latest.
-- The *User / Credential* block defines the user & credential that are visible in the Settings > Users & Roles tab. They are needed to configure the Hashicorp AWS provider.
-- The Bucket block defines the bucket itself.
-- The Output defines the access & secret key that may be useful for CLI usage.
+In the Public Cloud section, you can retrieve your service name ID using the `Copy to clipboard`{.action} button.
 
-#### Run
+![Copy paste service name](images/get-service-name.png){.thumbnail}
 
-```bash
-$ terraform apply
-```
+You can also use this information in Terraform resource definition files.
 
-Now you can go in the Console and check the "Object Storage" tab. Your bucket is created.
-
-#### Destroy
+## Instructions
 
-With the following command you will be back to your original state: Terraform will destroy all the resources that were previously created.
+If you would like to access the provider's documentation on Object Storage, [click here](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage.){.external}
 
-```bash
-$ terraform destroy
-```
+### Configuration
 
-> [!primary]
->
-> - This script does not follow Terraform best practices to split the project in multiple files e.g. **`provider.tf`, `main.tf`, `variables.tf`, `outputs.tf`**, ... This has been done intentionnaly to avoid switching into multiples files for what is a really simple example.
-> - The secret that is created by this script is stored in the [local](https://developer.hashicorp.com/terraform/language/settings/backends/local) state back-end. If you use this back-end in production, make sure to consider the state file as a secret.
+First, create a `provider.tf` file with the minimum version, the European endpoint (“ovh-eu”) and the keys you obtained in this guide.
 
-### Automating Object Storage policies with Terraform
-
-#### Initialize
-
-Clone the repository:
+Terraform:
 
 ```bash
-git clone https://github.com/yomovh/tf-at-ovhcloud && cd tf-at-ovhcloud/s3_policy
+terraform {
+  required_providers {
+    ovh = {
+      source  = "ovh/ovh"
+      version = "2.1.0" # greater than or equal to 2.0
+    }
+  }
+}
+
+provider "ovh" {
+  endpoint           = "ovh-eu"
+  application_key    = "<your_access_key>"
+  application_secret = "<your_application_secret>"
+  consumer_key       = "<your_consumer_key>"
+}
 ```
 
-Initialize Terraform:
-
-```bash
-$ terraform init
+Here, we've defined the `ovh-eu` endpoint because we want to call the OVHcloud Europe API, but other endpoints exist, depending on your needs:
+
+- `ovh-eu` pour OVHcloud Europe API
+- `ovh-us` pour OVHcloud US API
+- `ovh-ca` pour OVHcloud North-America API
+
+### Create a bucket
+
+You can create a file named 'object_storage_simple.tf' and write the following:
+
+```python
+# Create an Object Storage bucket
+resource "ovh_cloud_project_storage" "my-bucket" {
+ service_name = "my_service_name" # Replace with your OVHcloud project ID
+ region_name = "GRA" # Replace with the desired region in uppercase.
+  name = "object-storage-simple"
+  versioning = {
+    status = "enabled"
+  }
+  encryption = {
+    sse_algorithm = "AES256"
+  }
+}
 ```
 
-#### Plan
-
-With the following command, you will see what are the actions that Terraform is going to perform:
+You can create your resource by entering the following command:
 
 ```bash
-$ terraform plan
+terraform apply
 ```
 
-Now let's have a look at the content of the `main.tf` file and compare it with the previous example:
+### Delete a bucket
 
-- The *User / Credential* block defines 3 users and credentials : one user will be administrator of the bucket and create it, the two others will have read/write & read-only access.
-- In the *Bucket* block we have added the creation of a file into the bucket
-- The *Policy* block defines 2 policies, one for read/write and the other for read-only on the bucket.
-
-#### Run
+You can delete your bucket and all the objects it contains by entering the following command:
 
 ```bash
-$ terraform apply
+terraform destroy
 ```
 
-Now you can go in the Console and check the "Object Storage" tab. You will see the bucket and the file.
-
-You can also check the access right by using the AWS CLI with the 2 users that have the read / write & read-only access
-
-#### Destroy
-
-With the following command you will be back to your original state: Terraform will destroy all the resources that were previously created.
-
-```bash
-$ terraform destroy
-```
+> [!primary]
+>
+> This process may fail if the bucket contains locked objects. In this case, you'll need to delete these objects manually before you can run the command again.
+>
 
 ## Go further
 
diff --git a/pages/storage_and_backup/object_storage/s3_terraform/guide.en-ca.md b/pages/storage_and_backup/object_storage/s3_terraform/guide.en-ca.md
index cfcf00711ba..70caaa12e80 100644
--- a/pages/storage_and_backup/object_storage/s3_terraform/guide.en-ca.md
+++ b/pages/storage_and_backup/object_storage/s3_terraform/guide.en-ca.md
@@ -1,145 +1,116 @@
 ---
 title: Object Storage - Manage an Object Storage bucket with Terraform
-updated: 2024-08-27
+updated: 2025-05-05
 ---
 
 ## Objective
 
-This tutorial will show you how to automate some actions on Object Storage with Terraform which is an open source tool to automate infrastructure provisioning. The following actions will be automated:
-
-- Object Storage user creation
-- bucket creation
-- file copy into the bucket
-- S3 **\*** policies and assignment
+This tutorial will help you automate and orchestrate actions to use the [Object Storage](/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage) - S3* API with Terraform. Terraform is an open source tool for orchestrating the provisioning of resources.
 
 ## Requirements
 
-- Have terraform command line installed (see this [tutorial](https://developer.hashicorp.com/terraform/tutorials/aws-get-started/install-cli) from Hashicorp, the company behind Terraform). 
-- Have git command line installed
-- You will need to have set up an account to interact with the OVHcloud API (see this [tutorial](/pages/manage_and_operate/api/first-steps)). Depending on your needs in terms of permissions (http verbs PUT/GET/POST/DELETE), enter the route `/cloud/project/{serviceName}/region/{regionName}/storage/` to target object storage where *{serviceName}* corresponds to your Public Cloud project id and *{regionName}* corresponds to the region where your resources will be located. From the application keys created, you will need to export the 4 environment variables :
-
-```bash
-$ export OVH_ENDPOINT=ovh-eu
-$ export OVH_APPLICATION_KEY=Your_key_application_OVH(or_AK)
-$ export OVH_APPLICATION_SECRET=Your_secret_application_key_OVH(or_AS)
-$ export OVH_CONSUMER_KEY=Your_token(or_CK)
-```   
-
-- A Public Cloud project, with the ID exported as the variable `TF_VAR_OVH_PUBLIC_CLOUD_PROJECT_ID`
-
-```bash
-$ export TF_VAR_OVH_PUBLIC_CLOUD_PROJECT_ID=Your_public_cloud_project_id
-```
-
-**If you do not have your AWS CLI** configured, you should set dummy values with the following. This is due to a limitation in Terraform dependency graph for providers initialization (see this long lasting terraform [issue)](https://github.com/hashicorp/terraform/issues/2430)):
-
-```bash
-$ export AWS_ACCESS_KEY_ID="no_need_to_define_an_access_key"  
-$ export AWS_SECRET_ACCESS_KEY="no_need_to_define_a_secret_key"
-```
-
-## Instructions
+- Installation of the [Terraform CLI](https://www.terraform.io/downloads.html){.external}
+- Access to the [OVHcloud API](/links/api) (create your login by consulting [this guide](/pages/manage_and_operate/api/first-steps))
+- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account.
+- OVHcloud provides a [Terraform provider](https://registry.terraform.io/providers/ovh/ovh/latest){.external} which is available in the official Terraform registry. You must have installed a version >= 2.0. You can follow this guide [How to use Terraform on the OVHcloud Public Cloud](/pages/public_cloud/compute/how_to_use_terraform).
 
-### Manage an Object Storage bucket with terraform @OVHcloud
+## Getting information on your cluster/API tokens
 
-#### Initialize
+The “OVH provider” must be configured with a set of credentials:
 
-Clone the repository:
+- an `application_key`
+- an `application_secret`
+- a `consumer_key`
 
-```bash
-git clone https://github.com/yomovh/tf-at-ovhcloud && cd tf-at-ovhcloud/s3_bucket_only
-```
+Why?
 
-Initialize Terraform:
+Because, behind the scenes, the OVH Terraform provider makes requests to the OVHcloud APIs.
 
-```bash
-$ terraform init
-```
+To retrieve this necessary information, please follow the tutorial [First steps with the OVHcloud APIs](/pages/manage_and_operate/api/first-steps).
 
-#### Plan
+Once you've successfully generated your OVHcloud tokens, keep them. You'll need to set them in the next few minutes.
 
-With the following command, you will see what are the actions that Terraform is going to perform:
+The last piece of information you'll need is the `service_name`: this is the ID of your Public Cloud project.
 
-```bash
-$ terraform plan
-```
-
-Now let's have a look at the content of the `main.tf` file:
+How do I get it?
 
-- The *variable* block defines the region and s3 endpoint that are used to create the bucket. You can update it according to your needs : check this [page](/pages/storage_and_backup/object_storage/s3_location) to know what region / endpoints are available.
-- The *Providers* block defines 2 providers : ovh and Hashicorp AWS one. The first one is necessary to create the user whose identity / credentials will be used for the latest.
-- The *User / Credential* block defines the user & credential that are visible in the Settings > Users & Roles tab. They are needed to configure the Hashicorp AWS provider.
-- The Bucket block defines the bucket itself.
-- The Output defines the access & secret key that may be useful for CLI usage.
+In the Public Cloud section, you can retrieve your service name ID using the `Copy to clipboard`{.action} button.
 
-#### Run
+![Copy paste service name](images/get-service-name.png){.thumbnail}
 
-```bash
-$ terraform apply
-```
+You can also use this information in Terraform resource definition files.
 
-Now you can go in the Console and check the "Object Storage" tab. Your bucket is created.
-
-#### Destroy
+## Instructions
 
-With the following command you will be back to your original state: Terraform will destroy all the resources that were previously created.
+If you would like to access the provider's documentation on Object Storage, [click here](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage.){.external}
 
-```bash
-$ terraform destroy
-```
+### Configuration
 
-> [!primary]
->
-> - This script does not follow Terraform best practices to split the project in multiple files e.g. **`provider.tf`, `main.tf`, `variables.tf`, `outputs.tf`**, ... This has been done intentionnaly to avoid switching into multiples files for what is a really simple example.
-> - The secret that is created by this script is stored in the [local](https://developer.hashicorp.com/terraform/language/settings/backends/local) state back-end. If you use this back-end in production, make sure to consider the state file as a secret.
+First, create a `provider.tf` file with the minimum version, the European endpoint (“ovh-eu”) and the keys you obtained in this guide.
 
-### Automating Object Storage policies with Terraform
-
-#### Initialize
-
-Clone the repository:
+Terraform:
 
 ```bash
-git clone https://github.com/yomovh/tf-at-ovhcloud && cd tf-at-ovhcloud/s3_policy
+terraform {
+  required_providers {
+    ovh = {
+      source  = "ovh/ovh"
+      version = "2.1.0" # greater than or equal to 2.0
+    }
+  }
+}
+
+provider "ovh" {
+  endpoint           = "ovh-eu"
+  application_key    = "<your_access_key>"
+  application_secret = "<your_application_secret>"
+  consumer_key       = "<your_consumer_key>"
+}
 ```
 
-Initialize Terraform:
-
-```bash
-$ terraform init
+Here, we've defined the `ovh-eu` endpoint because we want to call the OVHcloud Europe API, but other endpoints exist, depending on your needs:
+
+- `ovh-eu` pour OVHcloud Europe API
+- `ovh-us` pour OVHcloud US API
+- `ovh-ca` pour OVHcloud North-America API
+
+### Create a bucket
+
+You can create a file named 'object_storage_simple.tf' and write the following:
+
+```python
+# Create an Object Storage bucket
+resource "ovh_cloud_project_storage" "my-bucket" {
+ service_name = "my_service_name" # Replace with your OVHcloud project ID
+ region_name = "GRA" # Replace with the desired region in uppercase.
+  name = "object-storage-simple"
+  versioning = {
+    status = "enabled"
+  }
+  encryption = {
+    sse_algorithm = "AES256"
+  }
+}
 ```
 
-#### Plan
-
-With the following command, you will see what are the actions that Terraform is going to perform:
+You can create your resource by entering the following command:
 
 ```bash
-$ terraform plan
+terraform apply
 ```
 
-Now let's have a look at the content of the `main.tf` file and compare it with the previous example:
+### Delete a bucket
 
-- The *User / Credential* block defines 3 users and credentials : one user will be administrator of the bucket and create it, the two others will have read/write & read-only access.
-- In the *Bucket* block we have added the creation of a file into the bucket
-- The *Policy* block defines 2 policies, one for read/write and the other for read-only on the bucket.
-
-#### Run
+You can delete your bucket and all the objects it contains by entering the following command:
 
 ```bash
-$ terraform apply
+terraform destroy
 ```
 
-Now you can go in the Console and check the "Object Storage" tab. You will see the bucket and the file.
-
-You can also check the access right by using the AWS CLI with the 2 users that have the read / write & read-only access
-
-#### Destroy
-
-With the following command you will be back to your original state: Terraform will destroy all the resources that were previously created.
-
-```bash
-$ terraform destroy
-```
+> [!primary]
+>
+> This process may fail if the bucket contains locked objects. In this case, you'll need to delete these objects manually before you can run the command again.
+>
 
 ## Go further
 
diff --git a/pages/storage_and_backup/object_storage/s3_terraform/guide.en-gb.md b/pages/storage_and_backup/object_storage/s3_terraform/guide.en-gb.md
index cfcf00711ba..70caaa12e80 100644
--- a/pages/storage_and_backup/object_storage/s3_terraform/guide.en-gb.md
+++ b/pages/storage_and_backup/object_storage/s3_terraform/guide.en-gb.md
@@ -1,145 +1,116 @@
 ---
 title: Object Storage - Manage an Object Storage bucket with Terraform
-updated: 2024-08-27
+updated: 2025-05-05
 ---
 
 ## Objective
 
-This tutorial will show you how to automate some actions on Object Storage with Terraform which is an open source tool to automate infrastructure provisioning. The following actions will be automated:
-
-- Object Storage user creation
-- bucket creation
-- file copy into the bucket
-- S3 **\*** policies and assignment
+This tutorial will help you automate and orchestrate actions to use the [Object Storage](/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage) - S3* API with Terraform. Terraform is an open source tool for orchestrating the provisioning of resources.
 
 ## Requirements
 
-- Have terraform command line installed (see this [tutorial](https://developer.hashicorp.com/terraform/tutorials/aws-get-started/install-cli) from Hashicorp, the company behind Terraform). 
-- Have git command line installed
-- You will need to have set up an account to interact with the OVHcloud API (see this [tutorial](/pages/manage_and_operate/api/first-steps)). Depending on your needs in terms of permissions (http verbs PUT/GET/POST/DELETE), enter the route `/cloud/project/{serviceName}/region/{regionName}/storage/` to target object storage where *{serviceName}* corresponds to your Public Cloud project id and *{regionName}* corresponds to the region where your resources will be located. From the application keys created, you will need to export the 4 environment variables :
-
-```bash
-$ export OVH_ENDPOINT=ovh-eu
-$ export OVH_APPLICATION_KEY=Your_key_application_OVH(or_AK)
-$ export OVH_APPLICATION_SECRET=Your_secret_application_key_OVH(or_AS)
-$ export OVH_CONSUMER_KEY=Your_token(or_CK)
-```   
-
-- A Public Cloud project, with the ID exported as the variable `TF_VAR_OVH_PUBLIC_CLOUD_PROJECT_ID`
-
-```bash
-$ export TF_VAR_OVH_PUBLIC_CLOUD_PROJECT_ID=Your_public_cloud_project_id
-```
-
-**If you do not have your AWS CLI** configured, you should set dummy values with the following. This is due to a limitation in Terraform dependency graph for providers initialization (see this long lasting terraform [issue)](https://github.com/hashicorp/terraform/issues/2430)):
-
-```bash
-$ export AWS_ACCESS_KEY_ID="no_need_to_define_an_access_key"  
-$ export AWS_SECRET_ACCESS_KEY="no_need_to_define_a_secret_key"
-```
-
-## Instructions
+- Installation of the [Terraform CLI](https://www.terraform.io/downloads.html){.external}
+- Access to the [OVHcloud API](/links/api) (create your login by consulting [this guide](/pages/manage_and_operate/api/first-steps))
+- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account.
+- OVHcloud provides a [Terraform provider](https://registry.terraform.io/providers/ovh/ovh/latest){.external} which is available in the official Terraform registry. You must have installed a version >= 2.0. You can follow this guide [How to use Terraform on the OVHcloud Public Cloud](/pages/public_cloud/compute/how_to_use_terraform).
 
-### Manage an Object Storage bucket with terraform @OVHcloud
+## Getting information on your cluster/API tokens
 
-#### Initialize
+The “OVH provider” must be configured with a set of credentials:
 
-Clone the repository:
+- an `application_key`
+- an `application_secret`
+- a `consumer_key`
 
-```bash
-git clone https://github.com/yomovh/tf-at-ovhcloud && cd tf-at-ovhcloud/s3_bucket_only
-```
+Why?
 
-Initialize Terraform:
+Because, behind the scenes, the OVH Terraform provider makes requests to the OVHcloud APIs.
 
-```bash
-$ terraform init
-```
+To retrieve this necessary information, please follow the tutorial [First steps with the OVHcloud APIs](/pages/manage_and_operate/api/first-steps).
 
-#### Plan
+Once you've successfully generated your OVHcloud tokens, keep them. You'll need to set them in the next few minutes.
 
-With the following command, you will see what are the actions that Terraform is going to perform:
+The last piece of information you'll need is the `service_name`: this is the ID of your Public Cloud project.
 
-```bash
-$ terraform plan
-```
-
-Now let's have a look at the content of the `main.tf` file:
+How do I get it?
 
-- The *variable* block defines the region and s3 endpoint that are used to create the bucket. You can update it according to your needs : check this [page](/pages/storage_and_backup/object_storage/s3_location) to know what region / endpoints are available.
-- The *Providers* block defines 2 providers : ovh and Hashicorp AWS one. The first one is necessary to create the user whose identity / credentials will be used for the latest.
-- The *User / Credential* block defines the user & credential that are visible in the Settings > Users & Roles tab. They are needed to configure the Hashicorp AWS provider.
-- The Bucket block defines the bucket itself.
-- The Output defines the access & secret key that may be useful for CLI usage.
+In the Public Cloud section, you can retrieve your service name ID using the `Copy to clipboard`{.action} button.
 
-#### Run
+![Copy paste service name](images/get-service-name.png){.thumbnail}
 
-```bash
-$ terraform apply
-```
+You can also use this information in Terraform resource definition files.
 
-Now you can go in the Console and check the "Object Storage" tab. Your bucket is created.
-
-#### Destroy
+## Instructions
 
-With the following command you will be back to your original state: Terraform will destroy all the resources that were previously created.
+If you would like to access the provider's documentation on Object Storage, [click here](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage.){.external}
 
-```bash
-$ terraform destroy
-```
+### Configuration
 
-> [!primary]
->
-> - This script does not follow Terraform best practices to split the project in multiple files e.g. **`provider.tf`, `main.tf`, `variables.tf`, `outputs.tf`**, ... This has been done intentionnaly to avoid switching into multiples files for what is a really simple example.
-> - The secret that is created by this script is stored in the [local](https://developer.hashicorp.com/terraform/language/settings/backends/local) state back-end. If you use this back-end in production, make sure to consider the state file as a secret.
+First, create a `provider.tf` file with the minimum version, the European endpoint (“ovh-eu”) and the keys you obtained in this guide.
 
-### Automating Object Storage policies with Terraform
-
-#### Initialize
-
-Clone the repository:
+Terraform:
 
 ```bash
-git clone https://github.com/yomovh/tf-at-ovhcloud && cd tf-at-ovhcloud/s3_policy
+terraform {
+  required_providers {
+    ovh = {
+      source  = "ovh/ovh"
+      version = "2.1.0" # greater than or equal to 2.0
+    }
+  }
+}
+
+provider "ovh" {
+  endpoint           = "ovh-eu"
+  application_key    = "<your_access_key>"
+  application_secret = "<your_application_secret>"
+  consumer_key       = "<your_consumer_key>"
+}
 ```
 
-Initialize Terraform:
-
-```bash
-$ terraform init
+Here, we've defined the `ovh-eu` endpoint because we want to call the OVHcloud Europe API, but other endpoints exist, depending on your needs:
+
+- `ovh-eu` pour OVHcloud Europe API
+- `ovh-us` pour OVHcloud US API
+- `ovh-ca` pour OVHcloud North-America API
+
+### Create a bucket
+
+You can create a file named 'object_storage_simple.tf' and write the following:
+
+```python
+# Create an Object Storage bucket
+resource "ovh_cloud_project_storage" "my-bucket" {
+ service_name = "my_service_name" # Replace with your OVHcloud project ID
+ region_name = "GRA" # Replace with the desired region in uppercase.
+  name = "object-storage-simple"
+  versioning = {
+    status = "enabled"
+  }
+  encryption = {
+    sse_algorithm = "AES256"
+  }
+}
 ```
 
-#### Plan
-
-With the following command, you will see what are the actions that Terraform is going to perform:
+You can create your resource by entering the following command:
 
 ```bash
-$ terraform plan
+terraform apply
 ```
 
-Now let's have a look at the content of the `main.tf` file and compare it with the previous example:
+### Delete a bucket
 
-- The *User / Credential* block defines 3 users and credentials : one user will be administrator of the bucket and create it, the two others will have read/write & read-only access.
-- In the *Bucket* block we have added the creation of a file into the bucket
-- The *Policy* block defines 2 policies, one for read/write and the other for read-only on the bucket.
-
-#### Run
+You can delete your bucket and all the objects it contains by entering the following command:
 
 ```bash
-$ terraform apply
+terraform destroy
 ```
 
-Now you can go in the Console and check the "Object Storage" tab. You will see the bucket and the file.
-
-You can also check the access right by using the AWS CLI with the 2 users that have the read / write & read-only access
-
-#### Destroy
-
-With the following command you will be back to your original state: Terraform will destroy all the resources that were previously created.
-
-```bash
-$ terraform destroy
-```
+> [!primary]
+>
+> This process may fail if the bucket contains locked objects. In this case, you'll need to delete these objects manually before you can run the command again.
+>
 
 ## Go further
 
diff --git a/pages/storage_and_backup/object_storage/s3_terraform/guide.en-ie.md b/pages/storage_and_backup/object_storage/s3_terraform/guide.en-ie.md
index cfcf00711ba..70caaa12e80 100644
--- a/pages/storage_and_backup/object_storage/s3_terraform/guide.en-ie.md
+++ b/pages/storage_and_backup/object_storage/s3_terraform/guide.en-ie.md
@@ -1,145 +1,116 @@
 ---
 title: Object Storage - Manage an Object Storage bucket with Terraform
-updated: 2024-08-27
+updated: 2025-05-05
 ---
 
 ## Objective
 
-This tutorial will show you how to automate some actions on Object Storage with Terraform which is an open source tool to automate infrastructure provisioning. The following actions will be automated:
-
-- Object Storage user creation
-- bucket creation
-- file copy into the bucket
-- S3 **\*** policies and assignment
+This tutorial will help you automate and orchestrate actions to use the [Object Storage](/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage) - S3* API with Terraform. Terraform is an open source tool for orchestrating the provisioning of resources.
 
 ## Requirements
 
-- Have terraform command line installed (see this [tutorial](https://developer.hashicorp.com/terraform/tutorials/aws-get-started/install-cli) from Hashicorp, the company behind Terraform). 
-- Have git command line installed
-- You will need to have set up an account to interact with the OVHcloud API (see this [tutorial](/pages/manage_and_operate/api/first-steps)). Depending on your needs in terms of permissions (http verbs PUT/GET/POST/DELETE), enter the route `/cloud/project/{serviceName}/region/{regionName}/storage/` to target object storage where *{serviceName}* corresponds to your Public Cloud project id and *{regionName}* corresponds to the region where your resources will be located. From the application keys created, you will need to export the 4 environment variables :
-
-```bash
-$ export OVH_ENDPOINT=ovh-eu
-$ export OVH_APPLICATION_KEY=Your_key_application_OVH(or_AK)
-$ export OVH_APPLICATION_SECRET=Your_secret_application_key_OVH(or_AS)
-$ export OVH_CONSUMER_KEY=Your_token(or_CK)
-```   
-
-- A Public Cloud project, with the ID exported as the variable `TF_VAR_OVH_PUBLIC_CLOUD_PROJECT_ID`
-
-```bash
-$ export TF_VAR_OVH_PUBLIC_CLOUD_PROJECT_ID=Your_public_cloud_project_id
-```
-
-**If you do not have your AWS CLI** configured, you should set dummy values with the following. This is due to a limitation in Terraform dependency graph for providers initialization (see this long lasting terraform [issue)](https://github.com/hashicorp/terraform/issues/2430)):
-
-```bash
-$ export AWS_ACCESS_KEY_ID="no_need_to_define_an_access_key"  
-$ export AWS_SECRET_ACCESS_KEY="no_need_to_define_a_secret_key"
-```
-
-## Instructions
+- Installation of the [Terraform CLI](https://www.terraform.io/downloads.html){.external}
+- Access to the [OVHcloud API](/links/api) (create your login by consulting [this guide](/pages/manage_and_operate/api/first-steps))
+- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account.
+- OVHcloud provides a [Terraform provider](https://registry.terraform.io/providers/ovh/ovh/latest){.external} which is available in the official Terraform registry. You must have installed a version >= 2.0. You can follow this guide [How to use Terraform on the OVHcloud Public Cloud](/pages/public_cloud/compute/how_to_use_terraform).
 
-### Manage an Object Storage bucket with terraform @OVHcloud
+## Getting information on your cluster/API tokens
 
-#### Initialize
+The “OVH provider” must be configured with a set of credentials:
 
-Clone the repository:
+- an `application_key`
+- an `application_secret`
+- a `consumer_key`
 
-```bash
-git clone https://github.com/yomovh/tf-at-ovhcloud && cd tf-at-ovhcloud/s3_bucket_only
-```
+Why?
 
-Initialize Terraform:
+Because, behind the scenes, the OVH Terraform provider makes requests to the OVHcloud APIs.
 
-```bash
-$ terraform init
-```
+To retrieve this necessary information, please follow the tutorial [First steps with the OVHcloud APIs](/pages/manage_and_operate/api/first-steps).
 
-#### Plan
+Once you've successfully generated your OVHcloud tokens, keep them. You'll need to set them in the next few minutes.
 
-With the following command, you will see what are the actions that Terraform is going to perform:
+The last piece of information you'll need is the `service_name`: this is the ID of your Public Cloud project.
 
-```bash
-$ terraform plan
-```
-
-Now let's have a look at the content of the `main.tf` file:
+How do I get it?
 
-- The *variable* block defines the region and s3 endpoint that are used to create the bucket. You can update it according to your needs : check this [page](/pages/storage_and_backup/object_storage/s3_location) to know what region / endpoints are available.
-- The *Providers* block defines 2 providers : ovh and Hashicorp AWS one. The first one is necessary to create the user whose identity / credentials will be used for the latest.
-- The *User / Credential* block defines the user & credential that are visible in the Settings > Users & Roles tab. They are needed to configure the Hashicorp AWS provider.
-- The Bucket block defines the bucket itself.
-- The Output defines the access & secret key that may be useful for CLI usage.
+In the Public Cloud section, you can retrieve your service name ID using the `Copy to clipboard`{.action} button.
 
-#### Run
+![Copy paste service name](images/get-service-name.png){.thumbnail}
 
-```bash
-$ terraform apply
-```
+You can also use this information in Terraform resource definition files.
 
-Now you can go in the Console and check the "Object Storage" tab. Your bucket is created.
-
-#### Destroy
+## Instructions
 
-With the following command you will be back to your original state: Terraform will destroy all the resources that were previously created.
+If you would like to access the provider's documentation on Object Storage, [click here](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage.){.external}
 
-```bash
-$ terraform destroy
-```
+### Configuration
 
-> [!primary]
->
-> - This script does not follow Terraform best practices to split the project in multiple files e.g. **`provider.tf`, `main.tf`, `variables.tf`, `outputs.tf`**, ... This has been done intentionnaly to avoid switching into multiples files for what is a really simple example.
-> - The secret that is created by this script is stored in the [local](https://developer.hashicorp.com/terraform/language/settings/backends/local) state back-end. If you use this back-end in production, make sure to consider the state file as a secret.
+First, create a `provider.tf` file with the minimum version, the European endpoint (“ovh-eu”) and the keys you obtained in this guide.
 
-### Automating Object Storage policies with Terraform
-
-#### Initialize
-
-Clone the repository:
+Terraform:
 
 ```bash
-git clone https://github.com/yomovh/tf-at-ovhcloud && cd tf-at-ovhcloud/s3_policy
+terraform {
+  required_providers {
+    ovh = {
+      source  = "ovh/ovh"
+      version = "2.1.0" # greater than or equal to 2.0
+    }
+  }
+}
+
+provider "ovh" {
+  endpoint           = "ovh-eu"
+  application_key    = "<your_access_key>"
+  application_secret = "<your_application_secret>"
+  consumer_key       = "<your_consumer_key>"
+}
 ```
 
-Initialize Terraform:
-
-```bash
-$ terraform init
+Here, we've defined the `ovh-eu` endpoint because we want to call the OVHcloud Europe API, but other endpoints exist, depending on your needs:
+
+- `ovh-eu` pour OVHcloud Europe API
+- `ovh-us` pour OVHcloud US API
+- `ovh-ca` pour OVHcloud North-America API
+
+### Create a bucket
+
+You can create a file named 'object_storage_simple.tf' and write the following:
+
+```python
+# Create an Object Storage bucket
+resource "ovh_cloud_project_storage" "my-bucket" {
+ service_name = "my_service_name" # Replace with your OVHcloud project ID
+ region_name = "GRA" # Replace with the desired region in uppercase.
+  name = "object-storage-simple"
+  versioning = {
+    status = "enabled"
+  }
+  encryption = {
+    sse_algorithm = "AES256"
+  }
+}
 ```
 
-#### Plan
-
-With the following command, you will see what are the actions that Terraform is going to perform:
+You can create your resource by entering the following command:
 
 ```bash
-$ terraform plan
+terraform apply
 ```
 
-Now let's have a look at the content of the `main.tf` file and compare it with the previous example:
+### Delete a bucket
 
-- The *User / Credential* block defines 3 users and credentials : one user will be administrator of the bucket and create it, the two others will have read/write & read-only access.
-- In the *Bucket* block we have added the creation of a file into the bucket
-- The *Policy* block defines 2 policies, one for read/write and the other for read-only on the bucket.
-
-#### Run
+You can delete your bucket and all the objects it contains by entering the following command:
 
 ```bash
-$ terraform apply
+terraform destroy
 ```
 
-Now you can go in the Console and check the "Object Storage" tab. You will see the bucket and the file.
-
-You can also check the access right by using the AWS CLI with the 2 users that have the read / write & read-only access
-
-#### Destroy
-
-With the following command you will be back to your original state: Terraform will destroy all the resources that were previously created.
-
-```bash
-$ terraform destroy
-```
+> [!primary]
+>
+> This process may fail if the bucket contains locked objects. In this case, you'll need to delete these objects manually before you can run the command again.
+>
 
 ## Go further
 
diff --git a/pages/storage_and_backup/object_storage/s3_terraform/guide.en-sg.md b/pages/storage_and_backup/object_storage/s3_terraform/guide.en-sg.md
index cfcf00711ba..70caaa12e80 100644
--- a/pages/storage_and_backup/object_storage/s3_terraform/guide.en-sg.md
+++ b/pages/storage_and_backup/object_storage/s3_terraform/guide.en-sg.md
@@ -1,145 +1,116 @@
 ---
 title: Object Storage - Manage an Object Storage bucket with Terraform
-updated: 2024-08-27
+updated: 2025-05-05
 ---
 
 ## Objective
 
-This tutorial will show you how to automate some actions on Object Storage with Terraform which is an open source tool to automate infrastructure provisioning. The following actions will be automated:
-
-- Object Storage user creation
-- bucket creation
-- file copy into the bucket
-- S3 **\*** policies and assignment
+This tutorial will help you automate and orchestrate actions to use the [Object Storage](/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage) - S3* API with Terraform. Terraform is an open source tool for orchestrating the provisioning of resources.
 
 ## Requirements
 
-- Have terraform command line installed (see this [tutorial](https://developer.hashicorp.com/terraform/tutorials/aws-get-started/install-cli) from Hashicorp, the company behind Terraform). 
-- Have git command line installed
-- You will need to have set up an account to interact with the OVHcloud API (see this [tutorial](/pages/manage_and_operate/api/first-steps)). Depending on your needs in terms of permissions (http verbs PUT/GET/POST/DELETE), enter the route `/cloud/project/{serviceName}/region/{regionName}/storage/` to target object storage where *{serviceName}* corresponds to your Public Cloud project id and *{regionName}* corresponds to the region where your resources will be located. From the application keys created, you will need to export the 4 environment variables :
-
-```bash
-$ export OVH_ENDPOINT=ovh-eu
-$ export OVH_APPLICATION_KEY=Your_key_application_OVH(or_AK)
-$ export OVH_APPLICATION_SECRET=Your_secret_application_key_OVH(or_AS)
-$ export OVH_CONSUMER_KEY=Your_token(or_CK)
-```   
-
-- A Public Cloud project, with the ID exported as the variable `TF_VAR_OVH_PUBLIC_CLOUD_PROJECT_ID`
-
-```bash
-$ export TF_VAR_OVH_PUBLIC_CLOUD_PROJECT_ID=Your_public_cloud_project_id
-```
-
-**If you do not have your AWS CLI** configured, you should set dummy values with the following. This is due to a limitation in Terraform dependency graph for providers initialization (see this long lasting terraform [issue)](https://github.com/hashicorp/terraform/issues/2430)):
-
-```bash
-$ export AWS_ACCESS_KEY_ID="no_need_to_define_an_access_key"  
-$ export AWS_SECRET_ACCESS_KEY="no_need_to_define_a_secret_key"
-```
-
-## Instructions
+- Installation of the [Terraform CLI](https://www.terraform.io/downloads.html){.external}
+- Access to the [OVHcloud API](/links/api) (create your login by consulting [this guide](/pages/manage_and_operate/api/first-steps))
+- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account.
+- OVHcloud provides a [Terraform provider](https://registry.terraform.io/providers/ovh/ovh/latest){.external} which is available in the official Terraform registry. You must have installed a version >= 2.0. You can follow this guide [How to use Terraform on the OVHcloud Public Cloud](/pages/public_cloud/compute/how_to_use_terraform).
 
-### Manage an Object Storage bucket with terraform @OVHcloud
+## Getting information on your cluster/API tokens
 
-#### Initialize
+The “OVH provider” must be configured with a set of credentials:
 
-Clone the repository:
+- an `application_key`
+- an `application_secret`
+- a `consumer_key`
 
-```bash
-git clone https://github.com/yomovh/tf-at-ovhcloud && cd tf-at-ovhcloud/s3_bucket_only
-```
+Why?
 
-Initialize Terraform:
+Because, behind the scenes, the OVH Terraform provider makes requests to the OVHcloud APIs.
 
-```bash
-$ terraform init
-```
+To retrieve this necessary information, please follow the tutorial [First steps with the OVHcloud APIs](/pages/manage_and_operate/api/first-steps).
 
-#### Plan
+Once you've successfully generated your OVHcloud tokens, keep them. You'll need to set them in the next few minutes.
 
-With the following command, you will see what are the actions that Terraform is going to perform:
+The last piece of information you'll need is the `service_name`: this is the ID of your Public Cloud project.
 
-```bash
-$ terraform plan
-```
-
-Now let's have a look at the content of the `main.tf` file:
+How do I get it?
 
-- The *variable* block defines the region and s3 endpoint that are used to create the bucket. You can update it according to your needs : check this [page](/pages/storage_and_backup/object_storage/s3_location) to know what region / endpoints are available.
-- The *Providers* block defines 2 providers : ovh and Hashicorp AWS one. The first one is necessary to create the user whose identity / credentials will be used for the latest.
-- The *User / Credential* block defines the user & credential that are visible in the Settings > Users & Roles tab. They are needed to configure the Hashicorp AWS provider.
-- The Bucket block defines the bucket itself.
-- The Output defines the access & secret key that may be useful for CLI usage.
+In the Public Cloud section, you can retrieve your service name ID using the `Copy to clipboard`{.action} button.
 
-#### Run
+![Copy paste service name](images/get-service-name.png){.thumbnail}
 
-```bash
-$ terraform apply
-```
+You can also use this information in Terraform resource definition files.
 
-Now you can go in the Console and check the "Object Storage" tab. Your bucket is created.
-
-#### Destroy
+## Instructions
 
-With the following command you will be back to your original state: Terraform will destroy all the resources that were previously created.
+If you would like to access the provider's documentation on Object Storage, [click here](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage.){.external}
 
-```bash
-$ terraform destroy
-```
+### Configuration
 
-> [!primary]
->
-> - This script does not follow Terraform best practices to split the project in multiple files e.g. **`provider.tf`, `main.tf`, `variables.tf`, `outputs.tf`**, ... This has been done intentionnaly to avoid switching into multiples files for what is a really simple example.
-> - The secret that is created by this script is stored in the [local](https://developer.hashicorp.com/terraform/language/settings/backends/local) state back-end. If you use this back-end in production, make sure to consider the state file as a secret.
+First, create a `provider.tf` file with the minimum version, the European endpoint (“ovh-eu”) and the keys you obtained in this guide.
 
-### Automating Object Storage policies with Terraform
-
-#### Initialize
-
-Clone the repository:
+Terraform:
 
 ```bash
-git clone https://github.com/yomovh/tf-at-ovhcloud && cd tf-at-ovhcloud/s3_policy
+terraform {
+  required_providers {
+    ovh = {
+      source  = "ovh/ovh"
+      version = "2.1.0" # greater than or equal to 2.0
+    }
+  }
+}
+
+provider "ovh" {
+  endpoint           = "ovh-eu"
+  application_key    = "<your_access_key>"
+  application_secret = "<your_application_secret>"
+  consumer_key       = "<your_consumer_key>"
+}
 ```
 
-Initialize Terraform:
-
-```bash
-$ terraform init
+Here, we've defined the `ovh-eu` endpoint because we want to call the OVHcloud Europe API, but other endpoints exist, depending on your needs:
+
+- `ovh-eu` pour OVHcloud Europe API
+- `ovh-us` pour OVHcloud US API
+- `ovh-ca` pour OVHcloud North-America API
+
+### Create a bucket
+
+You can create a file named 'object_storage_simple.tf' and write the following:
+
+```python
+# Create an Object Storage bucket
+resource "ovh_cloud_project_storage" "my-bucket" {
+ service_name = "my_service_name" # Replace with your OVHcloud project ID
+ region_name = "GRA" # Replace with the desired region in uppercase.
+  name = "object-storage-simple"
+  versioning = {
+    status = "enabled"
+  }
+  encryption = {
+    sse_algorithm = "AES256"
+  }
+}
 ```
 
-#### Plan
-
-With the following command, you will see what are the actions that Terraform is going to perform:
+You can create your resource by entering the following command:
 
 ```bash
-$ terraform plan
+terraform apply
 ```
 
-Now let's have a look at the content of the `main.tf` file and compare it with the previous example:
+### Delete a bucket
 
-- The *User / Credential* block defines 3 users and credentials : one user will be administrator of the bucket and create it, the two others will have read/write & read-only access.
-- In the *Bucket* block we have added the creation of a file into the bucket
-- The *Policy* block defines 2 policies, one for read/write and the other for read-only on the bucket.
-
-#### Run
+You can delete your bucket and all the objects it contains by entering the following command:
 
 ```bash
-$ terraform apply
+terraform destroy
 ```
 
-Now you can go in the Console and check the "Object Storage" tab. You will see the bucket and the file.
-
-You can also check the access right by using the AWS CLI with the 2 users that have the read / write & read-only access
-
-#### Destroy
-
-With the following command you will be back to your original state: Terraform will destroy all the resources that were previously created.
-
-```bash
-$ terraform destroy
-```
+> [!primary]
+>
+> This process may fail if the bucket contains locked objects. In this case, you'll need to delete these objects manually before you can run the command again.
+>
 
 ## Go further
 
diff --git a/pages/storage_and_backup/object_storage/s3_terraform/guide.en-us.md b/pages/storage_and_backup/object_storage/s3_terraform/guide.en-us.md
index cfcf00711ba..70caaa12e80 100644
--- a/pages/storage_and_backup/object_storage/s3_terraform/guide.en-us.md
+++ b/pages/storage_and_backup/object_storage/s3_terraform/guide.en-us.md
@@ -1,145 +1,116 @@
 ---
 title: Object Storage - Manage an Object Storage bucket with Terraform
-updated: 2024-08-27
+updated: 2025-05-05
 ---
 
 ## Objective
 
-This tutorial will show you how to automate some actions on Object Storage with Terraform which is an open source tool to automate infrastructure provisioning. The following actions will be automated:
-
-- Object Storage user creation
-- bucket creation
-- file copy into the bucket
-- S3 **\*** policies and assignment
+This tutorial will help you automate and orchestrate actions to use the [Object Storage](/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage) - S3* API with Terraform. Terraform is an open source tool for orchestrating the provisioning of resources.
 
 ## Requirements
 
-- Have terraform command line installed (see this [tutorial](https://developer.hashicorp.com/terraform/tutorials/aws-get-started/install-cli) from Hashicorp, the company behind Terraform). 
-- Have git command line installed
-- You will need to have set up an account to interact with the OVHcloud API (see this [tutorial](/pages/manage_and_operate/api/first-steps)). Depending on your needs in terms of permissions (http verbs PUT/GET/POST/DELETE), enter the route `/cloud/project/{serviceName}/region/{regionName}/storage/` to target object storage where *{serviceName}* corresponds to your Public Cloud project id and *{regionName}* corresponds to the region where your resources will be located. From the application keys created, you will need to export the 4 environment variables :
-
-```bash
-$ export OVH_ENDPOINT=ovh-eu
-$ export OVH_APPLICATION_KEY=Your_key_application_OVH(or_AK)
-$ export OVH_APPLICATION_SECRET=Your_secret_application_key_OVH(or_AS)
-$ export OVH_CONSUMER_KEY=Your_token(or_CK)
-```   
-
-- A Public Cloud project, with the ID exported as the variable `TF_VAR_OVH_PUBLIC_CLOUD_PROJECT_ID`
-
-```bash
-$ export TF_VAR_OVH_PUBLIC_CLOUD_PROJECT_ID=Your_public_cloud_project_id
-```
-
-**If you do not have your AWS CLI** configured, you should set dummy values with the following. This is due to a limitation in Terraform dependency graph for providers initialization (see this long lasting terraform [issue)](https://github.com/hashicorp/terraform/issues/2430)):
-
-```bash
-$ export AWS_ACCESS_KEY_ID="no_need_to_define_an_access_key"  
-$ export AWS_SECRET_ACCESS_KEY="no_need_to_define_a_secret_key"
-```
-
-## Instructions
+- Installation of the [Terraform CLI](https://www.terraform.io/downloads.html){.external}
+- Access to the [OVHcloud API](/links/api) (create your login by consulting [this guide](/pages/manage_and_operate/api/first-steps))
+- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account.
+- OVHcloud provides a [Terraform provider](https://registry.terraform.io/providers/ovh/ovh/latest){.external} which is available in the official Terraform registry. You must have installed a version >= 2.0. You can follow this guide [How to use Terraform on the OVHcloud Public Cloud](/pages/public_cloud/compute/how_to_use_terraform).
 
-### Manage an Object Storage bucket with terraform @OVHcloud
+## Getting information on your cluster/API tokens
 
-#### Initialize
+The “OVH provider” must be configured with a set of credentials:
 
-Clone the repository:
+- an `application_key`
+- an `application_secret`
+- a `consumer_key`
 
-```bash
-git clone https://github.com/yomovh/tf-at-ovhcloud && cd tf-at-ovhcloud/s3_bucket_only
-```
+Why?
 
-Initialize Terraform:
+Because, behind the scenes, the OVH Terraform provider makes requests to the OVHcloud APIs.
 
-```bash
-$ terraform init
-```
+To retrieve this necessary information, please follow the tutorial [First steps with the OVHcloud APIs](/pages/manage_and_operate/api/first-steps).
 
-#### Plan
+Once you've successfully generated your OVHcloud tokens, keep them. You'll need to set them in the next few minutes.
 
-With the following command, you will see what are the actions that Terraform is going to perform:
+The last piece of information you'll need is the `service_name`: this is the ID of your Public Cloud project.
 
-```bash
-$ terraform plan
-```
-
-Now let's have a look at the content of the `main.tf` file:
+How do I get it?
 
-- The *variable* block defines the region and s3 endpoint that are used to create the bucket. You can update it according to your needs : check this [page](/pages/storage_and_backup/object_storage/s3_location) to know what region / endpoints are available.
-- The *Providers* block defines 2 providers : ovh and Hashicorp AWS one. The first one is necessary to create the user whose identity / credentials will be used for the latest.
-- The *User / Credential* block defines the user & credential that are visible in the Settings > Users & Roles tab. They are needed to configure the Hashicorp AWS provider.
-- The Bucket block defines the bucket itself.
-- The Output defines the access & secret key that may be useful for CLI usage.
+In the Public Cloud section, you can retrieve your service name ID using the `Copy to clipboard`{.action} button.
 
-#### Run
+![Copy paste service name](images/get-service-name.png){.thumbnail}
 
-```bash
-$ terraform apply
-```
+You can also use this information in Terraform resource definition files.
 
-Now you can go in the Console and check the "Object Storage" tab. Your bucket is created.
-
-#### Destroy
+## Instructions
 
-With the following command you will be back to your original state: Terraform will destroy all the resources that were previously created.
+If you would like to access the provider's documentation on Object Storage, [click here](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage.){.external}
 
-```bash
-$ terraform destroy
-```
+### Configuration
 
-> [!primary]
->
-> - This script does not follow Terraform best practices to split the project in multiple files e.g. **`provider.tf`, `main.tf`, `variables.tf`, `outputs.tf`**, ... This has been done intentionnaly to avoid switching into multiples files for what is a really simple example.
-> - The secret that is created by this script is stored in the [local](https://developer.hashicorp.com/terraform/language/settings/backends/local) state back-end. If you use this back-end in production, make sure to consider the state file as a secret.
+First, create a `provider.tf` file with the minimum version, the European endpoint (“ovh-eu”) and the keys you obtained in this guide.
 
-### Automating Object Storage policies with Terraform
-
-#### Initialize
-
-Clone the repository:
+Terraform:
 
 ```bash
-git clone https://github.com/yomovh/tf-at-ovhcloud && cd tf-at-ovhcloud/s3_policy
+terraform {
+  required_providers {
+    ovh = {
+      source  = "ovh/ovh"
+      version = "2.1.0" # greater than or equal to 2.0
+    }
+  }
+}
+
+provider "ovh" {
+  endpoint           = "ovh-eu"
+  application_key    = "<your_access_key>"
+  application_secret = "<your_application_secret>"
+  consumer_key       = "<your_consumer_key>"
+}
 ```
 
-Initialize Terraform:
-
-```bash
-$ terraform init
+Here, we've defined the `ovh-eu` endpoint because we want to call the OVHcloud Europe API, but other endpoints exist, depending on your needs:
+
+- `ovh-eu` pour OVHcloud Europe API
+- `ovh-us` pour OVHcloud US API
+- `ovh-ca` pour OVHcloud North-America API
+
+### Create a bucket
+
+You can create a file named 'object_storage_simple.tf' and write the following:
+
+```python
+# Create an Object Storage bucket
+resource "ovh_cloud_project_storage" "my-bucket" {
+ service_name = "my_service_name" # Replace with your OVHcloud project ID
+ region_name = "GRA" # Replace with the desired region in uppercase.
+  name = "object-storage-simple"
+  versioning = {
+    status = "enabled"
+  }
+  encryption = {
+    sse_algorithm = "AES256"
+  }
+}
 ```
 
-#### Plan
-
-With the following command, you will see what are the actions that Terraform is going to perform:
+You can create your resource by entering the following command:
 
 ```bash
-$ terraform plan
+terraform apply
 ```
 
-Now let's have a look at the content of the `main.tf` file and compare it with the previous example:
+### Delete a bucket
 
-- The *User / Credential* block defines 3 users and credentials : one user will be administrator of the bucket and create it, the two others will have read/write & read-only access.
-- In the *Bucket* block we have added the creation of a file into the bucket
-- The *Policy* block defines 2 policies, one for read/write and the other for read-only on the bucket.
-
-#### Run
+You can delete your bucket and all the objects it contains by entering the following command:
 
 ```bash
-$ terraform apply
+terraform destroy
 ```
 
-Now you can go in the Console and check the "Object Storage" tab. You will see the bucket and the file.
-
-You can also check the access right by using the AWS CLI with the 2 users that have the read / write & read-only access
-
-#### Destroy
-
-With the following command you will be back to your original state: Terraform will destroy all the resources that were previously created.
-
-```bash
-$ terraform destroy
-```
+> [!primary]
+>
+> This process may fail if the bucket contains locked objects. In this case, you'll need to delete these objects manually before you can run the command again.
+>
 
 ## Go further
 
diff --git a/pages/storage_and_backup/object_storage/s3_terraform/guide.es-es.md b/pages/storage_and_backup/object_storage/s3_terraform/guide.es-es.md
index 0f2ac894711..bed0f020749 100644
--- a/pages/storage_and_backup/object_storage/s3_terraform/guide.es-es.md
+++ b/pages/storage_and_backup/object_storage/s3_terraform/guide.es-es.md
@@ -1,145 +1,116 @@
 ---
 title: Object Storage - Administrar un bucket Object Storage con Terraform (EN)
-updated: 2024-08-27
+updated: 2025-05-05
 ---
 
 ## Objective
 
-This tutorial will show you how to automate some actions on Object Storage with Terraform which is an open source tool to automate infrastructure provisioning. The following actions will be automated:
-
-- Object Storage user creation
-- bucket creation
-- file copy into the bucket
-- S3 **\*** policies and assignment
+This tutorial will help you automate and orchestrate actions to use the [Object Storage](/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage) - S3* API with Terraform. Terraform is an open source tool for orchestrating the provisioning of resources.
 
 ## Requirements
 
-- Have terraform command line installed (see this [tutorial](https://developer.hashicorp.com/terraform/tutorials/aws-get-started/install-cli) from Hashicorp, the company behind Terraform). 
-- Have git command line installed
-- You will need to have set up an account to interact with the OVHcloud API (see this [tutorial](/pages/manage_and_operate/api/first-steps)). Depending on your needs in terms of permissions (http verbs PUT/GET/POST/DELETE), enter the route `/cloud/project/{serviceName}/region/{regionName}/storage/` to target object storage where *{serviceName}* corresponds to your Public Cloud project id and *{regionName}* corresponds to the region where your resources will be located. From the application keys created, you will need to export the 4 environment variables :
-
-```bash
-$ export OVH_ENDPOINT=ovh-eu
-$ export OVH_APPLICATION_KEY=Your_key_application_OVH(or_AK)
-$ export OVH_APPLICATION_SECRET=Your_secret_application_key_OVH(or_AS)
-$ export OVH_CONSUMER_KEY=Your_token(or_CK)
-```   
-
-- A Public Cloud project, with the ID exported as the variable `TF_VAR_OVH_PUBLIC_CLOUD_PROJECT_ID`
-
-```bash
-$ export TF_VAR_OVH_PUBLIC_CLOUD_PROJECT_ID=Your_public_cloud_project_id
-```
-
-**If you do not have your AWS CLI** configured, you should set dummy values with the following. This is due to a limitation in Terraform dependency graph for providers initialization (see this long lasting terraform [issue)](https://github.com/hashicorp/terraform/issues/2430)):
-
-```bash
-$ export AWS_ACCESS_KEY_ID="no_need_to_define_an_access_key"  
-$ export AWS_SECRET_ACCESS_KEY="no_need_to_define_a_secret_key"
-```
-
-## Instructions
+- Installation of the [Terraform CLI](https://www.terraform.io/downloads.html){.external}
+- Access to the [OVHcloud API](/links/api) (create your login by consulting [this guide](/pages/manage_and_operate/api/first-steps))
+- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account.
+- OVHcloud provides a [Terraform provider](https://registry.terraform.io/providers/ovh/ovh/latest){.external} which is available in the official Terraform registry. You must have installed a version >= 2.0. You can follow this guide [How to use Terraform on the OVHcloud Public Cloud](/pages/public_cloud/compute/how_to_use_terraform).
 
-### Manage an Object Storage bucket with terraform @OVHcloud
+## Getting information on your cluster/API tokens
 
-#### Initialize
+The “OVH provider” must be configured with a set of credentials:
 
-Clone the repository:
+- an `application_key`
+- an `application_secret`
+- a `consumer_key`
 
-```bash
-git clone https://github.com/yomovh/tf-at-ovhcloud && cd tf-at-ovhcloud/s3_bucket_only
-```
+Why?
 
-Initialize Terraform:
+Because, behind the scenes, the OVH Terraform provider makes requests to the OVHcloud APIs.
 
-```bash
-$ terraform init
-```
+To retrieve this necessary information, please follow the tutorial [First steps with the OVHcloud APIs](/pages/manage_and_operate/api/first-steps).
 
-#### Plan
+Once you've successfully generated your OVHcloud tokens, keep them. You'll need to set them in the next few minutes.
 
-With the following command, you will see what are the actions that Terraform is going to perform:
+The last piece of information you'll need is the `service_name`: this is the ID of your Public Cloud project.
 
-```bash
-$ terraform plan
-```
-
-Now let's have a look at the content of the `main.tf` file:
+How do I get it?
 
-- The *variable* block defines the region and s3 endpoint that are used to create the bucket. You can update it according to your needs : check this [page](/pages/storage_and_backup/object_storage/s3_location) to know what region / endpoints are available.
-- The *Providers* block defines 2 providers : ovh and Hashicorp AWS one. The first one is necessary to create the user whose identity / credentials will be used for the latest.
-- The *User / Credential* block defines the user & credential that are visible in the Settings > Users & Roles tab. They are needed to configure the Hashicorp AWS provider.
-- The Bucket block defines the bucket itself.
-- The Output defines the access & secret key that may be useful for CLI usage.
+In the Public Cloud section, you can retrieve your service name ID using the `Copy to clipboard`{.action} button.
 
-#### Run
+![Copy paste service name](images/get-service-name.png){.thumbnail}
 
-```bash
-$ terraform apply
-```
+You can also use this information in Terraform resource definition files.
 
-Now you can go in the Console and check the "Object Storage" tab. Your bucket is created.
-
-#### Destroy
+## Instructions
 
-With the following command you will be back to your original state: Terraform will destroy all the resources that were previously created.
+If you would like to access the provider's documentation on Object Storage, [click here](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage.){.external}
 
-```bash
-$ terraform destroy
-```
+### Configuration
 
-> [!primary]
->
-> - This script does not follow Terraform best practices to split the project in multiple files e.g. **`provider.tf`, `main.tf`, `variables.tf`, `outputs.tf`**, ... This has been done intentionnaly to avoid switching into multiples files for what is a really simple example.
-> - The secret that is created by this script is stored in the [local](https://developer.hashicorp.com/terraform/language/settings/backends/local) state back-end. If you use this back-end in production, make sure to consider the state file as a secret.
+First, create a `provider.tf` file with the minimum version, the European endpoint (“ovh-eu”) and the keys you obtained in this guide.
 
-### Automating Object Storage policies with Terraform
-
-#### Initialize
-
-Clone the repository:
+Terraform:
 
 ```bash
-git clone https://github.com/yomovh/tf-at-ovhcloud && cd tf-at-ovhcloud/s3_policy
+terraform {
+  required_providers {
+    ovh = {
+      source  = "ovh/ovh"
+      version = "2.1.0" # greater than or equal to 2.0
+    }
+  }
+}
+
+provider "ovh" {
+  endpoint           = "ovh-eu"
+  application_key    = "<your_access_key>"
+  application_secret = "<your_application_secret>"
+  consumer_key       = "<your_consumer_key>"
+}
 ```
 
-Initialize Terraform:
-
-```bash
-$ terraform init
+Here, we've defined the `ovh-eu` endpoint because we want to call the OVHcloud Europe API, but other endpoints exist, depending on your needs:
+
+- `ovh-eu` pour OVHcloud Europe API
+- `ovh-us` pour OVHcloud US API
+- `ovh-ca` pour OVHcloud North-America API
+
+### Create a bucket
+
+You can create a file named 'object_storage_simple.tf' and write the following:
+
+```python
+# Create an Object Storage bucket
+resource "ovh_cloud_project_storage" "my-bucket" {
+ service_name = "my_service_name" # Replace with your OVHcloud project ID
+ region_name = "GRA" # Replace with the desired region in uppercase.
+  name = "object-storage-simple"
+  versioning = {
+    status = "enabled"
+  }
+  encryption = {
+    sse_algorithm = "AES256"
+  }
+}
 ```
 
-#### Plan
-
-With the following command, you will see what are the actions that Terraform is going to perform:
+You can create your resource by entering the following command:
 
 ```bash
-$ terraform plan
+terraform apply
 ```
 
-Now let's have a look at the content of the `main.tf` file and compare it with the previous example:
+### Delete a bucket
 
-- The *User / Credential* block defines 3 users and credentials : one user will be administrator of the bucket and create it, the two others will have read/write & read-only access.
-- In the *Bucket* block we have added the creation of a file into the bucket
-- The *Policy* block defines 2 policies, one for read/write and the other for read-only on the bucket.
-
-#### Run
+You can delete your bucket and all the objects it contains by entering the following command:
 
 ```bash
-$ terraform apply
+terraform destroy
 ```
 
-Now you can go in the Console and check the "Object Storage" tab. You will see the bucket and the file.
-
-You can also check the access right by using the AWS CLI with the 2 users that have the read / write & read-only access
-
-#### Destroy
-
-With the following command you will be back to your original state: Terraform will destroy all the resources that were previously created.
-
-```bash
-$ terraform destroy
-```
+> [!primary]
+>
+> This process may fail if the bucket contains locked objects. In this case, you'll need to delete these objects manually before you can run the command again.
+>
 
 ## Go further
 
diff --git a/pages/storage_and_backup/object_storage/s3_terraform/guide.es-us.md b/pages/storage_and_backup/object_storage/s3_terraform/guide.es-us.md
index 0f2ac894711..bed0f020749 100644
--- a/pages/storage_and_backup/object_storage/s3_terraform/guide.es-us.md
+++ b/pages/storage_and_backup/object_storage/s3_terraform/guide.es-us.md
@@ -1,145 +1,116 @@
 ---
 title: Object Storage - Administrar un bucket Object Storage con Terraform (EN)
-updated: 2024-08-27
+updated: 2025-05-05
 ---
 
 ## Objective
 
-This tutorial will show you how to automate some actions on Object Storage with Terraform which is an open source tool to automate infrastructure provisioning. The following actions will be automated:
-
-- Object Storage user creation
-- bucket creation
-- file copy into the bucket
-- S3 **\*** policies and assignment
+This tutorial will help you automate and orchestrate actions to use the [Object Storage](/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage) - S3* API with Terraform. Terraform is an open source tool for orchestrating the provisioning of resources.
 
 ## Requirements
 
-- Have terraform command line installed (see this [tutorial](https://developer.hashicorp.com/terraform/tutorials/aws-get-started/install-cli) from Hashicorp, the company behind Terraform). 
-- Have git command line installed
-- You will need to have set up an account to interact with the OVHcloud API (see this [tutorial](/pages/manage_and_operate/api/first-steps)). Depending on your needs in terms of permissions (http verbs PUT/GET/POST/DELETE), enter the route `/cloud/project/{serviceName}/region/{regionName}/storage/` to target object storage where *{serviceName}* corresponds to your Public Cloud project id and *{regionName}* corresponds to the region where your resources will be located. From the application keys created, you will need to export the 4 environment variables :
-
-```bash
-$ export OVH_ENDPOINT=ovh-eu
-$ export OVH_APPLICATION_KEY=Your_key_application_OVH(or_AK)
-$ export OVH_APPLICATION_SECRET=Your_secret_application_key_OVH(or_AS)
-$ export OVH_CONSUMER_KEY=Your_token(or_CK)
-```   
-
-- A Public Cloud project, with the ID exported as the variable `TF_VAR_OVH_PUBLIC_CLOUD_PROJECT_ID`
-
-```bash
-$ export TF_VAR_OVH_PUBLIC_CLOUD_PROJECT_ID=Your_public_cloud_project_id
-```
-
-**If you do not have your AWS CLI** configured, you should set dummy values with the following. This is due to a limitation in Terraform dependency graph for providers initialization (see this long lasting terraform [issue)](https://github.com/hashicorp/terraform/issues/2430)):
-
-```bash
-$ export AWS_ACCESS_KEY_ID="no_need_to_define_an_access_key"  
-$ export AWS_SECRET_ACCESS_KEY="no_need_to_define_a_secret_key"
-```
-
-## Instructions
+- Installation of the [Terraform CLI](https://www.terraform.io/downloads.html){.external}
+- Access to the [OVHcloud API](/links/api) (create your login by consulting [this guide](/pages/manage_and_operate/api/first-steps))
+- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account.
+- OVHcloud provides a [Terraform provider](https://registry.terraform.io/providers/ovh/ovh/latest){.external} which is available in the official Terraform registry. You must have installed a version >= 2.0. You can follow this guide [How to use Terraform on the OVHcloud Public Cloud](/pages/public_cloud/compute/how_to_use_terraform).
 
-### Manage an Object Storage bucket with terraform @OVHcloud
+## Getting information on your cluster/API tokens
 
-#### Initialize
+The “OVH provider” must be configured with a set of credentials:
 
-Clone the repository:
+- an `application_key`
+- an `application_secret`
+- a `consumer_key`
 
-```bash
-git clone https://github.com/yomovh/tf-at-ovhcloud && cd tf-at-ovhcloud/s3_bucket_only
-```
+Why?
 
-Initialize Terraform:
+Because, behind the scenes, the OVH Terraform provider makes requests to the OVHcloud APIs.
 
-```bash
-$ terraform init
-```
+To retrieve this necessary information, please follow the tutorial [First steps with the OVHcloud APIs](/pages/manage_and_operate/api/first-steps).
 
-#### Plan
+Once you've successfully generated your OVHcloud tokens, keep them. You'll need to set them in the next few minutes.
 
-With the following command, you will see what are the actions that Terraform is going to perform:
+The last piece of information you'll need is the `service_name`: this is the ID of your Public Cloud project.
 
-```bash
-$ terraform plan
-```
-
-Now let's have a look at the content of the `main.tf` file:
+How do I get it?
 
-- The *variable* block defines the region and s3 endpoint that are used to create the bucket. You can update it according to your needs : check this [page](/pages/storage_and_backup/object_storage/s3_location) to know what region / endpoints are available.
-- The *Providers* block defines 2 providers : ovh and Hashicorp AWS one. The first one is necessary to create the user whose identity / credentials will be used for the latest.
-- The *User / Credential* block defines the user & credential that are visible in the Settings > Users & Roles tab. They are needed to configure the Hashicorp AWS provider.
-- The Bucket block defines the bucket itself.
-- The Output defines the access & secret key that may be useful for CLI usage.
+In the Public Cloud section, you can retrieve your service name ID using the `Copy to clipboard`{.action} button.
 
-#### Run
+![Copy paste service name](images/get-service-name.png){.thumbnail}
 
-```bash
-$ terraform apply
-```
+You can also use this information in Terraform resource definition files.
 
-Now you can go in the Console and check the "Object Storage" tab. Your bucket is created.
-
-#### Destroy
+## Instructions
 
-With the following command you will be back to your original state: Terraform will destroy all the resources that were previously created.
+If you would like to access the provider's documentation on Object Storage, [click here](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage.){.external}
 
-```bash
-$ terraform destroy
-```
+### Configuration
 
-> [!primary]
->
-> - This script does not follow Terraform best practices to split the project in multiple files e.g. **`provider.tf`, `main.tf`, `variables.tf`, `outputs.tf`**, ... This has been done intentionnaly to avoid switching into multiples files for what is a really simple example.
-> - The secret that is created by this script is stored in the [local](https://developer.hashicorp.com/terraform/language/settings/backends/local) state back-end. If you use this back-end in production, make sure to consider the state file as a secret.
+First, create a `provider.tf` file with the minimum version, the European endpoint (“ovh-eu”) and the keys you obtained in this guide.
 
-### Automating Object Storage policies with Terraform
-
-#### Initialize
-
-Clone the repository:
+Terraform:
 
 ```bash
-git clone https://github.com/yomovh/tf-at-ovhcloud && cd tf-at-ovhcloud/s3_policy
+terraform {
+  required_providers {
+    ovh = {
+      source  = "ovh/ovh"
+      version = "2.1.0" # greater than or equal to 2.0
+    }
+  }
+}
+
+provider "ovh" {
+  endpoint           = "ovh-eu"
+  application_key    = "<your_access_key>"
+  application_secret = "<your_application_secret>"
+  consumer_key       = "<your_consumer_key>"
+}
 ```
 
-Initialize Terraform:
-
-```bash
-$ terraform init
+Here, we've defined the `ovh-eu` endpoint because we want to call the OVHcloud Europe API, but other endpoints exist, depending on your needs:
+
+- `ovh-eu` pour OVHcloud Europe API
+- `ovh-us` pour OVHcloud US API
+- `ovh-ca` pour OVHcloud North-America API
+
+### Create a bucket
+
+You can create a file named 'object_storage_simple.tf' and write the following:
+
+```python
+# Create an Object Storage bucket
+resource "ovh_cloud_project_storage" "my-bucket" {
+ service_name = "my_service_name" # Replace with your OVHcloud project ID
+ region_name = "GRA" # Replace with the desired region in uppercase.
+  name = "object-storage-simple"
+  versioning = {
+    status = "enabled"
+  }
+  encryption = {
+    sse_algorithm = "AES256"
+  }
+}
 ```
 
-#### Plan
-
-With the following command, you will see what are the actions that Terraform is going to perform:
+You can create your resource by entering the following command:
 
 ```bash
-$ terraform plan
+terraform apply
 ```
 
-Now let's have a look at the content of the `main.tf` file and compare it with the previous example:
+### Delete a bucket
 
-- The *User / Credential* block defines 3 users and credentials : one user will be administrator of the bucket and create it, the two others will have read/write & read-only access.
-- In the *Bucket* block we have added the creation of a file into the bucket
-- The *Policy* block defines 2 policies, one for read/write and the other for read-only on the bucket.
-
-#### Run
+You can delete your bucket and all the objects it contains by entering the following command:
 
 ```bash
-$ terraform apply
+terraform destroy
 ```
 
-Now you can go in the Console and check the "Object Storage" tab. You will see the bucket and the file.
-
-You can also check the access right by using the AWS CLI with the 2 users that have the read / write & read-only access
-
-#### Destroy
-
-With the following command you will be back to your original state: Terraform will destroy all the resources that were previously created.
-
-```bash
-$ terraform destroy
-```
+> [!primary]
+>
+> This process may fail if the bucket contains locked objects. In this case, you'll need to delete these objects manually before you can run the command again.
+>
 
 ## Go further
 
diff --git a/pages/storage_and_backup/object_storage/s3_terraform/guide.fr-ca.md b/pages/storage_and_backup/object_storage/s3_terraform/guide.fr-ca.md
index d93d12c5eee..2dfc76aa742 100644
--- a/pages/storage_and_backup/object_storage/s3_terraform/guide.fr-ca.md
+++ b/pages/storage_and_backup/object_storage/s3_terraform/guide.fr-ca.md
@@ -1,147 +1,116 @@
 ---
 title: Object Storage - Gérer un bucket Object Storage avec Terraform
-updated: 2024-08-27
+updated: 2025-05-05
 ---
 
 ## Objectif
 
-Ce tutoriel va vous permettre d'automatiser et d'orchestrer des actions pour utiliser l'Object Storage - S3 API avec Terraform. Terraform est un outil open source permettant d'orchestrer la provision et la mise à disposition des ressources. Les actions suivantes seront automatisées :
-
-- la création d'un Object Storage ;
-- la création d'un conteneur d'objet ;
-- la copie d'un objet dans un bucket ;
-- la gestion des accès des utilisateurs avec *S3 **\*** policies*.
+Ce tutoriel va vous permettre d'automatiser et d'orchestrer des actions pour utiliser l'[Object Storage](/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage) - S3* API avec Terraform. Terraform est un outil open source permettant d'orchestrer la provision et la mise à disposition des ressources.
 
 ## Prérequis
 
-- Installer la CLI Terraform  (se réferer au [tutoriel](https://developer.hashicorp.com/terraform/tutorials/aws-get-started/install-cli) d'Hashicorp, la société qui a créé Terraform). 
-- Installer la commande git 
-- Avoir accès aux API v6 (consultez notre guide de [premiers pas avec les API OVHcloud](/pages/manage_and_operate/api/first-steps)). En fonction de vos besoins en termes de permissions (verbes http PUT/GET/POST/DELETE), renseignez la route `/cloud/project/{serviceName}/region/{regionName}/storage/` pour cibler Object Storage où *{serviceName}* correspond à votre id de projet Public Cloud et *{regionName}* correspond à la région où vos ressources vont être localisées. Une fois les accès aux API créés, exportez les 4 IDs dans les variables, tel que décrit ci-dessous :
-
-```bash
-$ export OVH_ENDPOINT=ovh-eu
-$ export OVH_APPLICATION_KEY=Your_key_application_OVH(or_AK)
-$ export OVH_APPLICATION_SECRET=Your_secret_application_key_OVH(or_AS)
-$ export OVH_CONSUMER_KEY=Your_token(or_CK)
-```   
+- Installation de [la CLI Terraform](https://www.terraform.io/downloads.html){.external}
+- Accès à l'[API OVHcloud](/links/api) (créez vos identifiants en consultant [ce guide](/pages/manage_and_operate/api/first-steps))
+- Un [projet Public Cloud](/links/public-cloud/public-cloud) dans votre compte OVHcloud.
+- OVHcloud fournit un [Terraform provider](https://registry.terraform.io/providers/ovh/ovh/latest){.external} qui est disponible dans le registre officiel de Terraform. Vous devez avoir installé une version >= 2.0. Vous pouvez suivre le guide [Comment utiliser Terraform sur le Public Cloud OVHcloud](/pages/public_cloud/compute/how_to_use_terraform).
 
-- Un projet Public Cloud. Exportez l'ID dans la variable `TF_VAR_OVH_PUBLIC_CLOUD_PROJECT_ID` :
+## Obtenir des informations sur vos jetons cluster/API
 
-```bash
-$ export TF_VAR_OVH_PUBLIC_CLOUD_PROJECT_ID=Your_public_cloud_project_id
-```
+Le « provider OVH » doit être configuré avec un ensemble d'informations d'identification :
 
-**Si vous n'avez pas la CLI AWS configurée**, vous devez paramétrer les access key et secret keys Object Storage, peu importe leur valeur car elles seront surchargées. Cela est dû à une limitation de Terraform au moment de son initialisation (référez-vous au [ticket Terraform associé](https://github.com/hashicorp/terraform/issues/2430)) :
+- une `application_key`
+- une `application_secret`
+- une `consumer_key`
 
-```bash
-$ export AWS_ACCESS_KEY_ID="no_need_to_define_an_access_key"  
-$ export AWS_SECRET_ACCESS_KEY="no_need_to_define_a_secret_key"
-```
+Pourquoi ?
 
-## En pratique
+Parce que, dans les coulisses, le « OVH Terraform provider » fait des requêtes aux API d'OVHcloud.
 
-### Gérer un bucket Object Storage avec Terraform @OVHcloud
+Afin de récupérer ces informations nécessaires, veuillez suivre le tutoriel [Premiers pas avec les API OVHcloud](/pages/manage_and_operate/api/first-steps).
 
-#### Initialisation
+Lorsque vous avez généré avec succès vos tokens OVHcloud, conservez-les. Vous devrez les utiliser dans les minutes à venir.
 
-Clonez le répertoire depuis GitHub :
+La dernière information nécessaire est le `service_name` : c'est l'ID de votre projet Public Cloud.
 
-```bash
-git clone https://github.com/yomovh/tf-at-ovhcloud && cd tf-at-ovhcloud/s3_bucket_only
-```
+Comment l'obtenir ?
 
-Initialisez Terraform :
+Dans la section Public Cloud, vous pouvez récupérer l'ID de votre nom de service grâce au bouton `Copier dans le presse-papier`{.action}.
 
-```bash
-$ terraform init
-```
-
-#### Planification
-
-Avec la commande suivante, vous verrez quelles sont les actions que Terraform va effectuer :
-
-```bash
-$ terraform plan
-```
-
-Regardez à présent le contenu du fichier `main.tf` :
-
-- Le bloc *variable* définit la région et le *s3 endpoint* qui sont utilisés pour créer le bucket. Vous pouvez l'adapter en fonction de votre besoin : [Object Storage - Endpoints et géo-disponibilité de l’Object Storage](/pages/storage_and_backup/object_storage/s3_location) to know what region / endpoints are available..
-- Le bloc *Providers* définit 2 providers : celui d'OVHcloud et celui d'Hashicorp AWS. Le premier est nécessaire pour créer les utilisateurs qui seront utilisés par le second.
-- Le bloc *User / Credential* définit les user & credential qui sont visibles dans la table Settings > Users & Roles. Ils sont nécessaires pour la configuration du provider Hashicorp AWS provider.
-- Le bloc Bucket définit le bucket 
-- La sortie Output définit l'access et le secret key pouvant être utiles pour l'utilisation de la CLI.
-
-#### Run
-
-```bash
-$ terraform apply
-```
+![Copy paste service name](images/get-service-name.png){.thumbnail}
 
-Vous pouvez aller dans la Console et vérifier la table « Object Storage ». Votre bucket est créé.
+Vous utiliserez également ces informations dans les fichiers de définition des ressources Terraform.
 
-#### Suppression
+## En pratique
 
-Avec la commande ci-dessous, vous revenez à votre état initial : Terraform va détruire la ressource initialement créée.
+Si vous souhaitez accéder à la documentation du provider sur Object Storage, [cliquez-ici](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage.){.external}
 
-```bash
-$ terraform destroy
-```
+### Configuration
 
-> [!primary]
->
-> - Le script ne suit pas les bonnes pratiques de Terraform, à savoir séparer le projet en multiples fichiers tels que `provider.tf`, `main.tf`, `variables.tf`, `outputs.tf`, ... Ce point est intentionnel pour éviter de basculer dans de multiples fichiers pour cet exemple qui se veut didactique et simple.
->
-> - Le secret créé par ce script est stocké dans le *[local state back-end](https://developer.hashicorp.com/terraform/language/settings/backends/local)*. Si vous utilisez ce back-end en production, assurez-vous de gérer le *state file* comme un secret.
->
-
-### Automatisation des policies Object Storage avec Terraform
-
-#### Initialisation
+Tout d'abord, créez un fichier `provider.tf` avec la version minimale, le point de terminaison européen (`ovh-eu`) et les clés que vous avez obtenues dans ce guide.
 
-Clonez le répertoire :
+Terraform :
 
 ```bash
-git clone https://github.com/yomovh/tf-at-ovhcloud && cd tf-at-ovhcloud/s3_policy
+terraform {
+  required_providers {
+    ovh = {
+      source  = "ovh/ovh"
+      version = "2.1.0" # greater than or equal to 2.0
+    }
+  }
+}
+
+provider "ovh" {
+  endpoint           = "ovh-eu"
+  application_key    = "<your_access_key>"
+  application_secret = "<your_application_secret>"
+  consumer_key       = "<your_consumer_key>"
+}
 ```
 
-Initialisez Terraform :
-
-```bash
-$ terraform init
+Ici, nous avons défini le point de terminaison `ovh-eu` parce que nous voulons appeler l'API OVHcloud Europe, mais d'autres points de terminaison existent, en fonction de vos besoins :
+
+- `ovh-eu` pour OVHcloud Europe API
+- `ovh-us` pour OVHcloud US API
+- `ovh-ca` pour OVHcloud North-America API
+
+### Créer un bucket
+
+Vous pouvez créer un fichier nommé 'object_storage_simple.tf' et écrire ce qui suit :
+
+```python
+# Créer un bucket Object Storage
+resource "ovh_cloud_project_storage" "my-bucket" {
+  service_name = "my_service_name" # Remplacer par votre OVHcloud project ID
+  region_name = "GRA" # Remplacer par la région voulue en majuscule.
+  name = "object-storage-simple"
+  versioning = {
+    status = "enabled"
+  }
+  encryption = {
+    sse_algorithm = "AES256"
+  }
+}
 ```
 
-#### Planification
-
-Avec la commande suivante, vous verrez quelles sont les actions que Terraform va effectuer :
+Vous pouvez créer votre ressource en entrant la commande suivante :
 
 ```bash
-$ terraform plan
+terraform apply
 ```
 
-Regardez à présent le contenu du fichier `main.tf` file et comparez avec l'exemple précédent :
-
-- Le bloc *User / Credential* définit 3 *user & credentials* : un *user* va être utilisateur du bucket et le créer, les deux autres vont avoir les droits read/write pour l'un et les accès read-only access pour l'autre.
-- Le bloc *Bucket* réalise la création d'un objet dans un bucket.
-- Le bloc *Policy* définit 2 policies Object Storage, une pour read/write et l'autre pour read-only.
+### Supprimer un bucket
 
-#### Run
+Vous pouvez supprimer votre bucket ainsi que tout les objets qu'il contient en entrant la commande suivante :
 
 ```bash
-$ terraform apply
+terraform destroy
 ```
 
-Maintenant allez dans le manager (Console) et vérifiez la table « Object Storage ». Vous verrez le bucket et l'objet.
-
-Vous pouvez vérifier les accès en utilisant la CLI AWS et vérifier les user policies.
-
-#### Suppression
-
-Avec la commande ci-dessous, vous revenez à votre état initial : Terraform va détruire la ressource initialement créée :
-
-```bash
-$ terraform destroy
-```
+> [!primary]
+>
+> Ce processus peut échouer si le bucket contient des objets verrouillés. Dans ce cas, vous devrez supprimer ces objets manuellement avant de pouvoir relancer la commande.
+>
 
 ## Aller plus loin
 
diff --git a/pages/storage_and_backup/object_storage/s3_terraform/guide.fr-fr.md b/pages/storage_and_backup/object_storage/s3_terraform/guide.fr-fr.md
index 9a87f45777d..dc19dc66631 100644
--- a/pages/storage_and_backup/object_storage/s3_terraform/guide.fr-fr.md
+++ b/pages/storage_and_backup/object_storage/s3_terraform/guide.fr-fr.md
@@ -1,147 +1,116 @@
 ---
 title: Object Storage - Gérer un bucket Object Storage avec Terraform
-updated: 2024-08-27
+updated: 2025-05-05
 ---
 
 ## Objectif
 
-Ce tutoriel va vous permettre d'automatiser et d'orchestrer des actions pour utiliser l'Object Storage - S3 API avec Terraform. Terraform est un outil open source permettant d'orchestrer la provision et la mise à disposition des ressources. Les actions suivantes seront automatisées :
-
-- la création d'un Object Storage ;
-- la création d'un conteneur d'objet ;
-- la copie d'un objet dans un bucket ;
-- la gestion des accès des utilisateurs avec *S3 **\*** policies*.
+Ce tutoriel va vous permettre d'automatiser et d'orchestrer des actions pour utiliser l'[Object Storage](/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage) - S3* API avec Terraform. Terraform est un outil open source permettant d'orchestrer la provision et la mise à disposition des ressources.
 
 ## Prérequis
 
-- Installer la CLI Terraform  (se réferer au [tutoriel](https://developer.hashicorp.com/terraform/tutorials/aws-get-started/install-cli) d'Hashicorp, la société qui a créé Terraform). 
-- Installer la commande git 
-- Avoir accès aux API v6 (consultez notre guide de [premiers pas avec les API OVHcloud](/pages/manage_and_operate/api/first-steps)). En fonction de vos besoins en termes de permissions (verbes http PUT/GET/POST/DELETE), renseignez la route `/cloud/project/{serviceName}/region/{regionName}/storage/` pour cibler Object Storage où *{serviceName}* correspond à votre id de projet Public Cloud et *{regionName}* correspond à la région où vos ressources vont être localisées. Une fois les accès aux API créés, exportez les 4 IDs dans les variables, tel que décrit ci-dessous :
-
-```bash
-$ export OVH_ENDPOINT=ovh-eu
-$ export OVH_APPLICATION_KEY=Your_key_application_OVH(or_AK)
-$ export OVH_APPLICATION_SECRET=Your_secret_application_key_OVH(or_AS)
-$ export OVH_CONSUMER_KEY=Your_token(or_CK)
-```   
+- Installation de [la CLI Terraform](https://www.terraform.io/downloads.html){.external}
+- Accès à l'[API OVHcloud](/links/api) (créez vos identifiants en consultant [ce guide](/pages/manage_and_operate/api/first-steps))
+- Un [projet Public Cloud](/links/public-cloud/public-cloud) dans votre compte OVHcloud.
+- OVHcloud fournit un [Terraform provider](https://registry.terraform.io/providers/ovh/ovh/latest){.external} qui est disponible dans le registre officiel de Terraform. Vous devez avoir installé une version >= 2.0. Vous pouvez suivre le guide [Comment utiliser Terraform sur le Public Cloud OVHcloud](/pages/public_cloud/compute/how_to_use_terraform).
 
-- Un projet Public Cloud. Exportez l'ID dans la variable `TF_VAR_OVH_PUBLIC_CLOUD_PROJECT_ID` :
+## Obtenir des informations sur vos jetons cluster/API
 
-```bash
-$ export TF_VAR_OVH_PUBLIC_CLOUD_PROJECT_ID=Your_public_cloud_project_id
-```
+Le « provider OVH » doit être configuré avec un ensemble d'informations d'identification :
 
-**Si vous n'avez pas la CLI AWS configurée**, vous devez paramétrer les access key et secret keys Object Storage, peu importe leur valeur car elles seront surchargées. Cela est dû à une limitation de Terraform au moment de son initialisation (référez-vous au [ticket Terraform associé](https://github.com/hashicorp/terraform/issues/2430)) :
+- une `application_key`
+- une `application_secret`
+- une `consumer_key`
 
-```bash
-$ export AWS_ACCESS_KEY_ID="no_need_to_define_an_access_key"  
-$ export AWS_SECRET_ACCESS_KEY="no_need_to_define_a_secret_key"
-```
+Pourquoi ?
 
-## En pratique
+Parce que, dans les coulisses, le « OVH Terraform provider » fait des requêtes aux API d'OVHcloud.
 
-### Gérer un bucket Object Storage avec Terraform @OVHcloud
+Afin de récupérer ces informations nécessaires, veuillez suivre le tutoriel [Premiers pas avec les API OVHcloud](/pages/manage_and_operate/api/first-steps).
 
-#### Initialisation
+Lorsque vous avez généré avec succès vos tokens OVHcloud, conservez-les. Vous devrez les utiliser dans les minutes à venir.
 
-Clonez le répertoire depuis GitHub :
+La dernière information nécessaire est le `service_name` : c'est l'ID de votre projet Public Cloud.
 
-```bash
-git clone https://github.com/yomovh/tf-at-ovhcloud && cd tf-at-ovhcloud/s3_bucket_only
-```
+Comment l'obtenir ?
 
-Initialisez Terraform :
+Dans la section Public Cloud, vous pouvez récupérer l'ID de votre nom de service grâce au bouton `Copier dans le presse-papier`{.action}.
 
-```bash
-$ terraform init
-```
-
-#### Planification
-
-Avec la commande suivante, vous verrez quelles sont les actions que Terraform va effectuer :
-
-```bash
-$ terraform plan
-```
-
-Regardez à présent le contenu du fichier `main.tf` :
-
-- Le bloc *variable* définit la région et le *s3 endpoint* qui sont utilisés pour créer le bucket. Vous pouvez l'adapter en fonction de votre besoin : [Object Storage - Endpoints et géo-disponibilité de l’Object Storage](/pages/storage_and_backup/object_storage/s3_location) to know what region / endpoints are available..
-- Le bloc *Providers* définit 2 providers : celui d'OVHcloud et celui d'Hashicorp AWS. Le premier est nécessaire pour créer les utilisateurs qui seront utilisés par le second.
-- Le bloc *User / Credential* définit les user & credential qui sont visibles dans la table Settings > Users & Roles. Ils sont nécessaires pour la configuration du provider Hashicorp AWS provider.
-- Le bloc Bucket définit le bucket 
-- La sortie Output définit l'access et le secret key pouvant être utiles pour l'utilisation de la CLI.
-
-#### Run
-
-```bash
-$ terraform apply
-```
+![Copy paste service name](images/get-service-name.png){.thumbnail}
 
-Vous pouvez aller dans la Console et vérifier la table « Object Storage ». Votre bucket est créé.
+Vous utiliserez également ces informations dans les fichiers de définition des ressources Terraform.
 
-#### Suppression
+## En pratique
 
-Avec la commande ci-dessous, vous revenez à votre état initial : Terraform va détruire la ressource initialement créée.
+Si vous souhaitez accéder à la documentation du provider sur Object Storage, [cliquez-ici](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage.){.external}
 
-```bash
-$ terraform destroy
-```
+### Configuration
 
-> [!primary]
->
-> - Le script ne suit pas les bonnes pratiques de Terraform, à savoir séparer le projet en multiples fichiers tels que `provider.tf`, `main.tf`, `variables.tf`, `outputs.tf`, ... Ce point est intentionnel pour éviter de basculer dans de multiples fichiers pour cet exemple qui se veut didactique et simple.
->
-> - Le secret créé par ce script est stocké dans le *[local state back-end](https://developer.hashicorp.com/terraform/language/settings/backends/local)*. Si vous utilisez ce back-end en production, assurez-vous de gérer le *state file* comme un secret.
->
-
-### Automatisation des policies Object Storage avec Terraform
-
-#### Initialisation
+Tout d'abord, créez un fichier `provider.tf` avec la version minimale, le point de terminaison européen (`ovh-eu`) et les clés que vous avez obtenues dans ce guide.
 
-Clonez le répertoire :
+Terraform :
 
 ```bash
-git clone https://github.com/yomovh/tf-at-ovhcloud && cd tf-at-ovhcloud/s3_policy
+terraform {
+  required_providers {
+    ovh = {
+      source  = "ovh/ovh"
+      version = "2.1.0" # greater than or equal to 2.0
+    }
+  }
+}
+
+provider "ovh" {
+  endpoint           = "ovh-eu"
+  application_key    = "<your_access_key>"
+  application_secret = "<your_application_secret>"
+  consumer_key       = "<your_consumer_key>"
+}
 ```
 
-Initialisez Terraform :
-
-```bash
-$ terraform init
+Ici, nous avons défini le point de terminaison `ovh-eu` parce que nous voulons appeler l'API OVHcloud Europe, mais d'autres points de terminaison existent, en fonction de vos besoins :
+
+- `ovh-eu` pour OVHcloud Europe API
+- `ovh-us` pour OVHcloud US API
+- `ovh-ca` pour OVHcloud North-America API
+
+### Créer un bucket
+
+Vous pouvez créer un fichier nommé 'object_storage_simple.tf' et écrire ce qui suit :
+
+```python
+# Créer un bucket Object Storage
+resource "ovh_cloud_project_storage" "my-bucket" {
+  service_name = "my_service_name" # Remplacer par votre OVHcloud project ID
+  region_name = "GRA" # Remplacer par la région voulue en majuscule.
+  name = "object-storage-simple"
+  versioning = {
+    status = "enabled"
+  }
+  encryption = {
+    sse_algorithm = "AES256"
+  }
+}
 ```
 
-#### Planification
-
-Avec la commande suivante, vous verrez quelles sont les actions que Terraform va effectuer :
+Vous pouvez créer votre ressource en entrant la commande suivante :
 
 ```bash
-$ terraform plan
+terraform apply
 ```
 
-Regardez à présent le contenu du fichier `main.tf` file et comparez avec l'exemple précédent :
-
-- Le bloc *User / Credential* définit 3 *user & credentials* : un *user* va être utilisateur du bucket et le créer, les deux autres vont avoir les droits read/write pour l'un et les accès read-only access pour l'autre.
-- Le bloc *Bucket* réalise la création d'un objet dans un bucket.
-- Le bloc *Policy* définit 2 policies Object Storage, une pour read/write et l'autre pour read-only.
+### Supprimer un bucket
 
-#### Run
+Vous pouvez supprimer votre bucket ainsi que tout les objets qu'il contient en entrant la commande suivante :
 
 ```bash
-$ terraform apply
+terraform destroy
 ```
 
-Maintenant allez dans le manager (Console) et vérifiez la table « Object Storage ». Vous verrez le bucket et l'objet.
-
-Vous pouvez vérifier les accès en utilisant la CLI AWS et vérifier les user policies.
-
-#### Suppression
-
-Avec la commande ci-dessous, vous revenez à votre état initial : Terraform va détruire la ressource initialement créée :
-
-```bash
-$ terraform destroy
-```
+> [!primary]
+>
+> Ce processus peut échouer si le bucket contient des objets verrouillés. Dans ce cas, vous devrez supprimer ces objets manuellement avant de pouvoir relancer la commande.
+>
 
 ## Aller plus loin
 
diff --git a/pages/storage_and_backup/object_storage/s3_terraform/guide.it-it.md b/pages/storage_and_backup/object_storage/s3_terraform/guide.it-it.md
index 8cd3abeeb39..3751464b994 100644
--- a/pages/storage_and_backup/object_storage/s3_terraform/guide.it-it.md
+++ b/pages/storage_and_backup/object_storage/s3_terraform/guide.it-it.md
@@ -1,145 +1,116 @@
 ---
 title: Object Storage - Gestisci un bucket Object Storage con Terraform (EN)
-updated: 2024-08-27
+updated: 2025-05-05
 ---
 
 ## Objective
 
-This tutorial will show you how to automate some actions on Object Storage with Terraform which is an open source tool to automate infrastructure provisioning. The following actions will be automated:
-
-- Object Storage user creation
-- bucket creation
-- file copy into the bucket
-- S3 **\*** policies and assignment
+This tutorial will help you automate and orchestrate actions to use the [Object Storage](/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage) - S3* API with Terraform. Terraform is an open source tool for orchestrating the provisioning of resources.
 
 ## Requirements
 
-- Have terraform command line installed (see this [tutorial](https://developer.hashicorp.com/terraform/tutorials/aws-get-started/install-cli) from Hashicorp, the company behind Terraform). 
-- Have git command line installed
-- You will need to have set up an account to interact with the OVHcloud API (see this [tutorial](/pages/manage_and_operate/api/first-steps)). Depending on your needs in terms of permissions (http verbs PUT/GET/POST/DELETE), enter the route `/cloud/project/{serviceName}/region/{regionName}/storage/` to target object storage where *{serviceName}* corresponds to your Public Cloud project id and *{regionName}* corresponds to the region where your resources will be located. From the application keys created, you will need to export the 4 environment variables :
-
-```bash
-$ export OVH_ENDPOINT=ovh-eu
-$ export OVH_APPLICATION_KEY=Your_key_application_OVH(or_AK)
-$ export OVH_APPLICATION_SECRET=Your_secret_application_key_OVH(or_AS)
-$ export OVH_CONSUMER_KEY=Your_token(or_CK)
-```   
-
-- A Public Cloud project, with the ID exported as the variable `TF_VAR_OVH_PUBLIC_CLOUD_PROJECT_ID`
-
-```bash
-$ export TF_VAR_OVH_PUBLIC_CLOUD_PROJECT_ID=Your_public_cloud_project_id
-```
-
-**If you do not have your AWS CLI** configured, you should set dummy values with the following. This is due to a limitation in Terraform dependency graph for providers initialization (see this long lasting terraform [issue)](https://github.com/hashicorp/terraform/issues/2430)):
-
-```bash
-$ export AWS_ACCESS_KEY_ID="no_need_to_define_an_access_key"  
-$ export AWS_SECRET_ACCESS_KEY="no_need_to_define_a_secret_key"
-```
-
-## Instructions
+- Installation of the [Terraform CLI](https://www.terraform.io/downloads.html){.external}
+- Access to the [OVHcloud API](/links/api) (create your login by consulting [this guide](/pages/manage_and_operate/api/first-steps))
+- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account.
+- OVHcloud provides a [Terraform provider](https://registry.terraform.io/providers/ovh/ovh/latest){.external} which is available in the official Terraform registry. You must have installed a version >= 2.0. You can follow this guide [How to use Terraform on the OVHcloud Public Cloud](/pages/public_cloud/compute/how_to_use_terraform).
 
-### Manage an Object Storage bucket with terraform @OVHcloud
+## Getting information on your cluster/API tokens
 
-#### Initialize
+The “OVH provider” must be configured with a set of credentials:
 
-Clone the repository:
+- an `application_key`
+- an `application_secret`
+- a `consumer_key`
 
-```bash
-git clone https://github.com/yomovh/tf-at-ovhcloud && cd tf-at-ovhcloud/s3_bucket_only
-```
+Why?
 
-Initialize Terraform:
+Because, behind the scenes, the OVH Terraform provider makes requests to the OVHcloud APIs.
 
-```bash
-$ terraform init
-```
+To retrieve this necessary information, please follow the tutorial [First steps with the OVHcloud APIs](/pages/manage_and_operate/api/first-steps).
 
-#### Plan
+Once you've successfully generated your OVHcloud tokens, keep them. You'll need to set them in the next few minutes.
 
-With the following command, you will see what are the actions that Terraform is going to perform:
+The last piece of information you'll need is the `service_name`: this is the ID of your Public Cloud project.
 
-```bash
-$ terraform plan
-```
-
-Now let's have a look at the content of the `main.tf` file:
+How do I get it?
 
-- The *variable* block defines the region and s3 endpoint that are used to create the bucket. You can update it according to your needs : check this [page](/pages/storage_and_backup/object_storage/s3_location) to know what region / endpoints are available.
-- The *Providers* block defines 2 providers : ovh and Hashicorp AWS one. The first one is necessary to create the user whose identity / credentials will be used for the latest.
-- The *User / Credential* block defines the user & credential that are visible in the Settings > Users & Roles tab. They are needed to configure the Hashicorp AWS provider.
-- The Bucket block defines the bucket itself.
-- The Output defines the access & secret key that may be useful for CLI usage.
+In the Public Cloud section, you can retrieve your service name ID using the `Copy to clipboard`{.action} button.
 
-#### Run
+![Copy paste service name](images/get-service-name.png){.thumbnail}
 
-```bash
-$ terraform apply
-```
+You can also use this information in Terraform resource definition files.
 
-Now you can go in the Console and check the "Object Storage" tab. Your bucket is created.
-
-#### Destroy
+## Instructions
 
-With the following command you will be back to your original state: Terraform will destroy all the resources that were previously created.
+If you would like to access the provider's documentation on Object Storage, [click here](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage.){.external}
 
-```bash
-$ terraform destroy
-```
+### Configuration
 
-> [!primary]
->
-> - This script does not follow Terraform best practices to split the project in multiple files e.g. **`provider.tf`, `main.tf`, `variables.tf`, `outputs.tf`**, ... This has been done intentionnaly to avoid switching into multiples files for what is a really simple example.
-> - The secret that is created by this script is stored in the [local](https://developer.hashicorp.com/terraform/language/settings/backends/local) state back-end. If you use this back-end in production, make sure to consider the state file as a secret.
+First, create a `provider.tf` file with the minimum version, the European endpoint (“ovh-eu”) and the keys you obtained in this guide.
 
-### Automating Object Storage policies with Terraform
-
-#### Initialize
-
-Clone the repository:
+Terraform:
 
 ```bash
-git clone https://github.com/yomovh/tf-at-ovhcloud && cd tf-at-ovhcloud/s3_policy
+terraform {
+  required_providers {
+    ovh = {
+      source  = "ovh/ovh"
+      version = "2.1.0" # greater than or equal to 2.0
+    }
+  }
+}
+
+provider "ovh" {
+  endpoint           = "ovh-eu"
+  application_key    = "<your_access_key>"
+  application_secret = "<your_application_secret>"
+  consumer_key       = "<your_consumer_key>"
+}
 ```
 
-Initialize Terraform:
-
-```bash
-$ terraform init
+Here, we've defined the `ovh-eu` endpoint because we want to call the OVHcloud Europe API, but other endpoints exist, depending on your needs:
+
+- `ovh-eu` pour OVHcloud Europe API
+- `ovh-us` pour OVHcloud US API
+- `ovh-ca` pour OVHcloud North-America API
+
+### Create a bucket
+
+You can create a file named 'object_storage_simple.tf' and write the following:
+
+```python
+# Create an Object Storage bucket
+resource "ovh_cloud_project_storage" "my-bucket" {
+ service_name = "my_service_name" # Replace with your OVHcloud project ID
+ region_name = "GRA" # Replace with the desired region in uppercase.
+  name = "object-storage-simple"
+  versioning = {
+    status = "enabled"
+  }
+  encryption = {
+    sse_algorithm = "AES256"
+  }
+}
 ```
 
-#### Plan
-
-With the following command, you will see what are the actions that Terraform is going to perform:
+You can create your resource by entering the following command:
 
 ```bash
-$ terraform plan
+terraform apply
 ```
 
-Now let's have a look at the content of the `main.tf` file and compare it with the previous example:
+### Delete a bucket
 
-- The *User / Credential* block defines 3 users and credentials : one user will be administrator of the bucket and create it, the two others will have read/write & read-only access.
-- In the *Bucket* block we have added the creation of a file into the bucket
-- The *Policy* block defines 2 policies, one for read/write and the other for read-only on the bucket.
-
-#### Run
+You can delete your bucket and all the objects it contains by entering the following command:
 
 ```bash
-$ terraform apply
+terraform destroy
 ```
 
-Now you can go in the Console and check the "Object Storage" tab. You will see the bucket and the file.
-
-You can also check the access right by using the AWS CLI with the 2 users that have the read / write & read-only access
-
-#### Destroy
-
-With the following command you will be back to your original state: Terraform will destroy all the resources that were previously created.
-
-```bash
-$ terraform destroy
-```
+> [!primary]
+>
+> This process may fail if the bucket contains locked objects. In this case, you'll need to delete these objects manually before you can run the command again.
+>
 
 ## Go further
 
diff --git a/pages/storage_and_backup/object_storage/s3_terraform/guide.pl-pl.md b/pages/storage_and_backup/object_storage/s3_terraform/guide.pl-pl.md
index c1bbfbc930d..7691547cd7a 100644
--- a/pages/storage_and_backup/object_storage/s3_terraform/guide.pl-pl.md
+++ b/pages/storage_and_backup/object_storage/s3_terraform/guide.pl-pl.md
@@ -1,145 +1,116 @@
 ---
 title: Object Storage - Zarządzaj zasobnikiem Object Storage za pomocą Terraform (EN)
-updated: 2024-08-27
+updated: 2025-05-05
 ---
 
 ## Objective
 
-This tutorial will show you how to automate some actions on Object Storage with Terraform which is an open source tool to automate infrastructure provisioning. The following actions will be automated:
-
-- Object Storage user creation
-- bucket creation
-- file copy into the bucket
-- S3 **\*** policies and assignment
+This tutorial will help you automate and orchestrate actions to use the [Object Storage](/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage) - S3* API with Terraform. Terraform is an open source tool for orchestrating the provisioning of resources.
 
 ## Requirements
 
-- Have terraform command line installed (see this [tutorial](https://developer.hashicorp.com/terraform/tutorials/aws-get-started/install-cli) from Hashicorp, the company behind Terraform). 
-- Have git command line installed
-- You will need to have set up an account to interact with the OVHcloud API (see this [tutorial](/pages/manage_and_operate/api/first-steps)). Depending on your needs in terms of permissions (http verbs PUT/GET/POST/DELETE), enter the route `/cloud/project/{serviceName}/region/{regionName}/storage/` to target object storage where *{serviceName}* corresponds to your Public Cloud project id and *{regionName}* corresponds to the region where your resources will be located. From the application keys created, you will need to export the 4 environment variables :
-
-```bash
-$ export OVH_ENDPOINT=ovh-eu
-$ export OVH_APPLICATION_KEY=Your_key_application_OVH(or_AK)
-$ export OVH_APPLICATION_SECRET=Your_secret_application_key_OVH(or_AS)
-$ export OVH_CONSUMER_KEY=Your_token(or_CK)
-```   
-
-- A Public Cloud project, with the ID exported as the variable `TF_VAR_OVH_PUBLIC_CLOUD_PROJECT_ID`
-
-```bash
-$ export TF_VAR_OVH_PUBLIC_CLOUD_PROJECT_ID=Your_public_cloud_project_id
-```
-
-**If you do not have your AWS CLI** configured, you should set dummy values with the following. This is due to a limitation in Terraform dependency graph for providers initialization (see this long lasting terraform [issue)](https://github.com/hashicorp/terraform/issues/2430)):
-
-```bash
-$ export AWS_ACCESS_KEY_ID="no_need_to_define_an_access_key"  
-$ export AWS_SECRET_ACCESS_KEY="no_need_to_define_a_secret_key"
-```
-
-## Instructions
+- Installation of the [Terraform CLI](https://www.terraform.io/downloads.html){.external}
+- Access to the [OVHcloud API](/links/api) (create your login by consulting [this guide](/pages/manage_and_operate/api/first-steps))
+- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account.
+- OVHcloud provides a [Terraform provider](https://registry.terraform.io/providers/ovh/ovh/latest){.external} which is available in the official Terraform registry. You must have installed a version >= 2.0. You can follow this guide [How to use Terraform on the OVHcloud Public Cloud](/pages/public_cloud/compute/how_to_use_terraform).
 
-### Manage an Object Storage bucket with terraform @OVHcloud
+## Getting information on your cluster/API tokens
 
-#### Initialize
+The “OVH provider” must be configured with a set of credentials:
 
-Clone the repository:
+- an `application_key`
+- an `application_secret`
+- a `consumer_key`
 
-```bash
-git clone https://github.com/yomovh/tf-at-ovhcloud && cd tf-at-ovhcloud/s3_bucket_only
-```
+Why?
 
-Initialize Terraform:
+Because, behind the scenes, the OVH Terraform provider makes requests to the OVHcloud APIs.
 
-```bash
-$ terraform init
-```
+To retrieve this necessary information, please follow the tutorial [First steps with the OVHcloud APIs](/pages/manage_and_operate/api/first-steps).
 
-#### Plan
+Once you've successfully generated your OVHcloud tokens, keep them. You'll need to set them in the next few minutes.
 
-With the following command, you will see what are the actions that Terraform is going to perform:
+The last piece of information you'll need is the `service_name`: this is the ID of your Public Cloud project.
 
-```bash
-$ terraform plan
-```
-
-Now let's have a look at the content of the `main.tf` file:
+How do I get it?
 
-- The *variable* block defines the region and s3 endpoint that are used to create the bucket. You can update it according to your needs : check this [page](/pages/storage_and_backup/object_storage/s3_location) to know what region / endpoints are available.
-- The *Providers* block defines 2 providers : ovh and Hashicorp AWS one. The first one is necessary to create the user whose identity / credentials will be used for the latest.
-- The *User / Credential* block defines the user & credential that are visible in the Settings > Users & Roles tab. They are needed to configure the Hashicorp AWS provider.
-- The Bucket block defines the bucket itself.
-- The Output defines the access & secret key that may be useful for CLI usage.
+In the Public Cloud section, you can retrieve your service name ID using the `Copy to clipboard`{.action} button.
 
-#### Run
+![Copy paste service name](images/get-service-name.png){.thumbnail}
 
-```bash
-$ terraform apply
-```
+You can also use this information in Terraform resource definition files.
 
-Now you can go in the Console and check the "Object Storage" tab. Your bucket is created.
-
-#### Destroy
+## Instructions
 
-With the following command you will be back to your original state: Terraform will destroy all the resources that were previously created.
+If you would like to access the provider's documentation on Object Storage, [click here](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage.){.external}
 
-```bash
-$ terraform destroy
-```
+### Configuration
 
-> [!primary]
->
-> - This script does not follow Terraform best practices to split the project in multiple files e.g. **`provider.tf`, `main.tf`, `variables.tf`, `outputs.tf`**, ... This has been done intentionnaly to avoid switching into multiples files for what is a really simple example.
-> - The secret that is created by this script is stored in the [local](https://developer.hashicorp.com/terraform/language/settings/backends/local) state back-end. If you use this back-end in production, make sure to consider the state file as a secret.
+First, create a `provider.tf` file with the minimum version, the European endpoint (“ovh-eu”) and the keys you obtained in this guide.
 
-### Automating Object Storage policies with Terraform
-
-#### Initialize
-
-Clone the repository:
+Terraform:
 
 ```bash
-git clone https://github.com/yomovh/tf-at-ovhcloud && cd tf-at-ovhcloud/s3_policy
+terraform {
+  required_providers {
+    ovh = {
+      source  = "ovh/ovh"
+      version = "2.1.0" # greater than or equal to 2.0
+    }
+  }
+}
+
+provider "ovh" {
+  endpoint           = "ovh-eu"
+  application_key    = "<your_access_key>"
+  application_secret = "<your_application_secret>"
+  consumer_key       = "<your_consumer_key>"
+}
 ```
 
-Initialize Terraform:
-
-```bash
-$ terraform init
+Here, we've defined the `ovh-eu` endpoint because we want to call the OVHcloud Europe API, but other endpoints exist, depending on your needs:
+
+- `ovh-eu` pour OVHcloud Europe API
+- `ovh-us` pour OVHcloud US API
+- `ovh-ca` pour OVHcloud North-America API
+
+### Create a bucket
+
+You can create a file named 'object_storage_simple.tf' and write the following:
+
+```python
+# Create an Object Storage bucket
+resource "ovh_cloud_project_storage" "my-bucket" {
+ service_name = "my_service_name" # Replace with your OVHcloud project ID
+ region_name = "GRA" # Replace with the desired region in uppercase.
+  name = "object-storage-simple"
+  versioning = {
+    status = "enabled"
+  }
+  encryption = {
+    sse_algorithm = "AES256"
+  }
+}
 ```
 
-#### Plan
-
-With the following command, you will see what are the actions that Terraform is going to perform:
+You can create your resource by entering the following command:
 
 ```bash
-$ terraform plan
+terraform apply
 ```
 
-Now let's have a look at the content of the `main.tf` file and compare it with the previous example:
+### Delete a bucket
 
-- The *User / Credential* block defines 3 users and credentials : one user will be administrator of the bucket and create it, the two others will have read/write & read-only access.
-- In the *Bucket* block we have added the creation of a file into the bucket
-- The *Policy* block defines 2 policies, one for read/write and the other for read-only on the bucket.
-
-#### Run
+You can delete your bucket and all the objects it contains by entering the following command:
 
 ```bash
-$ terraform apply
+terraform destroy
 ```
 
-Now you can go in the Console and check the "Object Storage" tab. You will see the bucket and the file.
-
-You can also check the access right by using the AWS CLI with the 2 users that have the read / write & read-only access
-
-#### Destroy
-
-With the following command you will be back to your original state: Terraform will destroy all the resources that were previously created.
-
-```bash
-$ terraform destroy
-```
+> [!primary]
+>
+> This process may fail if the bucket contains locked objects. In this case, you'll need to delete these objects manually before you can run the command again.
+>
 
 ## Go further
 
diff --git a/pages/storage_and_backup/object_storage/s3_terraform/guide.pt-pt.md b/pages/storage_and_backup/object_storage/s3_terraform/guide.pt-pt.md
index edacb1cb9dc..340f5d4c8f4 100644
--- a/pages/storage_and_backup/object_storage/s3_terraform/guide.pt-pt.md
+++ b/pages/storage_and_backup/object_storage/s3_terraform/guide.pt-pt.md
@@ -1,145 +1,116 @@
 ---
 title: Object Storage - Gerenciar um bucket Object Storage com Terraform (EN)
-updated: 2024-08-27
+updated: 2025-05-05
 ---
 
 ## Objective
 
-This tutorial will show you how to automate some actions on Object Storage with Terraform which is an open source tool to automate infrastructure provisioning. The following actions will be automated:
-
-- Object Storage user creation
-- bucket creation
-- file copy into the bucket
-- S3 **\*** policies and assignment
+This tutorial will help you automate and orchestrate actions to use the [Object Storage](/pages/storage_and_backup/object_storage/s3_getting_started_with_object_storage) - S3* API with Terraform. Terraform is an open source tool for orchestrating the provisioning of resources.
 
 ## Requirements
 
-- Have terraform command line installed (see this [tutorial](https://developer.hashicorp.com/terraform/tutorials/aws-get-started/install-cli) from Hashicorp, the company behind Terraform). 
-- Have git command line installed
-- You will need to have set up an account to interact with the OVHcloud API (see this [tutorial](/pages/manage_and_operate/api/first-steps)). Depending on your needs in terms of permissions (http verbs PUT/GET/POST/DELETE), enter the route `/cloud/project/{serviceName}/region/{regionName}/storage/` to target object storage where *{serviceName}* corresponds to your Public Cloud project id and *{regionName}* corresponds to the region where your resources will be located. From the application keys created, you will need to export the 4 environment variables :
-
-```bash
-$ export OVH_ENDPOINT=ovh-eu
-$ export OVH_APPLICATION_KEY=Your_key_application_OVH(or_AK)
-$ export OVH_APPLICATION_SECRET=Your_secret_application_key_OVH(or_AS)
-$ export OVH_CONSUMER_KEY=Your_token(or_CK)
-```   
-
-- A Public Cloud project, with the ID exported as the variable `TF_VAR_OVH_PUBLIC_CLOUD_PROJECT_ID`
-
-```bash
-$ export TF_VAR_OVH_PUBLIC_CLOUD_PROJECT_ID=Your_public_cloud_project_id
-```
-
-**If you do not have your AWS CLI** configured, you should set dummy values with the following. This is due to a limitation in Terraform dependency graph for providers initialization (see this long lasting terraform [issue)](https://github.com/hashicorp/terraform/issues/2430)):
-
-```bash
-$ export AWS_ACCESS_KEY_ID="no_need_to_define_an_access_key"  
-$ export AWS_SECRET_ACCESS_KEY="no_need_to_define_a_secret_key"
-```
-
-## Instructions
+- Installation of the [Terraform CLI](https://www.terraform.io/downloads.html){.external}
+- Access to the [OVHcloud API](/links/api) (create your login by consulting [this guide](/pages/manage_and_operate/api/first-steps))
+- A [Public Cloud project](/links/public-cloud/public-cloud) in your OVHcloud account.
+- OVHcloud provides a [Terraform provider](https://registry.terraform.io/providers/ovh/ovh/latest){.external} which is available in the official Terraform registry. You must have installed a version >= 2.0. You can follow this guide [How to use Terraform on the OVHcloud Public Cloud](/pages/public_cloud/compute/how_to_use_terraform).
 
-### Manage an Object Storage bucket with terraform @OVHcloud
+## Getting information on your cluster/API tokens
 
-#### Initialize
+The “OVH provider” must be configured with a set of credentials:
 
-Clone the repository:
+- an `application_key`
+- an `application_secret`
+- a `consumer_key`
 
-```bash
-git clone https://github.com/yomovh/tf-at-ovhcloud && cd tf-at-ovhcloud/s3_bucket_only
-```
+Why?
 
-Initialize Terraform:
+Because, behind the scenes, the OVH Terraform provider makes requests to the OVHcloud APIs.
 
-```bash
-$ terraform init
-```
+To retrieve this necessary information, please follow the tutorial [First steps with the OVHcloud APIs](/pages/manage_and_operate/api/first-steps).
 
-#### Plan
+Once you've successfully generated your OVHcloud tokens, keep them. You'll need to set them in the next few minutes.
 
-With the following command, you will see what are the actions that Terraform is going to perform:
+The last piece of information you'll need is the `service_name`: this is the ID of your Public Cloud project.
 
-```bash
-$ terraform plan
-```
-
-Now let's have a look at the content of the `main.tf` file:
+How do I get it?
 
-- The *variable* block defines the region and s3 endpoint that are used to create the bucket. You can update it according to your needs : check this [page](/pages/storage_and_backup/object_storage/s3_location) to know what region / endpoints are available.
-- The *Providers* block defines 2 providers : ovh and Hashicorp AWS one. The first one is necessary to create the user whose identity / credentials will be used for the latest.
-- The *User / Credential* block defines the user & credential that are visible in the Settings > Users & Roles tab. They are needed to configure the Hashicorp AWS provider.
-- The Bucket block defines the bucket itself.
-- The Output defines the access & secret key that may be useful for CLI usage.
+In the Public Cloud section, you can retrieve your service name ID using the `Copy to clipboard`{.action} button.
 
-#### Run
+![Copy paste service name](images/get-service-name.png){.thumbnail}
 
-```bash
-$ terraform apply
-```
+You can also use this information in Terraform resource definition files.
 
-Now you can go in the Console and check the "Object Storage" tab. Your bucket is created.
-
-#### Destroy
+## Instructions
 
-With the following command you will be back to your original state: Terraform will destroy all the resources that were previously created.
+If you would like to access the provider's documentation on Object Storage, [click here](https://registry.terraform.io/providers/ovh/ovh/latest/docs/resources/cloud_project_storage.){.external}
 
-```bash
-$ terraform destroy
-```
+### Configuration
 
-> [!primary]
->
-> - This script does not follow Terraform best practices to split the project in multiple files e.g. **`provider.tf`, `main.tf`, `variables.tf`, `outputs.tf`**, ... This has been done intentionnaly to avoid switching into multiples files for what is a really simple example.
-> - The secret that is created by this script is stored in the [local](https://developer.hashicorp.com/terraform/language/settings/backends/local) state back-end. If you use this back-end in production, make sure to consider the state file as a secret.
+First, create a `provider.tf` file with the minimum version, the European endpoint (“ovh-eu”) and the keys you obtained in this guide.
 
-### Automating Object Storage policies with Terraform
-
-#### Initialize
-
-Clone the repository:
+Terraform:
 
 ```bash
-git clone https://github.com/yomovh/tf-at-ovhcloud && cd tf-at-ovhcloud/s3_policy
+terraform {
+  required_providers {
+    ovh = {
+      source  = "ovh/ovh"
+      version = "2.1.0" # greater than or equal to 2.0
+    }
+  }
+}
+
+provider "ovh" {
+  endpoint           = "ovh-eu"
+  application_key    = "<your_access_key>"
+  application_secret = "<your_application_secret>"
+  consumer_key       = "<your_consumer_key>"
+}
 ```
 
-Initialize Terraform:
-
-```bash
-$ terraform init
+Here, we've defined the `ovh-eu` endpoint because we want to call the OVHcloud Europe API, but other endpoints exist, depending on your needs:
+
+- `ovh-eu` pour OVHcloud Europe API
+- `ovh-us` pour OVHcloud US API
+- `ovh-ca` pour OVHcloud North-America API
+
+### Create a bucket
+
+You can create a file named 'object_storage_simple.tf' and write the following:
+
+```python
+# Create an Object Storage bucket
+resource "ovh_cloud_project_storage" "my-bucket" {
+ service_name = "my_service_name" # Replace with your OVHcloud project ID
+ region_name = "GRA" # Replace with the desired region in uppercase.
+  name = "object-storage-simple"
+  versioning = {
+    status = "enabled"
+  }
+  encryption = {
+    sse_algorithm = "AES256"
+  }
+}
 ```
 
-#### Plan
-
-With the following command, you will see what are the actions that Terraform is going to perform:
+You can create your resource by entering the following command:
 
 ```bash
-$ terraform plan
+terraform apply
 ```
 
-Now let's have a look at the content of the `main.tf` file and compare it with the previous example:
+### Delete a bucket
 
-- The *User / Credential* block defines 3 users and credentials : one user will be administrator of the bucket and create it, the two others will have read/write & read-only access.
-- In the *Bucket* block we have added the creation of a file into the bucket
-- The *Policy* block defines 2 policies, one for read/write and the other for read-only on the bucket.
-
-#### Run
+You can delete your bucket and all the objects it contains by entering the following command:
 
 ```bash
-$ terraform apply
+terraform destroy
 ```
 
-Now you can go in the Console and check the "Object Storage" tab. You will see the bucket and the file.
-
-You can also check the access right by using the AWS CLI with the 2 users that have the read / write & read-only access
-
-#### Destroy
-
-With the following command you will be back to your original state: Terraform will destroy all the resources that were previously created.
-
-```bash
-$ terraform destroy
-```
+> [!primary]
+>
+> This process may fail if the bucket contains locked objects. In this case, you'll need to delete these objects manually before you can run the command again.
+>
 
 ## Go further
 
diff --git a/pages/storage_and_backup/object_storage/s3_terraform/images/get-service-name.png b/pages/storage_and_backup/object_storage/s3_terraform/images/get-service-name.png
new file mode 100644
index 00000000000..0b2140b4644
Binary files /dev/null and b/pages/storage_and_backup/object_storage/s3_terraform/images/get-service-name.png differ