Configuring an HTTP Proxy for a Server Group

You can configure an HTTP proxy for all servers in a server group to access intranet and internet URLs.

Agent Support

The following agents support configuration via an HTTP proxy (using client/client group or server group settings):

  • Amazon EC2

  • Amazon DynamoDB

  • Amazon Redshift

  • Amazon Relational Database Service (RDS)

  • Azure Database for MariaDB

  • Azure Cosmos DB

  • MySQL

  • Oracle Cloud Infrastructure (OCI)

  • PostgreSQL

  • Salesforce

Procedure

Note

Based on your environment, some features, such as the Custom Report Engine, Private Metrics Reporting, Scheduled reports, and REST calls to Web Console URLs (such as MongoDB readiness), may or may not need HTTP proxy. If HTTP proxy is not needed for these features in your environment, then consider bypassing those intranet URLs going via the HTTP proxy by specifying the addresses in the Proxy bypass list field (see Step 7, below).

  1. From the navigation pane, go to Manage > Server groups.

    The Server groups page appears.

  2. Click the server group.

    The server group page appears.

  3. On the Configuration tab, in the HTTP proxy section, move the Use HTTP proxy toggle key to the right.

    The HTTP proxy dialog box appears.

  4. Enter the proxy server name and proxy port.

  5. To specify authentication options, move the Use authentication toggle key to the right, and then enter or add credentials.

  6. To use the HTTP proxy with network topologies, move the Use with network topologies toggle key to the right.

    If you select this setting, the network daemon service uses this HTTP proxy for the outgoing connections that are set up in the network topology for the server group.

  7. To enter a domain or website that does not require this HTTP proxy, enter the address in the Proxy bypass list field, and then click Add.

    Each entry can only have letters (a-z), numbers (0-9), periods (.), or hyphens (-). You can start with ""http://" or "https://" and use "" to skip the proxy for local addresses.

    For example:

    • You can enter a hostname, such as rds.ap-south-1.amazonaws.com

    • You can enter a domain such as amazonaws.com to bypass HTTP proxy for URLs containing hostnames such as amazonaws.com, amazonaws.com:80, and www.amazonaws.com. However, this will not bypass incorrectly spelled URLS such as www.amazonavs.com and amazonaws.com.org.

      Note

      The "." operator is not allowed at the beginning of the bypass list (for example, .amazonaws.com).

  8. Click Save.

Loading...