Customizing Maia Foundation runner networking and connectivity🔗
This document contains additional information for configuring connectivity to a Hybrid SaaS Maia Foundation runner. It covers configuration considerations for common use cases, such as using the Maia Foundation runner with a proxy server.
Maia Foundation runners don't interact with proxy servers by default, but can be configured to do so if required. This is true of both AWS and Azure hosted Maia Foundation runners.
There is no support for using proxy servers with Matillion-hosted Maia Foundation runners in a Full SaaS solution.
Note
This article is not intended as a guide for how to set up a proxy server; we assume you are already using a proxy in your infrastructure, and need to know how to use your Maia Foundation runner with it.
IP allow list🔗
If your account uses IP restrictions, you must also add your Maia Foundation runner's outbound IP address or range to the Maia IP allow list. For more information, read IP allow list.
Environment variables for outbound connections🔗
There are a number of optional environment variables that must be set to configure outbound connections for the Maia Foundation runner. These are:
| Variable | Description |
|---|---|
| PROXY_HTTP | Holds your HTTP proxy server name and port used. For example: myproxy.com:3000. |
| PROXY_HTTPS | Holds your HTTPS proxy server name and port used. For example: myproxy.com:3000. |
| PROXY_EXCLUDES | Lists addresses for the proxy to ignore. Separate multiple addresses using a pipe character. For example: example.com|example.net. |
| CUSTOM_CERT_LOCATION | Points to the storage location for custom certificates that you want the Maia Foundation runner to trust. For example, my_storage/my_certs |
For more information on setting these, read Optional Maia Foundation runner parameters.