docs: Updated bucket names and added warning (#13347)

Co-authored-by: J Stickler <[email protected]>

docs/sources/setup/install/helm/install-microservices/_index.md

@@ -167,6 +167,10 @@ It is not recommended to run scalable mode with `filesystem` storage. For the pu
 
 After testing Loki with MinIO, it is recommended to configure Loki with an object storage provider. The following examples shows how to configure Loki with different object storage providers:
 
+{{< admonition type="caution" >}}
+When deploying Loki using S3 Storage **DO NOT** use the default bucket names;  `chunk`, `ruler` and `admin`. Choose a unique name for each bucket. For more information see the following [security update](https://grafana.com/blog/2024/06/27/grafana-security-update-grafana-loki-and-unintended-data-write-attempts-to-amazon-s3-buckets/). This caution does not apply when you are using MinIO. When using MinIO we recommend using the default bucket names.
+{{< /admonition >}}
+
 {{< code >}}
 
 ```s3
@@ -192,9 +196,9 @@ After testing Loki with MinIO, it is recommended to configure Loki with an objec
     storage:
       type: s3
       bucketNames:
-        chunks: "chunks"
-        ruler: "ruler"
-        admin: "admin"
+        chunks: "<INSERT BUCKET NAME>"
+        ruler: "<INSERT BUCKET NAME>"
+        admin: "<INSERT BUCKET NAME>"
       s3:
         # s3 URL can be used to specify the endpoint, access key, secret key, and bucket name
         s3: s3://access_key:secret_access_key@custom_endpoint/bucket_name
@@ -343,4 +347,4 @@ To configure other storage providers, refer to the [Helm Chart Reference]({{< re
 
 ## Next Steps 
 * Configure an agent to [send log data to Loki](/docs/loki/<LOKI_VERSION>/send-data/).
-* Monitor the Loki deployment using the [Meta Monitoring Healm chart](/docs/loki/<LOKI_VERSION>/setup/install/helm/monitor-and-alert/)
+* Monitor the Loki deployment using the [Meta Monitoring Helm chart](/docs/loki/<LOKI_VERSION>/setup/install/helm/monitor-and-alert/)

docs/sources/setup/install/helm/install-scalable/_index.md

@@ -128,6 +128,10 @@ It is not recommended to run scalable mode with `filesystem` storage. For the pu
 
 After testing Loki with MinIO, it is recommended to configure Loki with an object storage provider. The following examples shows how to configure Loki with different object storage providers:
 
+{{< admonition type="caution" >}}
+When deploying Loki using S3 Storage **DO NOT** use the default bucket names;  `chunk`, `ruler` and `admin`. Choose a unique name for each bucket. For more information see the following [security update](https://grafana.com/blog/2024/06/27/grafana-security-update-grafana-loki-and-unintended-data-write-attempts-to-amazon-s3-buckets/). This caution does not apply when you are using MinIO. When using MinIO we recommend using the default bucket names.
+{{< /admonition >}}
+
 {{< code >}}
 
 ```s3
@@ -151,9 +155,9 @@ loki:
   storage:
     type: s3
     bucketNames:
-      chunks: "chunks"
-      ruler: "ruler"
-      admin: "admin"
+      chunks: "<INSERT BUCKET NAME>"
+      ruler: "<INSERT BUCKET NAME>"
+      admin: "<INSERT BUCKET NAME>"
     s3:
       # s3 URL can be used to specify the endpoint, access key, secret key, and bucket name
       s3: s3://access_key:secret_access_key@custom_endpoint/bucket_name
@@ -295,4 +299,4 @@ To configure other storage providers, refer to the [Helm Chart Reference]({{< re
 
 ## Next Steps 
 * Configure an agent to [send log data to Loki](/docs/loki/<LOKI_VERSION>/send-data/).
-* Monitor the Loki deployment using the [Meta Monitoring Healm chart](/docs/loki/<LOKI_VERSION>/setup/install/helm/monitor-and-alert/)
+* Monitor the Loki deployment using the [Meta Monitoring Helm chart](/docs/loki/<LOKI_VERSION>/setup/install/helm/monitor-and-alert/)