The diagnostic cli does not detect the proxy setting on Windows the same way as the agent does.
The agent goes through the documented order of methods to read the settings.
But the cli only reads the system environment variables -
The result is that the diagnostics is not a true reflection of the agent's connectivity.
The diagnostic cli does not detect the proxy setting on Windows the same way as the agent does. The agent goes through the documented order of methods to read the settings. But the cli only reads the system environment variables -
The result is that the diagnostics is not a true reflection of the agent's connectivity.
I had a look at the code, and it seems like the cli calls GetProxyConfig() in https://github.com/aws/amazon-ssm-agent/blob/mainline/agent/proxyconfig/proxy.go instead of https://github.com/aws/amazon-ssm-agent/blob/mainline/agent/proxyconfig/proxy_windows.go