Skip to content
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.

Sign up for GitHub

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

Jump to bottom

NoProxy Configuration Not Working As Expected #441

Open
BradyShober opened this issue May 21, 2024 · 0 comments · May be fixed by #442
Open

NoProxy Configuration Not Working As Expected #441

BradyShober opened this issue May 21, 2024 · 0 comments · May be fixed by #442
Labels
bug

Comments

@BradyShober
Copy link

Issue Details

Describe the bug
In our environment we need to configure a proxy however we use VPC endpoints and do not need all AWS traffic proxied. In our case with the NoProxy list below traffic to autoscaling.us-east-2.amazonaws.com and ec2.us-east-2.amazonaws.com are being sent to the proxy.

To Reproduce

  1. Configure Jenkins proxy with NoProxy list such as
    169.254.169.254
    *.s3.us-east-2.amazonaws.com
    sts.us-east-2.amazonaws.com
    autoscaling.us-east-2.amazonaws.com
    ec2.us-east-2.amazonaws.com
    ecs.us-east-2.amazonaws.com

  2. Attempt to configure a Cloud, the plugin will not be able to pull available auto scaling groups if proxy does not allow the traffic.

Environment Details

Plugin Version?
3.0.2

Jenkins Version?
2.426.2

Spot Fleet or ASG?
ASG

Label based fleet?
Yes

Linux or Windows?
Either
@BradyShober BradyShober linked a pull request May 21, 2024 that will close this issue
Open
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix NoProxy configuration sentryinsurance/ec2-fleet-plugin
1 participant
@BradyShober