Product: StreamSets Data Collector
Version: SDC 3.21.0 and later
With the SDC 3.21.0 release, Elasticsearch stages include additional security validation. As a result, pipelines with Elasticsearch security issues that previously ran without error might fail to start after you upgrade to version 3.21.0 or later.
When this occurs, check for additional details in the error messages, then correct the security issue or stage configuration, as needed.
For example, in earlier Data Collector versions, an Elasticsearch stage configured to use the AWS Signature V4 security mode with SSL/TLS would not generate an error if the certificate was missing from the specified truststore. With version 3.21.0 or later, the pipeline fails to start with the following error:
ELASTICSEARCH_43 - Could not connect to the server(s)As another example, in earlier versions, if you specify a port in an HTTP URL that doesn’t support the HTTPS protocol when configuring an Elasticsearch stage to use SSL/TLS, the stage used HTTP without raising an error. With version 3.21.0 or later, the pipeline fails to start with an error such as:
ELASTICSEARCH_43 - Could not connect to the server(s). Unrecognized SSL message, plaintext conne
