Merge pull request #2994 from SEKOIA-IO/fix/align_https_doc_on_various_regions

fix/align_doc_on_various_regions

Author: alexane-bougeardbebin-sekoia

_shared_content/automate/playbooks-on-premises.md

@@ -71,6 +71,11 @@ To ensure a bug-free installation, the Sekoia Endpoint Agent must be able to com
     - minio-symphony.prod.sekoia.io
     - ...
 
+!!! note
+    The domains listed above apply to the **FRA1** region.
+    For other regions, the agent will communicate with region-specific endpoints (e.g., `app.fra2.sekoia.io`, `api.fra2.sekoia.io` for FRA2 region).
+    The required domains for your region are displayed during the playbook runner installation in the Sekoia.io interface.
+
 ### Testing the prerequisites
 
 We've prepared a Docker image to facilitate the validation process and ensure the environment is properly configured for agent installation.
@@ -83,22 +88,24 @@ docker run ghcr.io/sekoia-io/hello-sekoia:latest
 
 This command will initiate the image download, effectively verifying whether the host system can successfully access the Docker registry and establish connectivity with Sekoia.io.
 
-Here's an example of the expected output for your reference:
+??? example "Example of the expected output (FRA1 region):"
 
-```
-Checking container runs in Docker ... OK
-Checking connectivity with Sekoia.io APIs ...
-  - Checking app.sekoia.io ... OK
-  - Checking api.sekoia.io ... OK
-Checking connectivity with the object storage ... OK
-```
+    ```
+    Checking container runs in Docker ... OK
+    Checking connectivity with Sekoia.io APIs ...
+    - Checking app.sekoia.io ... OK
+    - Checking api.sekoia.io ... OK
+    Checking connectivity with the object storage ... OK
+    ```
 
 !!! tip
     The `-e` option can be passed to the docker command to specify:
 
-    * The region: `-e region=mco1`
-    * Proxy information: `-e https_proxy={proxy_url}`
+    * The region: `-e region=<region>` (e.g., `-e region=mco1` for MCO1 region)
+    * Proxy information: `-e https_proxy=<proxy_url>`
 
+!!! tip
+    Learn more about region and code in [our dedicated article](/getting_started/regions.md).
 
 ## Playbook runners
 
@@ -120,7 +127,10 @@ To create a playbook runner, follow these steps:
 Your newly created playbook runner should now appear in the list. It will also be shown when configuring any playbook action.
 
 !!! tip
-    To specify a region when installing the runner, the `--region` argument can be added to the command.
+    To specify a region when installing the runner, add the `--region` argument to the installation command.
+
+!!! tip
+    Learn more about region and code in [our dedicated article](/getting_started/regions.md).
 
 ### Use a runner in a playbook action
 

docs/integration/ingestion_methods/https/format.md

@@ -1,26 +1,52 @@
 # Formatting options
 
-To forward logs to Sekoia.io, several options format are available:
+To forward logs to Sekoia.io, several formatting options are available:
 
 - Send your events as line-oriented records
 - Send your events as a JSON object
 - Send your events as a structured payload
 
-For each option, we will have to supply an intake key. The collector endpoint of Sekoia.io will provide event identifiers within the Sekoia.io detection workflow in the form of a JSON payload.
+For each option, we have to supply an intake key. The collector endpoint of Sekoia.io will provide event identifiers within the Sekoia.io detection workflow in the form of a JSON payload.
+
+## Select the intake endpoint for your region
+
+Sekoia.io supports multiple regions for HTTP ingestion.
+
+FRA1 keeps the historical URL scheme, while all other regions use the new API-prefixed scheme.
+
+!!! tip
+    Learn more about region and code in [our dedicated article](/getting_started/regions.md).
+
+Endpoints must be built from regional base URLs:
+
+- FRA1 base URL: `https://intake.sekoia.io`
+- Other regions base URL: `https://intake.<region>.sekoia.io/api/v1/intake-http`
+
+Then append the path `/<path>` (e.g., `/plain`, `/plain/batch`, `/jsons`, `/batch`, `/array`, etc.) to the corresponding regional base URL.
+
+Examples:
+
+- `https://intake.sekoia.io/batch`
+- `https://intake.fra2.sekoia.io/api/v1/intake-http/batch`
+- `https://intake.mco1.sekoia.io/api/v1/intake-http/jsons`
+- `https://intake.uae1.sekoia.io/api/v1/intake-http/plain/batch`
+
+!!! warning
+    The examples below use FRA1 URLs for readability. For other regions, replace the base URL with your regional endpoint.
 
 ## Push our events to Sekoia.io as line-oriented records
 
 To forward events as plain records, you can use the `/plain` endpoint.
 
