> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/setup-and-configuration/~/revisions/PVjGdtwKqOFTNscZ4vzb/sealights-agents/https-collector.md). # HTTPS Collector The Sealights HTTPS Collector is deployed on-premise to support lightweight versions of other Sealights agents (e.g., browser agent) or for Lambda-based applications. Acting as middleware, it aggregates metadata or coverage data in transit, improving performance and reducing bandwidth usage when the default listener cannot communicate directly with Sealights backend services. The on-premise agent functions solely as a proxy, facilitating communication without capturing data independently. It enhances performance, reduces latency issues, minimizes outbound connections to Sealights servers, and serves as a local cache. All agent requests are stored in memory and do not persist on disk, enabling better security auditing for customers by routing all traffic to the Sealights backend via the collector. All communications must be encrypted via TLS v1.2/1.3 according to the latest SSL security policy to safeguard network traffic. Supported cipher suites include: * TLS\_ECDHE\_RSA\_WITH\_AES\_128\_CBC\_SHA * TLS\_ECDHE\_RSA\_WITH\_AES\_256\_CBC\_SHA * TLS\_ECDHE\_ECDSA\_WITH\_AES\_128\_GCM\_SHA256 * TLS\_ECDHE\_ECDSA\_WITH\_AES\_256\_GCM\_SHA384 * TLS\_ECDHE\_RSA\_WITH\_CHACHA20\_POLY1305\_SHA256 * TLS\_ECDHE\_ECDSA\_WITH\_CHACHA20\_POLY1305\_SHA256 The TLS configuration involves enabling TLS, and if enabled, specifying the certificate and key data or their file paths. Additionally, CA certificates and P12 files with their passwords can be configured. The server must be accessible by Fully Qualified Domain Name (FQDN), and a TLS certificate for the FQDN must be provided. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.sealights.io/knowledgebase/setup-and-configuration/~/revisions/PVjGdtwKqOFTNscZ4vzb/sealights-agents/https-collector.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.