To set up the AWS integration manually, create an IAM policy and IAM role in your AWS account, and configure the role with an AWS External ID generated in your Datadog account. This allows Datadog’s AWS account to query AWS APIs on your behalf, and pull data into your Datadog account. The sections below detail the steps for creating each of these components, and then completing the setup in your Datadog account.

Setup

Generate an external ID

1. In the AWS integration configuration page, click Add AWS Account(s), and then select Manually.

2. Choose which AWS partition your AWS account is scoped to. The partition is either aws for commercial regions, aws-cn for China*, or aws-us-gov for GovCloud. See Partitions in the AWS documentation for more information.

   If your AWS account is in the aws-us-gov (GovCloud) partition, verify with your compliance team before connecting it to your Datadog site. Confirm that forwarding data from that account meets your organization's authorization boundary and data handling requirements. Applicable frameworks may include FedRAMP, ITAR, IL4, or IL5.

4. Copy the AWS External ID. For more information about the external ID, read the IAM User Guide. Note: The External ID remains available and is not regenerated for 48 hours, unless explicitly changed by a user or another AWS account is added to Datadog during this period. You can return to the Add AWS Account(s) page within that time period without the External ID changing.

Create a Datadog integration IAM role

Datadog assumes this role to collect data on your behalf.

1. Go to the AWS IAM Console and click Create role.
2. Select AWS account for the trusted entity type, and Another AWS account.

Note: Ensure that the DATADOG SITE selector on the right of this documentation page is set to your Datadog site before copying the account ID above.

4. Select Require external ID and enter the external ID copied in the previous section. Leave Require MFA disabled. For more details, see the Access to AWS accounts owned by third parties page in the AWS documentation.
5. Click Next.
6. To enable resource collection, attach the AWS SecurityAudit Policy to the role.
7. Click Next.
8. Give the role a name such as DatadogIntegrationRole. Optionally, provide a description and add tags to the role.
9. Click Create Role.

Create an inline IAM policy for the Datadog integration role

This policy defines the permissions necessary for the Datadog integration role to collect data for every AWS integration offered by Datadog. These permissions may change as new AWS services are added to this integration.

1. Select the Datadog integration role on the IAM roles page.
2. Click Add permissions, and select Create inline policy.
3. Select the JSON tab.
4. Paste the permission policies in the textbox.
   Note: Optionally, you can add Condition elements to the IAM policy. For example, conditions can be used to restrict monitoring to certain regions.
5. Click Next.
6. Give the policy a name such as DatadogIntegrationPolicy.
7. Click Create policy.

Complete the setup in Datadog

1. Return to the manual setup section of the AWS integration configuration page.
2. Click the I confirm that the Datadog IAM Role has been added to the AWS Account checkbox.
3. In the Account ID section, enter your account ID without dashes; for example, 123456789012. You can find the account ID in the ARN of the Datadog integration role, which follows the format arn:aws:iam::<ACCOUNT_ID>:role/<ROLE_NAME>.
4. In the AWS Role Name section, enter the name of the Datadog integration role previously created. Note: The role name is case sensitive and must exactly match the role name in AWS.
5. Click Save.
6. Wait up to 10 minutes for data to start being collected, and then view the out-of-the-box AWS Overview Dashboard to see metrics sent by your AWS services and infrastructure.

Troubleshoot IAM role issues

If the integration does not appear to be working after setup, verify the following:

Common trust policy mistakes:

• The Account ID in the trust policy must match the Datadog account ID for your Datadog site. Verify that the DATADOG SITE selector on this page is set correctly.
• The External ID in the trust policy must match the value shown in the AWS integration configuration page. External IDs are regenerated after 48 hours if not used.
• The role ARN entered in Datadog must exactly match the role ARN in AWS, including capitalization.

Validate the integration in Datadog:

After configuring the role, return to the AWS integration page and save the configuration. Datadog validates the role by attempting to assume it from Datadog’s own AWS account. If the role cannot be assumed, an error message appears in the UI. See Error: Datadog is not authorized to perform sts:AssumeRole for detailed troubleshooting steps.

Service Control Policies (SCPs):

If your AWS account is part of an AWS Organization, Service Control Policies can block the integration even when the IAM role and trust policy are correct. See Missing metrics in the troubleshooting guide for details.

* All use of Datadog Services in (or in connection with environments within) mainland China is subject to the disclaimer published in the Restricted Service Locations section on our website.

Setup

AWS

1. In your AWS console, create an IAM user to be used by the Datadog integration with the necessary permissions.
2. Generate an access key and secret key for the Datadog integration IAM user.

Datadog

3. In the AWS integration tile, click Add AWS Account, and then select Manually.

4. Select the Access Keys tab.

5. Choose which AWS partition your AWS account is scoped to. The partition is either aws for commercial regions, aws-cn for China*, or aws-us-gov for GovCloud. See [Partitions][9] in the AWS documentation for more information.

   Access keys authentication is supported only for AWS accounts in the aws-us-gov (GovCloud) and aws-cn (China) partitions. For AWS accounts in the aws (commercial) partition, use Role Delegation instead.
   If your AWS account is in the aws-us-gov (GovCloud) partition, verify with your compliance team before connecting it to your Datadog site. Confirm that forwarding data from that account meets your organization's authorization boundary and data handling requirements. Applicable frameworks may include FedRAMP, ITAR, IL4, or IL5.

6. Click the I confirm that the IAM User for the Datadog Integration has been added to the AWS Account checkbox.

7. Enter your Account ID, AWS Access Key and AWS Secret Key.

8. Click Save.

9. Wait up to 10 minutes for data to start being collected, and then view the out-of-the-box AWS Overview Dashboard to see metrics sent by your AWS services and infrastructure.

* All use of Datadog Services in (or in connection with environments within) mainland China is subject to the disclaimer published in the Restricted Service Locations section on our website.