AWS application-discovery documentation change
Summary
Added instruction to generate IAM access keys before managing Discovery Agent
Security assessment
Emphasizes proper IAM credential management which is security-related best practice, but doesn't address a specific vulnerability
Diff
diff --git a/application-discovery/latest/userguide/start-agent-data-collection.md b/application-discovery/latest/userguide/start-agent-data-collection.md index 81e7f8af4..88cb126bc 100644 --- a//application-discovery/latest/userguide/start-agent-data-collection.md +++ b//application-discovery/latest/userguide/start-agent-data-collection.md @@ -7 +7 @@ -After the Discovery Agent is deployed and configured, if data collections stops you can restart it. You can start or stop data collection through the console by following the steps in [Starting and stopping data collectors in the AWS Migration Hub console](./start-stop-data_collection.html), or by making API calls through the AWS CLI. +After the Discovery Agent is deployed and configured, if data collections stops you can restart it. You can start or stop data collection through the console by following the steps in [Starting and stopping data collectors in the AWS Migration Hub console](./start-stop-data_collection.html), or by making API calls through the AWS CLI. Before starting be sure to generate [access keys](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_credentials_access-keys.html) needed to manage the Discovery Agent.