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
I can't confirm that, unfortunately. That would be a function of the upstream client library capabilities.
The elasticsearch8 Python module does not in itself have any mechanism to determine acceptable and unacceptable encryption algorithms from what I can see. Everything of that nature is upstream in the transport module.
Curator itself does not use any extra modules, so it uses the default Urllib3HttpNode means of communication. If urllib3 can be FIPS compliant, then there's probably a way to make elasticsearch8 FIPS compliant, which would make es_client and therefore Curator FIPS compliant.
Is elastic curator FIPS compliant?
The text was updated successfully, but these errors were encountered: