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.

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

Existing VPC and EKS but behind http proxy #50

Open
lkr2des opened this issue Feb 14, 2025 · 1 comment
Open

Existing VPC and EKS but behind http proxy #50

lkr2des opened this issue Feb 14, 2025 · 1 comment

Comments

@lkr2des
Copy link

lkr2des commented Feb 14, 2025

Hi @mirodrr2

I am trying within our org due to existing vpc restrictions.Appreciate that you've made this available now to existing vpc.
As a result we've created our existing eks cluster as well.
Our VPC's private subnets are non routable to the internet directly(either via NATGW or IGW).
We use http squid proxy for outbound connectivity.On this subnet we created managed nodegroups
with http proxy environment settings.

Based on the above scernario how do accomplish enabling litellm via http proxy for outbound

"If you'd like to run LiteLLM in subnets without outbound internet
access, set DISABLE_OUTBOUND_NETWORK_ACCESS="true". Due to lack of
internet access, this configuration will only work with AWS Bedrock or
SageMaker models. Because of this, you must remove all
non-Bedrock/non-SageMaker models from your config/config.yaml file. If
you do not do this, LiteLLM will fail to start as it will attempt to
call third party models over the internet."

Thanks

@mirodrr2
Copy link
Contributor

I can try to get to this later, but there's other priorities I need to handle first

I would recommend diving into the cdk and terraform and seeing what you may need to tweak to work with your particular network setup.

Sorry I don't have a better answer for you right now. I'll revisit this when things slow down on my end

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants