Sidecar Networking

A deployed sidecar needs network access in 3 directions: from the data consumers connecting to it, to the database it forwards connections to, and to ALTR’s SaaS control plane.

Network Requirements

• Inbound — Data consumers connect to the sidecar on its registered listener port(s). Identify where those data consumers are connecting from — for example, an internal network, a VPN, or a specific IP range — and open the corresponding listener port(s) and firewall rules on the sidecar to allow connections from that location.
• Outbound (to database) — The sidecar connects to the database on its native port. Configuring the database’s firewall to allow connections from the sidecar’s IP address or network range is the customer’s responsibility.
• Outbound (to ALTR) — The sidecar communicates with ALTR’s SaaS control plane over HTTPS (port 443) for policy retrieval, telemetry, and audit log delivery. Configuring the network to permit this outbound connection is the customer’s responsibility.