Configuring an HTTP proxy for discovery connector nodes
Configure an HTTP proxy for a discovery connector node by using an HTTP Proxy policy.
About this task
Discovery connectors deployed to an on-premises system might require an HTTP proxy to connect to
public endpoints. You can configure the following discovery connector nodes to use an HTTP proxy for
such connections:
- Amazon DynamoDB Request node
- Amazon EC2 Request node
- Amazon EventBridge Request node
- Amazon Kinesis Request node
- Amazon RDS Request node
- Amazon S3 Request node
- Amazon SNS Request node
- Amazon SQS Request node
- Astra DB Input node
- Astra DB Request node
- AWS Lambda Request node
- Confluence Request node
- Databricks Input node
- Databricks Request node
- GitHub Input node
- GitHub Request node
- Google Chat Request node
- Google Drive Request node
- Google Gemini Request node
- Google Sheets Request node
- Microsoft Azure Blob Storage Request node
- Microsoft Azure Event Hubs Input node
- Microsoft Azure Event Hubs Request node
- Microsoft Azure Service Bus Input node
- Microsoft Azure Service Bus Request node
- Microsoft Dynamics 365 for Finance and Operations Request node
- Microsoft Dynamics 365 for Sales Input node
- Microsoft Dynamics 365 for Sales Request node
- Microsoft Entra ID Input node
- Microsoft Entra ID Request node
- Microsoft Exchange Input node
- Microsoft Exchange Request node
- Microsoft SharePoint Input node
- Microsoft SharePoint Request node
- Microsoft Teams Input node
- Microsoft Teams Request node
- Salesforce Input node
- Salesforce Request node
- SAP Ariba Request node
- ServiceNow Input node
- ServiceNow Request node
- Shopify Request node
- Slack Input node
- Slack Request node
- Snowflake Request node
- Splunk Request node
- Workday Request node
Procedure
Configure an HTTP proxy for a discovery connector node by completing the following steps:


