Skip to content

Commit eec9f50

Browse files
authored
[DOCS-11492] Add configuration section (#30584)
1 parent dd6e1cd commit eec9f50

File tree

1 file changed

+13
-5
lines changed
  • content/en/getting_started/integrations

1 file changed

+13
-5
lines changed

content/en/getting_started/integrations/aws.md

Lines changed: 13 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -116,20 +116,28 @@ Before getting started, ensure you have the following prerequisites:
116116
c. Optionally, send logs and other data to Datadog with the [Datadog Forwarder Lambda][1].
117117
d. Optionally, enable [Cloud Security Misconfigurations][54] to scan your cloud environment, hosts, and containers for misconfigurations and security risks.
118118

119-
5. Click **Launch CloudFormation Template**. This opens the AWS Console and loads the CloudFormation stack. All the parameters are filled in based on your selections in the prior Datadog form, so you do not need to edit those unless desired.
119+
4. Click **Launch CloudFormation Template**. This opens the AWS Console and loads the CloudFormation stack. All the parameters are filled in based on your selections in the prior Datadog form, so you do not need to edit those unless desired.
120120
**Note:** The `DatadogAppKey` parameter enables the CloudFormation stack to make API calls to Datadog to add and edit the Datadog configuration for this AWS account. The key is automatically generated and tied to your Datadog account.
121121

122-
6. Check the required boxes from AWS and click **Create stack**. This launches the creation process for the Datadog stack along with three nested stacks. This could take several minutes. Ensure that the stack is successfully created before proceeding.
122+
5. Check the required boxes from AWS and click **Create stack**. This launches the creation process for the Datadog stack along with three nested stacks. This could take several minutes. Ensure that the stack is successfully created before proceeding.
123123

124-
7. After the stack is created, go back to the AWS integration tile in Datadog and click **Ready!**
124+
6. After the stack is created, go back to the AWS integration tile in Datadog and click **Ready!**
125125

126-
8. Wait up to 10 minutes for data to start being collected, and then view the out-of-the-box [AWS overview dashboard][12] to see metrics sent by your AWS services and infrastructure:
126+
7. Wait up to 10 minutes for data to start being collected, and then view the out-of-the-box [AWS overview dashboard][12] to see metrics sent by your AWS services and infrastructure:
127127
{{< img src="getting_started/integrations/aws-dashboard.png" alt="The AWS overview dashboard in the Datadog account. On the left is the AWS logo and an AWS events graph showing 'No matching entries found'. In the center are graphs related to EBS volumes with numerical data displayed and a heatmap showing consistent data. Along the right are graphs related to ELBs showing numerical data as well as a timeseries graph showing spiky data from three sources.">}}
128128

129-
## Enable integrations for individual AWS services
129+
## Configuration
130+
131+
### Enable integrations for individual AWS services
130132

131133
See the [Integrations page][13] for a full listing of the available sub-integrations. Many of these integrations are installed by default when Datadog recognizes data coming in from your AWS account.
132134

135+
Use the **Metric Collection** tab on the [AWS integration page][8] to configure which services the Datadog integration collects metrics from.
136+
137+
### Add regions
138+
139+
Under the **General** tab on the [AWS integration page][8], you can control the AWS regions where Datadog collects metrics, CloudWatch events, and resources.
140+
133141
## Send logs
134142

135143
There are two ways of sending AWS service logs to Datadog:

0 commit comments

Comments
 (0)