Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,8 @@ If you're [using the Iceberg framework in AWS Glue][5], you can see metadata fro
Before you begin, make sure you have:

- An AWS account with Glue Iceberg tables you want to monitor.
- The [Datadog AWS integration][1] configured for the account.
- An [AWS account connected in Datadog][1].
- Log forwarding is not required for Data Observability.
- IAM permissions to modify the Datadog role's policies.
- (Optional) AWS Lake Formation access if you use it to manage table permissions.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,8 @@ Datadog supports both provisioned Redshift clusters and Redshift Serverless work

Before you begin, make sure you have:

- An [AWS account connected in Datadog][3].
- Log forwarding is not required for Data Observability.
- A Redshift superuser or database user with the ability to create roles and grant privileges.
- If your Redshift cluster or workgroup restricts network access by IP, add Datadog webhook IPs to your VPC security group inbound rules. For the list of IPs, see the `webhooks` section of the {{< region-param key="ip_ranges_url" link="true" text="IP ranges list" >}}.

Expand Down Expand Up @@ -183,4 +185,5 @@ After the initial sync completes, create a [Data Observability monitor][2] to st
{{< partial name="whats-next/whats-next.html" >}}

[1]: https://app.datadoghq.com/datasets/settings/integrations
[2]: /monitors/types/data_observability/
[2]: /monitors/types/data_observability/
[3]: /integrations/amazon-web-services/
Loading