Skip to content

Commit 421911a

Browse files
committed
[AWS] Small update of the aws setup process to make it clearer
see also https://datadog.zendesk.com/agent/tickets/58395
1 parent 9ffc759 commit 421911a

File tree

2 files changed

+1
-1
lines changed

2 files changed

+1
-1
lines changed

content/integrations/aws.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -126,7 +126,7 @@ Note: GovCloud does not support role based authentication.
126126
1. Create a new role in the IAM Console. Name it anything you like, such as ```DatadogAWSIntegrationRole```.
127127
2. From the selection, choose Role for Cross-Account Access.
128128
3. Click the Select button for **Allows IAM users from a 3rd party AWS account to access this account**.
129-
4. For Account ID, enter ```464622532012```. For External ID, enter the one generated on our website. Make sure you leave **Require MFA** disabled. *For more information about the External ID, refer to [this document in the IAM User Guide](http://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-user_externalid.html)*.
129+
4. For Account ID, enter ```464622532012``` (Datadog's account ID). This means that you will grant Datadog and Datadog only read access to your AWS data. For External ID, enter the one generated on our website. Make sure you leave **Require MFA** disabled. *For more information about the External ID, refer to [this document in the IAM User Guide](http://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_create_for-user_externalid.html)*.
130130
5. Select the policy you created above.
131131
6. Review what you selected and click the **Create Role** button.
132132
* Access Key-based authentication: create a user which will have Secret and Access Key associated with it
186 KB
Loading

0 commit comments

Comments
 (0)