-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ec2-instance-connect open-tunnel failed when NO_PROXY not set. #8023
Comments
Hi @sayurin thanks for reaching out. I'm having trouble reproducing this issue, could you share your debug logs (with any sensitive info redacted) by adding |
@tim-finnigan I updated description, repro steps. Please try with |
Thanks for following up, I can reproduce the issue now. We will reach out to the team working this customization for next steps. |
|
Describe the bug
ec2-instance-connect open-tunnel failed when NO_PROXY not set.
Expected Behavior
open-tunnel successfully connected.
Current Behavior
following error message.
Reproduction Steps
HTTP_PROXY
to use proxy.In bash,
export HTTP_PROXY=http://proxy.example.com:8080
.In PowerShell
$env:HTTP_PROXY="http://proxy.example.com:8080"
.NO_PROXY
.In bash,
unset NO_PROXY
.In PowerShell,
$env:NO_PROXY=""
.aws ec2-instance-connect ssh --connection-type eice --instance-id i-xxxx --debug
.This will fail with the error written at Current Behavior.
Workarround,
NO_PROXY
to dummy value.In bash,
export NO_PROXY=1
.In PowerShell,
$env:NO_PROXY="1"
.aws ec2-instance-connect ssh --connection-type eice --instance-id i-xxxx --debug
.This will success as expected behavior.
Possible Solution
aws-cli/awscli/customizations/ec2instanceconnect/websocket.py
Lines 157 to 158 in 03e3028
If environment variable
NO_PROXY
is not set,no_proxy
becomeNoneType
.Additional Information/Context
For workaround, set environment variable
NO_PROXY
with dummy value.CLI version used
4.12.7
Environment details (OS name and version, etc.)
Windows and CloudShell.
The text was updated successfully, but these errors were encountered: