From bdc1693646ecfe7692693582798849fdbd77c6ec Mon Sep 17 00:00:00 2001 From: Gus Vargas Date: Wed, 24 Jun 2026 16:15:30 -0500 Subject: [PATCH 1/2] Add AWS account prerequisite to Redshift and Glue Data Observability docs --- .../quality_monitoring/data_lakes/aws_glue.md | 2 +- .../quality_monitoring/data_warehouses/redshift.md | 4 +++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/content/en/data_observability/quality_monitoring/data_lakes/aws_glue.md b/content/en/data_observability/quality_monitoring/data_lakes/aws_glue.md index d67fe226769..087b5a86aa4 100644 --- a/content/en/data_observability/quality_monitoring/data_lakes/aws_glue.md +++ b/content/en/data_observability/quality_monitoring/data_lakes/aws_glue.md @@ -22,7 +22,7 @@ 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]. - IAM permissions to modify the Datadog role's policies. - (Optional) AWS Lake Formation access if you use it to manage table permissions. diff --git a/content/en/data_observability/quality_monitoring/data_warehouses/redshift.md b/content/en/data_observability/quality_monitoring/data_warehouses/redshift.md index 793842f5368..25af408b723 100644 --- a/content/en/data_observability/quality_monitoring/data_warehouses/redshift.md +++ b/content/en/data_observability/quality_monitoring/data_warehouses/redshift.md @@ -20,6 +20,7 @@ Datadog supports both provisioned Redshift clusters and Redshift Serverless work Before you begin, make sure you have: +- An [AWS account connected in Datadog][3]. - 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" >}}. @@ -183,4 +184,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/ \ No newline at end of file +[2]: /monitors/types/data_observability/ +[3]: /integrations/amazon-web-services/ \ No newline at end of file From c632968a17f547b2ddaf24421b7ac1b3b1b505d8 Mon Sep 17 00:00:00 2001 From: Gus Vargas Date: Thu, 25 Jun 2026 10:28:41 -0500 Subject: [PATCH 2/2] Note log forwarding not required for Data Observability --- .../data_observability/quality_monitoring/data_lakes/aws_glue.md | 1 + .../quality_monitoring/data_warehouses/redshift.md | 1 + 2 files changed, 2 insertions(+) diff --git a/content/en/data_observability/quality_monitoring/data_lakes/aws_glue.md b/content/en/data_observability/quality_monitoring/data_lakes/aws_glue.md index 087b5a86aa4..c0a5dfa37fe 100644 --- a/content/en/data_observability/quality_monitoring/data_lakes/aws_glue.md +++ b/content/en/data_observability/quality_monitoring/data_lakes/aws_glue.md @@ -23,6 +23,7 @@ Before you begin, make sure you have: - An AWS account with Glue Iceberg tables you want to monitor. - 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. diff --git a/content/en/data_observability/quality_monitoring/data_warehouses/redshift.md b/content/en/data_observability/quality_monitoring/data_warehouses/redshift.md index 25af408b723..4ba0e38da19 100644 --- a/content/en/data_observability/quality_monitoring/data_warehouses/redshift.md +++ b/content/en/data_observability/quality_monitoring/data_warehouses/redshift.md @@ -21,6 +21,7 @@ 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" >}}.