AWS Security ChangesHomeSearch

AWS amazonq documentation change

Service: amazonq · 2025-05-22 · Documentation low

File: amazonq/latest/qbusiness-ug/quip-credentials.md

Summary

Updated screenshot descriptions to be more specific about API token generation steps in Quip integration documentation.

Security assessment

Visual documentation improvement showing where to obtain API tokens, but does not introduce new security controls or address vulnerabilities. Focuses on authentication setup clarity.

Diff

diff --git a/amazonq/latest/qbusiness-ug/quip-credentials.md b/amazonq/latest/qbusiness-ug/quip-credentials.md
index 0b0f8a693..074f7dc7d 100644
--- a//amazonq/latest/qbusiness-ug/quip-credentials.md
+++ b//amazonq/latest/qbusiness-ug/quip-credentials.md
@@ -21 +21 @@ To configure Quip for Amazon Q, you must be an admin user in the Quip account.
-![Quip document interface showing welcome message, editing tools, and a getting started checklist.](/images/amazonq/latest/qbusiness-ug/images/quip-1.png)
+![Screenshot of the Quip interface showing the account settings menu where users can access developer tools to generate an API token.](/images/amazonq/latest/qbusiness-ug/images/quip-1.png)
@@ -27 +27 @@ To configure Quip for Amazon Q, you must be an admin user in the Quip account.
-![Quip logo and API Access Token interface with a redacted token field.](/images/amazonq/latest/qbusiness-ug/images/quip-2.png)
+![Screenshot of the Quip developer token page showing the generated personal access token that needs to be copied for API authentication.](/images/amazonq/latest/qbusiness-ug/images/quip-2.png)