AWS quick documentation change
Summary
Added troubleshooting guidance for network/VPN-related sign-in failures and explicit log file locations
Security assessment
While the changes help diagnose network security controls (TLS inspection, domain blocking), they focus on connectivity troubleshooting rather than addressing a specific security vulnerability. The log location disclosure improves diagnostics but doesn't directly relate to security flaws.
Diff
diff --git a/quick/latest/userguide/desktop-troubleshooting.md b/quick/latest/userguide/desktop-troubleshooting.md index 4832c00b3..692e92ca0 100644 --- a//quick/latest/userguide/desktop-troubleshooting.md +++ b//quick/latest/userguide/desktop-troubleshooting.md @@ -105,0 +106,14 @@ If connections to Google services (Gmail, Google Calendar, Google Drive, Google +Sign-in or responses fail on a corporate network or VPN + + +The Amazon Quick desktop application might fail to sign in or load responses only when you are connected to a corporate network, VPN, or secure web gateway, but work normally when you disconnect. When that happens, your organization's network is likely blocking or inspecting the connection. Complete the following steps with your network administrator. + + 1. Confirm that the required Amazon Quick domains are reachable from your network. For the list of domains to add to your allow list, see [Network access and required domains](./desktop-security.html#desktop-network-access). + + 2. If your organization inspects encrypted traffic (TLS or SSL inspection), your operating system's certificate store must trust the inspection certificate authority, or the Amazon Quick domains must be excluded from inspection. Your network administrator can confirm whether inspection is active and configure either option. + + + + +If the issue persists after your network administrator confirms the domains are reachable and resolves any inspection issues, export your application logs (see Exporting diagnostics) and contact AWS Support. + @@ -307,0 +322,9 @@ If you need to share diagnostic information for troubleshooting, you can export +If you cannot open the application to export diagnostics, you can find the log files directly on your machine at the following locations. + + * **macOS** – `~/Library/Application Support/QuickWork/` for the current log, and `~/Library/Logs/QuickWork/` for dated logs. + + * **Windows** – `%APPDATA%\QuickWork\` for the current log, and `%APPDATA%\QuickWork\logs\` for dated logs. + + + +