> For the complete documentation index, see [llms.txt](https://docs.apono.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apono.io/docs/additional-integrations/monitoring/datadog.md).

# Datadog

Datadog is a monitoring and observability platform that centralizes metrics, traces, and logs across applications and infrastructure. It uses role-based access control (RBAC) to manage user permissions.

Through this integration, Apono helps you discover Datadog roles and securely manage membership in those roles.

***

### Prerequisites

<table><thead><tr><th width="234.234375">Item</th><th>Description</th></tr></thead><tbody><tr><td><strong>Apono Connector</strong></td><td><p>On-prem connection serving as a bridge between your Datadog instance and Apono:</p><ul><li><a href="/pages/U4HFH35XWDo3jyqhJqgQ">AWS</a></li><li><a href="/pages/ztAsRPKJcMNxeQKE2GNB">Azure</a></li><li><a href="/pages/xPrzAcLGsoliEpPJuozp">GCP</a></li><li><a href="/pages/p5PzUV4THznqePSTYgEH">Kubernetes</a></li></ul><p>Learn how to update an existing <a href="/pages/cNMceTvopbZdVqebcrk5">AWS</a>, <a href="/pages/qX1nxTxfqQ683NIJVRn5">Azure</a>, <a href="/pages/TmT0CXNeTeCE9vImZPl4">GCP</a>, or <a href="/pages/PGql18C6xhmOlcwdDh6b">Kubernetes</a> connector.</p></td></tr><tr><td><strong>Datadog Account Access</strong></td><td>Datadog account with the <strong>User Access Manage</strong> permission that can create the API and application keys</td></tr><tr><td><strong>Datadog Site</strong></td><td><p>Datadog site that hosts your organization</p><p><strong>Possible values</strong>:</p><ul><li>(Default) <strong>US1</strong> (datadoghq.com)</li><li><strong>AP1</strong> (ap1.datadoghq.com)</li><li><strong>AP2</strong> (ap2.datadoghq.com)</li><li><strong>EU1</strong> (datadoghq.eu)</li><li><strong>US3</strong> (us3.datadoghq.com)</li><li><strong>US5</strong> (us5.datadoghq.com)</li></ul><p><strong>NOTE</strong>: Government (<strong>FED</strong>) sites are not supported.</p></td></tr></tbody></table>

***

### Create connector credentials

To enable Apono to discover Datadog roles and manage role membership, you must create an API key and a scoped application key in Datadog.

Follow these steps to create the credentials:

1. In Datadog, on the [**Service Accounts**](https://app.datadoghq.com/organization-settings/service-accounts) page, [create a service account](https://docs.datadoghq.com/account_management/org_settings/service_accounts/#create-service-account) for Apono.

{% hint style="warning" %}
Assign either the **Datadog Admin** role or a [custom role](https://docs.datadoghq.com/account_management/rbac/permissions/#custom-roles) that has the **User Access Manage** (`user_access_manage`) permission. This enables Apono to read roles and assign or unassign users.
{% endhint %}

2. For the service account, create an [API key](https://docs.datadoghq.com/account_management/api-app-keys/#add-an-api-key-or-client-token) and copy its value.
3. For the same service account, create an [application key](https://docs.datadoghq.com/account_management/api-app-keys/#add-application-keys) and copy its value.

{% hint style="warning" %}
Under **Scopes**, grant only `user_access_manage`.
{% endhint %}

4. [Create a secret](/docs/connectors-and-secrets/apono-integration-secret.md) with the credentials from steps **2** and **3**.

   Use the following key-value pair structure when generating the secret. Be sure to replace `<API_KEY>` and `<APPLICATION_KEY>` with the actual values.

{% code overflow="wrap" expandable="true" %}

```
"api_key": "<API_KEY>", 
"application_key": "<APPLICATION_KEY>"
```

{% endcode %}

{% hint style="success" icon="lightbulb" %}
You can also input the user credentials directly into the Apono UI during the [integration process](#integrate-elastic-cloud).
{% endhint %}

***

### Integrate Datadog

<figure><img src="/files/HRhz8AV0mK0BgBHX6Rk9" alt="" width="563"><figcaption><p><em>Datadog resource tile</em></p></figcaption></figure>

{% hint style="success" %}
You can also use the steps below to integrate with Apono using Terraform.

In step **11**, instead of clicking **Confirm**, follow the **Are you integrating with Apono using Terraform?** guidance.
{% endhint %}

Follow these steps to complete the integration:

1. On the [**Catalog**](https://app.apono.io/catalog?search=elastic+cloud) tab, click **Datadog**. The **Connect Integration** page appears.
2. Under **Discovery**, click **Next**. The **Apono connector** section expands.
3. From the dropdown menu, select a connector. Choosing a connector links Apono to all the services available on the account where the connector is located.

{% hint style="success" %}
If the desired connector is not listed, click **New Connector** and follow the instructions for creating a connector ([AWS](/docs/aws-environment/apono-connector-for-aws.md), [Azure](/docs/azure-environment/apono-connector-for-azure.md), [GCP](/docs/gcp-environment/apono-connector-for-gcp.md), [Kubernetes](/docs/kubernetes-environment/apono-connector-for-kubernetes.md)).
{% endhint %}

4. Click **Next**. The **Integration Config** section expands.
5. Define the **Integration Config** settings.

   <table><thead><tr><th width="224">Setting</th><th>Description</th></tr></thead><tbody><tr><td><strong>Integration Name</strong></td><td>Unique, alphanumeric, user-friendly name used to identify the integration when constructing an access flow</td></tr><tr><td><strong>Datadog Site</strong></td><td><p>Datadog site that hosts your organization</p><p>Select the site that matches the domain you use to sign in to Datadog.</p></td></tr></tbody></table>
6. Click **Next**. The **Secret Store** section expands.
7. [Associate the secret or credentials](/docs/connectors-and-secrets/apono-integration-secret.md).

{% hint style="info" %}
If you select the Apono secret manager, enter the values of the **Datadog API Key** and **Datadog Application Key**.
{% endhint %}

8. Click **Next**. The **Get more with Apono** section expands.
9. Define the **Get more with Apono** settings.

   <table><thead><tr><th width="224">Setting</th><th>Description</th></tr></thead><tbody><tr><td><strong>Custom Access Details</strong></td><td>(Optional) Instructions explaining how to access this integration's resources<br><br>Upon accessing an integration, a message with these instructions will be displayed to end users in the User Portal. The message may include up to <strong>400 characters</strong>.<br><br>To view the message as it appears to end users, click <strong>Preview</strong>.</td></tr><tr><td><strong>Integration Owner</strong></td><td><p>(Optional) Fallback approver if no <a href="/pages/Ey4wuziyr2BzKYQnd5am">resource owner</a> is found<br><br>Follow these steps to define one or several integration owners:</p><ol><li>From the <strong>Attribute</strong> dropdown menu, select <strong>User</strong> or <strong>Group</strong> under the relevant identity provider (IdP) platform.</li><li>From the <strong>Value</strong> dropdown menu, select one or multiple users or groups.</li></ol><p><br><strong>NOTE</strong>: When <strong>Resource Owner</strong> is defined, an <strong>Integration Owner</strong> must be defined.</p></td></tr><tr><td><strong>Resource Owner</strong></td><td><p>(Optional) Group or role responsible for managing access approvals or rejections for the resource<br><br>Follow these steps to define one or several <a href="/pages/Ey4wuziyr2BzKYQnd5am">resource owners</a>:</p><ol><li>Enter a <strong>Key name</strong>. This value is the name of the tag created in your cloud environment.</li><li>From the <strong>Attribute</strong> dropdown menu, select an attribute under the IdP platform to which the key name is associated.<br><br>Apono will use the value associated with the key (tag) to identify the resource owner. When you update the membership of the group or role in your IdP platform, this change is also reflected in Apono.</li></ol><p><br><strong>NOTE</strong>: When this setting is defined, an <strong>Integration Owner</strong> must also be defined.</p></td></tr></tbody></table>
10. (Recommended) Click **Test Integration** to validate the integration.

{% hint style="info" %}
**Test Integration** is available after you have entered or selected values for all required integration fields.

During the test, Apono runs the following validation checks:

* Integration reachability
* Target host connectivity
* Credential validity
* Resource discovery

The **Test Validation** checklist shows the result of each check.

<img src="/files/pbwu1vBf54x16eGs1IjP" alt="" data-size="original">

If a check fails, Apono identifies the failed check and highlights the fields that need correction.
{% endhint %}

11. Click **Confirm**.

<details>

<summary>💡 Are you integrating with Apono using Terraform?</summary>

If you want to integrate with Apono using Terraform, follow these steps instead of clicking **Confirm**:

1. At the top of the screen, click **View as Code**. A modal appears with the completed Terraform configuration code.
2. Click to copy the code.
3. Make any additional edits.
4. Deploy the code in your Terraform.

Refer to [Integration Config Metadata](https://docs.apono.io/metadata-for-integration-config/integration-metadata/datadog) for more details about the schema definition.

</details>

#### Usage

Now that the integration is complete, you can add Datadog roles as resources in an access flow. This allows requesters to securely request temporary membership in those roles based on your approval and provisioning rules.

Follow the guidance in these articles to define Datadog roles as resources:

* [Define the resource (Self Serve Access Flows)](/docs/access-flows/creating-access-flows-in-apono/self-serve-access-flows.md#define-the-resource)
* [Define the resource (Automatic Access Flows)](/docs/access-flows/creating-access-flows-in-apono/automatic-access-flows.md#define-the-resource)


---

# 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.apono.io/docs/additional-integrations/monitoring/datadog.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.