Skip to content

Commit 1146344

Browse files
committed
Copy and title edits, ready for publication
1 parent c6d157c commit 1146344

File tree

1 file changed

+24
-18
lines changed

1 file changed

+24
-18
lines changed
Lines changed: 24 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
layout: post
3-
title: "How Scribd manages Datadog’s AWS integration using Terraform"
3+
title: "Using Terraform to integrate Datadog and AWS"
44
authors:
55
- jimp
66
- qphou
@@ -11,22 +11,28 @@ tags:
1111
team: Core Infrastructure
1212
---
1313

14-
Datadog comes with a builtin AWS
14+
We love metrics but hate manual processes. When we adopted
15+
[Datadog](https://datadoghq.com)'s builtin AWS
1516
[integration](https://docs.datadoghq.com/integrations/amazon_web_services/?tab=allpermissions)
16-
to ship CloudWatch metrics to your Datadog account. Once enabled, the
17-
integration will automatically synchronize whitelisted CloudWatch metrics into
18-
your Datadog account.
17+
we couldn't wait to get AWS CloudWatch metrics into Datadog, but first we needed to automate
18+
the [numerous manual steps
19+
required](https://docs.datadoghq.com/integrations/amazon_web_services/?tab=allpermissions)
20+
to set it up. Datadog's AWS integration is quite powerful, once
21+
enabled it will automatically synchronize specified CloudWatch metrics into a
22+
Datadog account. Basically, anything available within CloudWatch, can be easily
23+
made available in Datadog, alongside all of our other metrics and dashboards.
1924

20-
While this integration is powerful and convenient to use, it’s setup process is
21-
actually quite involved. As outlined in [Datadog's documentation](https://docs.datadoghq.com/integrations/amazon_web_services/?tab=allpermissions), there are 18
22-
manual steps required, including:
25+
26+
Despite the integration's power and convenience, its setup process is actually
27+
quite involved. As outlined in [Datadog's
28+
documentation](https://docs.datadoghq.com/integrations/amazon_web_services/?tab=allpermissions),
29+
there are *18 manual steps** required, including:
2330

2431
- finding the right AWS account ID
2532
- creating the right IAM policy
2633
- copy pasting the right AWS resource ID into Datadog UI
27-
- etc.
2834

29-
If you have more than a few AWS accounts, you may prefer to use Terraform.
35+
If you have more than a few AWS accounts like we do, you may prefer to automate this! In our case, that means using [Terraform](https://terraform.io)
3036

3137
In this blog post, we would like to share how Scribd uses Terraform to automate
3238
our Datadog and AWS integration across the organization.
@@ -50,21 +56,21 @@ module "datadog" {
5056

5157
The benefit from an AWS Account maintainer point of view is that using the
5258
module is a convenient way to inherit centralized best practice. For module
53-
maintainers, any change to the datadog integration module can be released using
59+
maintainers, any change to the Datadog integration module can be released using
5460
a [standard Terraform module release process](https://www.terraform.io/docs/registry/modules/publish.html).
5561

5662

57-
# Cloudwatch log synchronization
63+
# CloudWatch log synchronization
5864

5965
Initially, the module only sets up the base integration. As adoption increased, more
6066
features were added to the module by various teams. One of these features is
61-
automation for setting up log ingestion for cloudwatch.
67+
automation for setting up log ingestion for CloudWatch.
6268

6369
Like setting up the official AWS integration app, the [instructions for log
6470
synchronization](https://docs.datadoghq.com/integrations/amazon_web_services/?tab=allpermissions#log-collection)
6571
are a bit overwhelming.
6672

67-
However, using the terraform-aws-datadog module, we can enable the feature with a single parameter:
73+
However, using the `terraform-aws-datadog` module, we can enable the feature with a single parameter:
6874

6975
```terraform
7076
module "datadog" {
@@ -76,9 +82,9 @@ module "datadog" {
7682
}
7783
```
7884

79-
That’s it, Terraform will automatically create the datadog serverless function
80-
and triggers for specified log groups to forward all cloudwatch logs into
81-
Datadog. After running terraform apply, you should be able to see logs showing
85+
That’s it! Terraform will automatically create the Datadog serverless function
86+
and triggers for specified log groups to forward all CloudWatch logs into
87+
Datadog. After running `terraform apply`, you should be able to see logs showing
8288
up in Datadog within minutes.
8389

8490

@@ -91,7 +97,7 @@ more features to the module as we migrate Scribd’s infrastructure into AWS.
9197
Metrics ingested through the official AWS integration are delayed by couple
9298
minutes, which is not ideal to use as signals for monitoring critical systems.
9399
There are opportunities to enable real time metrics synchronization by
94-
automating datadog agent setup.
100+
automating Datadog agent setup.
95101

96102
The [datadog-serverless-functions
97103
repo](https://github.com/DataDog/datadog-serverless-functions/tree/master/aws)

0 commit comments

Comments
 (0)