> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/~/revisions/1AlFSZBNMIBgs7fiOwFD/early-access/logging-service/overview/log-security.md).

# Log Security

The IONOS Logging Service is a versatile and accessible platform that allows you to conveniently store and manage logs from various sources. Whether it's logs generated within the IONOS infrastructure, your own bare metal system, or even from another cloud environment, this platform provides a seamless solution for log aggregation. With its flexibility, you can effortlessly push logs from anywhere, ensuring comprehensive log monitoring and analysis.

All types of communications to push logs (**HTTP** and **TCP**) are protected by the following two mechanisms:

* TLS (Transport Layer Security)
* KEY
  * HTTP: APIKEY Header
  * TCP: SharedKey

The Key brings an extra layer of security with which you can revoke or regenerate the existing key.

## TCP (FluentBit)

When using TCP/TLS, you have to enable `tls` and provide a `Shared_key` (key) in the FluentBit configuration. The key can be obtained via our REST API (ShareOnce Policy)

```editorconfig
[OUTPUT]
    Name            forward
    Match           *
    Port            9000
    Tag             <TAG>
    Host            <TCP_ENDPOINT>
    tls             on
    Shared_Key      <KEY>
```

{% hint style="info" %}
Refer to [FluentBit's official website](https://docs.fluentbit.io/manual/pipeline/outputs/forward) to see the whole parameters.
{% endhint %}

## HTTP (cURL)

If you are planning to use HTTP (JSON), you should provide the key in the header alongside your account email address:

```bash
curl -X "POST" "https://12be6dbe134f-logs.3b0b424eb27f.logging.de-txl.ionos.com/myhttp" \
     -H 'Content-Type: application/json' \
     -H 'APIKEY: <KEY>' \
     -d $'{
  "status": "Ready",
  "ts": 1580306777.04728,
  "pod": {
    "name": "Example Name",
    "namespace": "data"
  },
  "msg": "Pod status updated",
  "level": "error",
  "label_1": "test label"
}'
```

## HTTP (FluentBit)

This is an equivalent example of configuring FluentBit with HTTP outbound:

```editorconfig
[OUTPUT]
    Name            http
    Match           *
    Host            <HTTPS_ENDPOINT>
    URI             /<TAG>
    Format          json
    Header          APIKEY <KEY>
    tls             on
    Port            443
```

{% hint style="info" %}
Refer to [FluentBit's official website](https://docs.fluentbit.io/manual/pipeline/outputs/http) to see the whole parameters.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ionos.com/cloud/~/revisions/1AlFSZBNMIBgs7fiOwFD/early-access/logging-service/overview/log-security.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.