# Configure an external proxy (Helm) {% hint style="info" %} This documentation only applies to **advanced Orchestrated container deployments** using **Kubernetes** and **Helm** {% endhint %} CARTO Self-hosted supports operating behind an HTTP or HTTPS proxy. The proxy acts as a gateway, enabling CARTO Self-hosted components to establish connections with essential external services like CARTO licensing system, or `auth.carto.com`. You can find detailed information about these components and services in the [network requirements](https://docs.carto.com/carto-self-hosted/key-concepts/deployment-requirements#network-egress-requirements) section.
**CARTO Self-hosted does not provide or install any proxy component**; It's built to connect to an existing proxy software deployed on your side. A comprehensive list of domains that must be whitelisted by the proxy for the proper operation of CARTO Self-hosted can be found [here](https://docs.carto.com/carto-self-hosted/key-concepts/deployment-requirements#network-egress-requirements). Such list includes domains for the core services of CARTO Self-hosted, as well as some optional domains that should be enabled to access specific features. ## **HTTP** In order to configure an external HTTP proxy on your CARTO Self-hosted installation, you'll have to: Add the following lines in your customizations.yaml file: ```yaml externalProxy: enabled: true host: port: type: http excludedDomains: ["localhost,.svc.cluster.local"] ``` The `externalProxy.excludedDomains` property contains a comma-separated list of domains to exclude from proxying. The `.svc.cluster.local` domain must be in the list to allow internal communication between components within your cluster. {% hint style="warning" %} Please, take into account that if you're configuring an external proxy in a CARTO Self-Hosted installation running in [GKE with Workload Identity](/carto-self-hosted/guides/guides/use-workload-identity-in-gcp.md) configured, you'll have to add the following excluded domains: `169.254.169.254,metadata,metadata.google.internal` These domains are required when authenticating the requests performed from an installation using Workload Identity. {% endhint %} ## **HTTPS** To configure an HTTPS proxy on CARTO Self-hosted, you'll have to change the following configuration: Add the following lines in your customizations.yaml file: ```yaml externalProxy: enabled: true host: port: type: https excludedDomains: ["localhost,.svc.cluster.local"] ## NOTE: Please, carefully read CARTO Self-hosted proxy documentation to understand the the current limitations with [custom CAs]. sslRejectUnauthorized: true # sslCA: | # -----BEGIN CERTIFICATE----- # XXXXXXXXXXXXXXXXXXXXXXXXXXX # -----END CERTIFICATE----- ``` * `externalProxy.excludedDomains` : obtains a comma-separated list of domains to exclude from proxying. The `.svc.cluster.local` domain must be in the list to allow internal communication between components. * `externalProxy.sslRejectUnauthorized` (optional): Specify if CARTO Self-hosted should check if the proxy certificate is valid or not. For instance, self-signed certificates validation must be skipped. * `externalProxy.sslCA` (optional): Path to the proxy CA certificate. If the proxy certificate is signed by a **custom CA**, such CA must be included here, but if it's signed by a **well known CA**, there is no need to add it here. Well known CAs are usually part of the [ca-certificates package](https://askubuntu.com/questions/857476/what-is-the-use-purpose-of-the-ca-certificates-package). {% hint style="warning" %} Please, take into account that if you're configuring an external proxy in a CARTO Self-Hosted installation running in [GKE with Workload Identity](/carto-self-hosted/guides/guides/use-workload-identity-in-gcp.md) configured, you'll have to add the following excluded domains: `169.254.169.254,metadata,metadata.google.internal` These domains are required when authenticating the requests performed from an installation using Workload Identity. {% endhint %} ## Support for data warehouses While certain data warehouses can be configured to work with a proxy, **there are some providers that will inherently bypass it**. This means that the connection to these data warehouses won't be created through the proxy, so CARTO Self-hosted services will try to directly perform requests to the providers. * **BigQuery**: It supports both HTTP and HTTPs proxy. * **PostgreSQL and Redshift**: They use a TCP connection instead of HTTP(S), so the proxy is bypassed. * **Databricks**: Proxy is not supported, so the HTTPS connection will be bypassed. * **Snowflake:** It supports HTTP proxy, but HTTPS is not supported and will have to be bypassed. In order to bypass it, you'll have to add `snowflakecomputing.com` to the list of excluded domains. * **Oracle:** It supports HTTP proxy, but HTTPS is not supported and will have to be bypassed. In order to bypass it, you'll have to add `oraclecloud.com` to the list of excluded domains. {% hint style="info" %} When the proxy is bypassed, and you have a restrictive network policy in place, you will need to explicitly allow this egress of non-proxied traffic. {% endhint %} ## Enhanced control over non-proxied egress traffic {% hint style="info" %} The following configuration just applies for orchestrated container deployments of CARTO Self-Hosted, so if you're using the Single VM deployment this section must be skipped. {% endhint %} When no network policy is enforced, all outgoing traffic that does not pass through a proxy will be permitted. In restrictive environments, it is indispensable to maintain strict control over connections made by CARTO Self-hosted components. To achieve this, you should configure your proxy to allow only approved external services (whitelisting), while blocking any other outgoing traffic that does not go through the proxy. To accomplish this, you can apply a custom network policy, such as the one provided in this example: ```yaml apiVersion: networking.k8s.io/v1 kind: NetworkPolicy metadata: name: carto-no-internet-access # Optional labels labels: app.kubernetes.io/instance: app.kubernetes.io/managed-by: app.kubernetes.io/name: spec: # Match all Pods except the proxy Pod. # NOTE: Make sure your proxy pod has the label app.kubernetes.io/component: proxy # NOTE: Proxy pod is not deployed with the CARTO Self-hosted chart podSelector: matchExpressions: - key: app.kubernetes.io/component operator: NotIn values: - proxy - router policyTypes: - Ingress - Egress ingress: # Allow connections within the same namespace - from: - namespaceSelector: matchLabels: kubernetes.io/metadata.name: egress: # Allow connections within the same namespace - to: - namespaceSelector: matchLabels: kubernetes.io/metadata.name: # Allow DNS resolution - to: - namespaceSelector: matchLabels: kubernetes.io/metadata.name: kube-system - podSelector: matchLabels: k8s-app: kube-dns ports: - port: 53 protocol: UDP # Allow connections to external datawarehouses - to: - ipBlock: cidr: 0.0.0.0/0 ports: # Postgres - port: 5432 protocol: TCP # Redshift - port: 5439 protocol: TCP # Valkey - port: 6379 protocol: TCP # Allow connections to other datawarehouses hosts on port 443 - to: - ipBlock: cidr: ports: - port: 443 protocol: TCP ``` ## Limitations Password authentication is not supported for the proxy connection. [Importing data](https://docs.carto.com/carto-user-manual/data-explorer/importing-data) using an HTTPS Proxy configured with a certificate signed by a Custom CA\ is not supported. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.carto.com/carto-self-hosted/guides/guides-helm/configure-an-external-proxy.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.