Skip to content

[DOCS-12364] Remove site-region restriction #32449

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 8, 2025
Merged

[DOCS-12364] Remove site-region restriction #32449

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 0 additions & 4 deletions .../integrations/guide/aws-cloudwatch-metric-streams-with-kinesis-data-firehose.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,10 +10,6 @@ further_reading:
text: "Collect Amazon CloudWatch metrics using Metric Streams"
---

{{% site-region region="gov" %}}
<div class="alert alert-danger">AWS CloudWatch Metric Streams with Amazon Data Firehose is not available for the selected site ({{< region-param key="dd_site_name" >}}).</div>
{{% /site-region %}}

Using Amazon CloudWatch Metric Streams and Amazon Data Firehose, you can get CloudWatch metrics into Datadog with only a two to three minute latency. This is significantly faster than Datadog's default API polling approach, which provides updated metrics every 10 minutes. You can learn more about the API polling approach in the [Cloud Metric Delay documentation][1].

## Overview
Expand Down
8 changes: 3 additions & 5 deletions content/en/integrations/guide/cloud-metric-delay.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,12 +39,8 @@

Further, the CloudWatch API only offers a metric-by-metric crawl to pull data. The CloudWatch APIs have a rate limit that varies based on the combination of authentication credentials, region, and service. Metrics are made available by AWS dependent on the account level. For example, if you are paying for *detailed metrics* within AWS, they are available more quickly. This level of service for detailed metrics also applies to granularity, with some metrics being available per minute and others per five minutes.

{{% site-region region="us,us3,us5,eu,ap1,ap2" %}}
On your selected [Datadog site][1] ({{< region-param key="dd_site_name" >}}), you can optionally configure Amazon CloudWatch Metric Streams and Amazon Data Firehose to get CloudWatch metrics into Datadog faster with a 2-3 minute latency. Visit the [documentation on metric streaming][2] to learn more about this approach.
On your selected [Datadog site][4] ({{< region-param key="dd_site_name" >}}), you can optionally configure Amazon CloudWatch Metric Streams and Amazon Data Firehose to get CloudWatch metrics into Datadog faster with a 2-3 minute latency. Visit the [documentation on metric streaming][5] to learn more about this approach.

Check notice on line 42 in content/en/integrations/guide/cloud-metric-delay.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.sentencelength 

Suggestion: Try to keep your sentence length to 25 words or fewer.

[1]: /getting_started/site/
[2]: /integrations/guide/aws-cloudwatch-metric-streams-with-kinesis-data-firehose/
{{% /site-region %}}

### Azure

Expand All @@ -71,3 +67,5 @@
[1]: /agent/faq/why-should-i-install-the-agent-on-my-cloud-instances/
[2]: /help/
[3]: /integrations/amazon-rds/#metrics
[4]: /getting_started/site/
[5]: /integrations/guide/aws-cloudwatch-metric-streams-with-kinesis-data-firehose/
Loading