-The following headers are handled by Sekoia.io’S HTTPS log collector:
+The following headers are handled by Sekoia.io's HTTPS log collector:
 
 | Header                       | Mandatory? | Type     | Description                                                                            |
 |------------------------------|------------|----------|----------------------------------------------------------------------------------------|
 | `X-SEKOIAIO-INTAKE-KEY`      | No         | String   | Intake to which you would like to push events to                                       |
 | `X-SEKOIAIO-EVENT-TIMESTAMP` | No         | Datetime | Event date if you want to push your own date (fallback is to use the reception’s date) |
 
 
-Supply the intake key as the header `X-SEKOIAIO-INTAKE-KEY`, as password in the HTTP Basic authentication mechanism or as a parameter in the querystring.
+Supply the intake key as the header `X-SEKOIAIO-INTAKE-KEY`, as password in the HTTP Basic authentication mechanism, or as a parameter in the query string.
 
 To push one event, just POST content to `https://intake.sekoia.io/plain`
 
@@ -121,15 +147,15 @@ curl -X POST -H "X-SEKOIAIO-INTAKE-KEY: REPLACE_BY_INTAKE_KEY" --data-binary @ev
 
 To send us events as a JSON list, you should set `Content-Type` HTTP header to `application/json`.
 
-The following headers are handled by Sekoia.io’S HTTPS log collector:
+The following headers are handled by Sekoia.io's HTTPS log collector:
 
 | Header                       | Mandatory? | Type     | Description                                                                            |
 |------------------------------|------------|----------|----------------------------------------------------------------------------------------|
 | `X-SEKOIAIO-INTAKE-KEY`      | No         | String   | Intake to which you would like to push events to                                       |
 | `X-SEKOIAIO-EVENT-TIMESTAMP` | No         | Datetime | Event date if you want to push your own date (fallback is to use the reception’s date) |
 
 
-Supply the intake key as the header `X-SEKOIAIO-INTAKE-KEY`, as password in the HTTP Basic authentication mechanism or as a parameter in the querystring.
+Supply the intake key as the header `X-SEKOIAIO-INTAKE-KEY`, as password in the HTTP Basic authentication mechanism, or as a parameter in the query string.
 
 Use the endpoint `/jsons`. This endpoint accepts a set of events:
 
@@ -223,11 +249,11 @@ If your events are enclosed in a JSON object, use the endpoint `/jsons` and prov
 
 To send us events, you should set `Content-Type` HTTP header to `application/json`.
 
-The following fields are currently handled by Sekoia.io’S HTTPS log collector:
+The following fields are currently handled by Sekoia.io's HTTPS log collector:
 
 | Field         | Mandatory? | Type     | Description                                                                                            |
 |---------------|------------|----------|--------------------------------------------------------------------------------------------------------|
-| `intakey_key` | Yes        | String   | Intake to which you would like to push events to                                                       |
+| `intake_key`  | Yes        | String   | Intake to which you would like to push events to                                                       |
 | `json`        | Yes        | String   | The actual log payload. If you want to push structured JSON logs, please send them as quoted JSON here |
 | `@timestamp`  | No         | Datetime | Event date if you want to push your own date (fallback is to use the reception’s date)                 |