Envoy must set a limit on established connections.

Envoy client connections must be limited to preserve system resources and continue servicing connections without interruption. Without a limit set, the system would be vulnerable to a trivial denial-of-service attack where connections are created en masse and vCenter resources are entirely consumed.

Envoy comes hard coded with a tested and supported value for "maxHttpsConnections" that must be verified and maintained.

At the command prompt, run the following command:

# xmllint --xpath '/config/envoy/L4Filter/maxHttpsConnections/text()' /etc/vmware-rhttpproxy/config.xml 

Expected result:

2048

or

XPath set is empty

If the output does not match the expected result, this is a finding.

Navigate to and open:

/etc/vmware-rhttpproxy/config.xml

Locate the <config>/<envoy>/<L4Filter> block and configure <maxHttpsConnections> as follows:

<maxHttpsConnections>2048</maxHttpsConnections>

Restart the service for changes to take effect.

# vmon-cli --restart rhttpproxy