You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 21, 2023. It is now read-only.
Connections between inputs like Beats and the shipper are intended to be encrypted using mTLS. This is currently disabled because of some challenges in configuring the server based on the way the configuration is provided by the agent, see #224.
Regardless of the way TLS is configured, it needs to be possible to enable TLS for connections between the inputs and the shipper. The scope of this issue is to reenable TLS between the inputs and shipper, and measure the performance impact of enabling TLS so we can decide if it needs to be optional.
Acceptance Criteria:
A test exists proving that a shipper client can communicate with the shipper server using a TLS encrypted connection.
A performance comparison between the shipper with TLS and the shipper without TLS has been documented.
Connections between inputs like Beats and the shipper are intended to be encrypted using mTLS. This is currently disabled because of some challenges in configuring the server based on the way the configuration is provided by the agent, see #224.
elastic-agent-shipper/controller/controller_client.go
Lines 107 to 123 in fff35d3
Regardless of the way TLS is configured, it needs to be possible to enable TLS for connections between the inputs and the shipper. The scope of this issue is to reenable TLS between the inputs and shipper, and measure the performance impact of enabling TLS so we can decide if it needs to be optional.
Acceptance Criteria: