AWS amazonq medium security documentation change
Summary
Removed IAM permission requirements for secret rotation
Security assessment
Removal of secret rotation permissions guidance could lead to insecure secret management practices
Diff
diff --git a/amazonq/latest/qbusiness-ug/jira-prereqs.md b/amazonq/latest/qbusiness-ug/jira-prereqs.md index f5528daea..c32b313f0 100644 --- a/amazonq/latest/qbusiness-ug/jira-prereqs.md +++ b/amazonq/latest/qbusiness-ug/jira-prereqs.md @@ -11 +11 @@ Before you begin, make sure that you have completed the following prerequisites. - * Created Jira API token authentication credentials that include a Jira ID (email ID with domain) and a Jira credential (Jira API token). See the [Atlassian documentation for information about managing API tokens](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/). + * Created Jira API token authentication credentials that include a Jira ID (email ID with domain) and a Jira credential (Jira API token). See [Atlassian documentation on managing API tokens](https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/). @@ -17,2 +16,0 @@ Before you begin, make sure that you have completed the following prerequisites. - * If you want to have Amazon Q automatically rotate your secret, ensure that your IAM role includes the `secretsmanager:PutSecretValue` and `secretsmanager:UpdateSecret` permissions. -