Skip to content

How to use an HTTP proxy

HTTP proxies play an important role in enterprise IT architectures by enforcing security policies, filtering and inspecting web traffic, improving performance through caching, and providing centralized logging and access control.

Versio.io supports HTTP proxies by setting environment variables.

During Versio.io projects, we have learned some important points for a successful implementation:

  • Only use HTTP proxies if the technical expertise is also available.
  • The environment variables for HTTP proxy configuration are to be defined in lowercase letters.
  • OneGate and OneImporter communicate with the Versio.io platform exclusively via HTTPS protocol.
  • Various modules are active in OneGate and OneImporter, which inventory data from third-party systems via the HTTP(S)-based API (e.g. hyperscalers). Please remember that this communication then also runs via the HTTP proxy! This can be prevented by specifying it in the no_proxy environment variable. This applies to the following Versio.io importers:
    • Cloud & hosting importers (AWS, GCP, Azure, etc.)
    • Monitoring solutions (Dynatrace, Instana, etc.)
    • Hypervisors (VMware vSphere, Proxmox, etc.)
    • Kubernetes & container platforms
    • Palo Alto network devices
    • Microsoft 365