[Enhancement]: URL DNS mapping from helm chart level

[louislusesese]

What features would you like to see added?

With the use of librechat, the LLM models of major platforms can be supported, but it is found that the librechat helm chart does not support some manual mapping of DNS.

For example, if the user wants to intervene in the AWS bedrock program, it will access the following nodes through the public network. Can the helm chart support manual modification of DNS so that the following URL can point to the internal VPC network?

bedrock.eu-central-1.amazonaws.com
bedrock-runtime.eu-central-1.amazonaws.com

More details

could be introduce a feature CoreDNS or something can be rewritten the dns or ip for the application.

Which components are impacted by your request?

Other, Endpoints

Pictures

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[george-matthew]

Hi, I am not familiar with helm charts, however, we were able to route traffic via PrivateLink endpoints by creating a private hosted zone in Route53 for the bedrock endpoints and attaching the hosted zone to the VPC where LibreChat is running. Then, you create an alias record in the zone that points traffic to your PrivateLink endpoint, and all traffic will remain private, with DNS queries for bedrock.region.amazonaws.com returning private IPs that belong to the PrivateLink endpoint.

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-vpc-interface-endpoint.html

[louislusesese]

Hi @george-matthew Thanks for the information! The helm chart are librechat kubernates solution , yes , we have PrivateLink between AWS bedrock and kubernates, but only can modify the DNS records from DNS manager level! which all the network will be impacted! so the best solution will be have CoreDNS or similar solution on librechat application level to provide more flexibility .