Proxy Configuration

When you are deploying Polaris through our Microsoft Azure or Google Cloud marketplace offers, you will be asked to configure some parameters of the Polaris Proxy. The configuration is identical for both cloud providers.

• Enable Input Encryption - whether the Polaris Proxy should expect encrypted input requests. If enabled, the proxy will decrypt the input requests before forwarding them to the client workload. Please refer to the Polaris SDK on how you can implement encrypted input requests in your servers or applications.
• Enable Output Encryption - whether the Polaris Proxy should encrypt the output responses before sending them back to the client. Please refer to the Polaris SDK on how you can decrypt output responses in your servers or applications.
• Enable CORS policy - if you are communicating with the Polaris container directly from a web browser, you will need to enable CORS for the proxy.
• Enable Logging - whether the Polaris Proxy should log high-level metadata about all incoming and outgoing requests. The logs only contain the URLs that are being processed and the HTTP status codes. No request or response data is logged.
• Image Version - by default Polaris is configured to use the latest version of the Polaris Proxy. If you want to use a specific version, you can use a Docker image tag for image hash here.

tip

If you need further configuration options for the proxy, please get in touch.