> For the complete documentation index, see [llms.txt](https://docs.datasentinel.io/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datasentinel.io/manual/features/tips-and-hints/predefined-providers.md).

# Predefined Providers

By assigning a **provider** [Tag](/manual/features/tips-and-hints/tags.md) to an instance, you can easily identify and filter instances according to the platform they are hosted on, such as [Amazon Web Services](https://aws.amazon.com/) (AWS), [Google Cloud Platform](https://cloud.google.com/) (GCP), [Microsoft Azure](https://azure.microsoft.com/), or [Fujitsu Enterprise Postgres](https://www.postgresql.fastware.com/).

{% hint style="info" %}
Omitting the **provider** tag is also an option.
{% endhint %}

## How it Works

In the [Agentless approach](/manual/features/other-features/agentless-monitoring.md), the user interface offers a pre-configured dropdown list for effortless provider selection for your instance.

<figure><img src="/files/nMuBDjoxio9sGgbqWa82" alt=""><figcaption><p>Predefined Providers</p></figcaption></figure>

For alternative configuration methods, such as [Agent-based](/manual/implementation/agent-usage.md) or [API](/manual/implementation/platform-usage/api-reference/connection.md) approaches, specify the **provider** Tag and choose from the predefined options available

* amazon-aws
* microsoft-azure
* google-cloud
* fujitsu-enterprise-postgres

## Interactive Demo

{% hint style="info" %}
The user interface is enriched by adding provider icons next to each related PostgreSQL instance, simplifying both navigation and instance recognition
{% endhint %}

{% @arcade/embed url="<https://app.arcade.software/share/KGeJR2vfK5Oc64RjuMjx>" flowId="KGeJR2vfK5Oc64RjuMjx" %}

> Feel free to request the addition of new providers that align with your needs.


---

# 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.datasentinel.io/manual/features/tips-and-hints/predefined-providers.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.