AWS transform documentation change
Summary
Added Windows-specific logging paths and PowerShell examples for proxy configuration
Security assessment
Changes provide OS-specific troubleshooting details but do not address security vulnerabilities or document new security features. The proxy configuration examples are operational improvements rather than security fixes.
Diff
diff --git a/transform/latest/userguide/custom-troubleshooting.md b/transform/latest/userguide/custom-troubleshooting.md index 85430e484..dee50fc96 100644 --- a//transform/latest/userguide/custom-troubleshooting.md +++ b//transform/latest/userguide/custom-troubleshooting.md @@ -18,0 +19,3 @@ AWS Transform CLI maintains logs in the following locations: +Linux and macOS + + @@ -21,0 +25,6 @@ AWS Transform CLI maintains logs in the following locations: +Windows + + + + %USERPROFILE%\.aws\atx\custom\<conversation_id>\logs\<timestamp>-conversation.log + @@ -25,0 +35,3 @@ These logs contain the full conversation history for debugging specific transfor +Linux and macOS + + @@ -28,0 +41,6 @@ These logs contain the full conversation history for debugging specific transfor +Windows + + + + %USERPROFILE%\.aws\atx\custom\<conversation_id>\logs\subagents\<name>.log + @@ -32,0 +51,3 @@ These logs contain output from subagents that the main agent spawns during trans +Linux and macOS + + @@ -36,0 +58,7 @@ These logs contain output from subagents that the main agent spawns during trans +Windows + + + + %USERPROFILE%\.aws\atx\logs\debug*.log + %USERPROFILE%\.aws\atx\logs\error.log + @@ -156 +184,11 @@ If you are using a VPN/Proxy server that leverages the `https_proxy` and `no_pro -`export no_proxy=.s3.amazonaws.com,transform-custom.<region>.api.aws` +Linux and macOS + + + + export no_proxy=.s3.amazonaws.com,transform-custom.<region>.api.aws + +Windows (PowerShell) + + + + $env:no_proxy=".s3.amazonaws.com,transform-custom.<region>.api.aws"