Add minor fixes (#29401)

* Add minor fixes

* Relative reference link

---------

Co-authored-by: Esther Kim <[email protected]>

Author: guilload

content/en/cloudprem/_index.md

@@ -1,7 +1,7 @@
 ---
 title: CloudPrem
 description: Learn how to deploy and manage Datadog CloudPrem, a self-hosted log management solution for cost-effective log ingestion, processing, indexing, and search capabilities
-private: true 
+private: true
 ---
 
 <div class="alert alert-warning">CloudPrem is in Preview.</div>
@@ -25,7 +25,7 @@ Datadog CloudPrem is a self-hosted log management solution that enables cost-eff
 {{< /whatsnext >}}
 
 
-[1]: https://kubernetes-sigs.github.io/aws-load-balancer-controller/latest/deploy/installation/ 
+[1]: https://kubernetes-sigs.github.io/aws-load-balancer-controller/latest/deploy/installation/
 [2]: /cloudprem/installation/
 [3]: /cloudprem/processing/
-[4]: /cloudprem/architecture/
+[4]: /cloudprem/architecture/

content/en/cloudprem/architecture.md

@@ -40,14 +40,17 @@ The CloudPrem cluster, typically deployed on Kubernetes (EKS), consists of sever
 : Responsible for receiving logs from Datadog Agents. Indexers process, index, and store logs in index files called _splits_ to the object storage (for example, Amazon S3).
 
 **Searchers**
-: Handle search queries from the Datadog UI, reading metadata from Metastore and index data from the object storage.
+: Handle search queries from the Datadog UI, reading metadata from Metastore and fetching data from the object storage.
 
 **Metastore**
-: Stores metadata about the indexes, including splits locations on the object storage. CloudPrem uses PostgreSQL for this purpose.
+: Stores metadata about the indexes, including split locations on the object storage. CloudPrem uses PostgreSQL for this purpose.
 
-**Janitor/Control Plane**
-: Responsible for tasks like indexing tasks scheduling and delete tasks.
+**Control Plane**
+: Schedules indexing jobs called _indexing pipelines_ on indexers.
+
+**Janitor**
+: Performs maintenance tasks, applying retention policies, garbage collecting expired splits, and running delete query jobs.
 
 ## Further reading
 
-{{< partial name="whats-next/whats-next.html" >}}
+{{< partial name="whats-next/whats-next.html" >}}

content/en/cloudprem/aws_config.md

@@ -35,9 +35,9 @@ To deploy CloudPrem on AWS, you need to configure:
 
 When starting a node, CloudPrem attempts to find AWS credentials using the credential provider chain implemented by [rusoto\_core::ChainProvider][2] and looks for credentials in this order:
 
-1. Environment variables `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`, or `AWS_SESSION_TOKEN` (optional).  
-2. Credential profiles file, typically located at `~/.aws/credentials` or otherwise specified by the `AWS_SHARED_CREDENTIALS_FILE` and `AWS_PROFILE` environment variables if set and not empty.  
-3. Amazon ECS container credentials, loaded from the Amazon ECS container if the environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is set.  
+1. Environment variables `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`, or `AWS_SESSION_TOKEN` (optional).
+2. Credential profiles file, typically located at `~/.aws/credentials` or otherwise specified by the `AWS_SHARED_CREDENTIALS_FILE` and `AWS_PROFILE` environment variables if set and not empty.
+3. Amazon ECS container credentials, loaded from the Amazon ECS container if the environment variable `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` is set.
 4. Instance profile credentials, used on Amazon EC2 instances, and delivered through the Amazon EC2 metadata service.
 
 An error is returned if no credentials are found in the chain.
@@ -46,20 +46,20 @@ An error is returned if no credentials are found in the chain.
 
 CloudPrem attempts to find the AWS region from multiple sources, using the following order of precedence:
 
-1. **Environment variables**: Checks `AWS_REGION`, then `AWS_DEFAULT_REGION`.  
-2. **AWS config file**: Typically located at `~/.aws/config`, or at the path specified by the `AWS_CONFIG_FILE` environment variable (if set and not empty).  
-3. **EC2 instance metadata**: Uses the region of the currently running Amazon EC2 instance.  
+1. **Environment variables**: Checks `AWS_REGION`, then `AWS_DEFAULT_REGION`.
+2. **AWS config file**: Typically located at `~/.aws/config`, or at the path specified by the `AWS_CONFIG_FILE` environment variable (if set and not empty).
+3. **EC2 instance metadata**: Uses the region of the currently running Amazon EC2 instance.
 4. **Default**: Falls back to `us-east-1` if no other source provides a region.
 
 ## IAM permissions for S3
 
 Required authorized actions:
 
-* `ListBucket` (on the bucket directly)  
-* `GetObject`  
-* `PutObject`  
-* `DeleteObject`  
-* `ListMultipartUploadParts`  
+* `ListBucket` (on the bucket directly)
+* `GetObject`
+* `PutObject`
+* `DeleteObject`
+* `ListMultipartUploadParts`
 * `AbortMultipartUpload`
 
 Here is an example of a bucket policy:
@@ -97,7 +97,7 @@ Here is an example of a bucket policy:
 
 ## Further reading
 
-{{< partial name="whats-next/whats-next.html" >}} 
+{{< partial name="whats-next/whats-next.html" >}}
 
 [1]: /cloudprem/ingress/
-[2]: https://docs.rs/rusoto_credential/latest/rusoto_credential/struct.ChainProvider.html
+[2]: https://docs.rs/rusoto_credential/latest/rusoto_credential/struct.ChainProvider.html

content/en/cloudprem/cluster.md

@@ -71,4 +71,4 @@ The following components are typically lightweight:
 
 ## Further reading
 
-{{< partial name="whats-next/whats-next.html" >}} 
+{{< partial name="whats-next/whats-next.html" >}}

content/en/cloudprem/ingress.md

@@ -47,15 +47,15 @@ This setup ensures that only authenticated Datadog services can access the Cloud
 
 {{< img src="/cloudprem/ingress/public_ingress.png" alt="Diagram showing CloudPrem public ingress architecture with Datadog services connecting through an internet-facing AWS ALB using mTLS authentication to access the CloudPrem gRPC API" style="width:100%;" >}}
 
-### IP ranges API
-The Datadog control plane and query services connect to CloudPrem clusters using a set of fixed IP ranges, which can be retrieved for each Datadog site from the Datadog IP Ranges API, specifically under the "webhooks" section. For example, to fetch the IP ranges for the datadoghq.eu site, you can run:
+### IP Allowlisting
+
+The Datadog control plane and query services connect to CloudPrem clusters using a set of fixed IP ranges, which can be retrieved for each Datadog site from the Datadog [IP Ranges API][1], specifically under the "webhooks" section. For example, to fetch the IP ranges for the datadoghq.eu site, you can run:
 ```
 curl -X GET "https://ip-ranges.datadoghq.eu/" \
       -H "Accept: application/json" |
       jq '.webhooks'
 ```
 
-
 ## Internal ingress
 
 The internal ingress enables log ingestion from Datadog Agents and other log collectors within your environment through HTTP.
@@ -89,7 +89,7 @@ rules:
           service:
             name: <RELEASE_NAME>-indexer
             port:
-              name: rest 
+              name: rest
       - path: /api/v2/logs
         pathType: Prefix
         backend:
@@ -120,4 +120,6 @@ rules:
 
 ## Further reading
 
-{{< partial name="whats-next/whats-next.html" >}} 
+{{< partial name="whats-next/whats-next.html" >}}
+
+[1]: /api/latest/ip-ranges/

content/en/cloudprem/installation.md

@@ -50,7 +50,7 @@ Before getting started with CloudPrem, ensure you have:
 3. [Configure the Datadog Agent to send Kubernetes logs](#send-kubernetes-logs-to-cloudprem-with-the-datadog-agent).
 4. [Configure your Datadog account](#configure-your-datadog-account).
 
-## Install the CloudPrem Helm chart 
+## Install the CloudPrem Helm chart
 
 1. Add and update the Datadog Helm repository:
 
@@ -70,7 +70,7 @@ Before getting started with CloudPrem, ensure you have:
    ```bash
    kubectl create secret generic <SECRET_NAME> \
    -n <NAMESPACE_NAME> \
-   --from-literal QW_METASTORE_URI=postgres://<USERNAME>:<PASSWORD>@<ENDPOINT>:<PORT>/<DATABASE> 
+   --from-literal QW_METASTORE_URI=postgres://<USERNAME>:<PASSWORD>@<ENDPOINT>:<PORT>/<DATABASE>
    ```
 
 4. Customize the Helm chart
@@ -200,6 +200,14 @@ Before getting started with CloudPrem, ensure you have:
          memory: "16Gi"
    ```
 
+5. Install or upgrade the Helm chart
+
+   ```bash
+   helm upgrade --install <RELEASE_NAME> datadog/cloudprem \
+   -n <NAMESPACE_NAME> \
+   -f datadog-values.yaml
+   ```
+
    To check if the deployment went well:
    - Look at the logs from the metastore or indexer pod.
    - Look at the status of deployment resources, such as the ingress status.
@@ -224,13 +232,13 @@ spec:
         keyName: api-key
     env:
       - name: DD_LOGS_CONFIG_LOGS_DD_URL
-        value: http://<RELEASE_NAME>-indexer.<NAMESPACE>.svc.cluster.local:7280
+        value: http://<RELEASE_NAME>-indexer.<NAMESPACE_NAME>.svc.cluster.local:7280
 
   features:
     logCollection:
       enabled: true
       containerCollectAll: true
-      
+
     otlp:
       receiver:
         protocols:
@@ -244,7 +252,7 @@ spec:
 
 ```
 
-- Within the cluster, use the indexer service for the logs endpoint URL: `DD_LOGS_CONFIG_LOGS_DD_URL:http://<RELEASE_NAME>-indexer.<NAMESPACE>.svc.cluster.local:7280`.
+- Within the cluster, use the indexer service for the logs endpoint URL: `DD_LOGS_CONFIG_LOGS_DD_URL:http://<RELEASE_NAME>-indexer.<NAMESPACE_NAME>.svc.cluster.local:7280`.
 - Outside the cluster, use the host of the internal ingress.
 - To send cluster metrics to Datadog, enable `prometheusScrape`.
 - To send cluster logs to Datadog, enable `OTLP/gRPC`.
@@ -266,7 +274,7 @@ After your Datadog account is configured, you are ready to search into the `clou
 To uninstall CloudPrem:
 
 ```bash
-helm uninstall <DEPLOYMENT_NAME>
+helm uninstall <RELEASE_NAME>
 ```
 
 ## Further reading

content/en/cloudprem/processing.md

@@ -32,13 +32,13 @@ further_reading:
 
 ## Overview
 
-CloudPrem includes a processing feature that allows you to parse and enrich logs. It automatically parses logs formatted in JSON. You can define pipelines and processors to extract meaningful information or attributes from semi-structured text, which can then be used for aggregations. 
+CloudPrem includes a processing feature that allows you to parse and enrich logs. It automatically parses logs formatted in JSON. You can define pipelines and processors to extract meaningful information or attributes from semi-structured text, which can then be used for aggregations.
 
 <div class="alert alert-info">CloudPrem log pipelines and processors are designed to be match the capabilities of Datadog's <a href="/logs/log_configuration/pipelines/?tab=source">cloud-based log pipelines and processors</a>. </div>
 
 For a list of supported and unsupported processors, see [Compatibility with cloud-based pipelines](#compatibility-with-cloud-based-pipelines).
 
-You configure log processing pipelines using a JSON file that adheres to the same format as Datadog pipeline configurations.
+You can configure log processing pipelines using a JSON file that adheres to the same format as Datadog pipeline configurations.
 
 ## Setting up processing
 
@@ -48,24 +48,24 @@ You configure log processing pipelines using a JSON file that adheres to the sam
    curl -X GET "https://api.datadoghq.com/api/v1/logs/config/pipelines" \
     -H "Accept: application/json" \
     -H "DD-API-KEY: ${DD_API_KEY}" \
-    -H "DD-APPLICATION-KEY: ${DD_APP_KEY}" > my-pipelines_config.json
+    -H "DD-APPLICATION-KEY: ${DD_APP_KEY}" > pipelines-config.json
    ```
 
-   This JSON file can be used directly with CloudPrem.
+This JSON file can be used directly with CloudPrem.
 
 2. To set the configuration in the Helm Chart, provide the path to your JSON configuration file using the `pipelinesConfig` parameter in the CloudPrem Helm chart:
 
    ```bash
    helm repo update
-   helm upgrade <RELEASE_NAME> -n <NAMESPACE> --set-file pipelinesConfig=./pipelines_config.json -f your_custom_values_file.yaml
+   helm upgrade <RELEASE_NAME> -n <NAMESPACE_NAME> --set-file pipelinesConfig=./pipelines-config.json -f datadog-values.yaml
    ```
 
    CloudPrem logs an informational message (`Successfully read pipeline config file`) when it successfully reads the configuration file. Any processors defined in the file that are not supported by CloudPrem are ignored during startup.
    **Note**: Helm imposes a 1 MB size limit on the configuration file due to its underlying etcd storage.
 
 ## Configuration file format
 
-The configuration is a JSON array, where each element represents a processor or a nested pipeline.  
+The configuration is a JSON array, where each element represents a processor or a nested pipeline.
 
 The order of elements in the array defines the sequential execution order of the processors.  The structure mirrors the output of the Datadog API endpoint `api/v1/logs/config/pipelines`.
 
@@ -150,8 +150,8 @@ Ignored processors appear as a warning in the indexer logs.
 
 ## Further reading
 
-{{< partial name="whats-next/whats-next.html" >}} 
+{{< partial name="whats-next/whats-next.html" >}}
 
 [1]: /logs/log_configuration/pipelines/?tab=source
 [2]: /api/latest/logs-pipelines/#get-all-pipelines
-[3]: /logs/log_configuration/processors/
+[3]: /logs/log_configuration/processors/