AWS application-discovery documentation change
Summary
Removed redundant programmatic access note and added setup step
Security assessment
Clarifies programmatic access setup but does not address a specific security vulnerability.
Diff
diff --git a/application-discovery/latest/userguide/setting-up.md b/application-discovery/latest/userguide/setting-up.md index a7be470c3..eca1f4c59 100644 --- a//application-discovery/latest/userguide/setting-up.md +++ b//application-discovery/latest/userguide/setting-up.md @@ -79,3 +79 @@ While following the instructions in the _IAM User Guide_ : - * When on the step about selecting the type of access, select **Programmatic access**. Note, while not recommended, only select **AWS Management Console access** if you plan to use the same IAM user credentials for accessing the AWS console. - - * When on the step about the **Set permission** page, choose the option to **Attach existing policies to user directly**. Then select a managed IAM policy for Application Discovery Service from the list of policies. For information about Application Discovery Service managed policies, see [AWS managed policies for AWS Application Discovery Service](./security-iam-awsmanpol.html). + * When on the step about the **Set permissions** page, choose the option to **Attach existing policies to user directly**. Then select a managed IAM policy for Application Discovery Service from the list of policies. For information about Application Discovery Service managed policies, see [AWS managed policies for AWS Application Discovery Service](./security-iam-awsmanpol.html). @@ -84,0 +83,2 @@ While following the instructions in the _IAM User Guide_ : + 3. After you create the user provide them with programmatic access as described in [Support programmatic user access](https://docs.aws.amazon.com/IAM/latest/UserGuide/introduction_identity-management.html?icmpid=docs_iam_console#gs-get-keys). +