My guess, based on the info you've provided so far, is that the file you're editing isn't the one that elasticsearch is reading from.
Your config has a typo which ought to prevent the node from starting up, but if the typo is fixed then the config seems fine and SSL should be enabled.
What file are you editing, and how are you starting elasticsearch?
it looks like an invalid path doesn't cause an error
I certainly does in 5.0.0, I can't imagine that the behaviour changed in 5.0.2, but I'll give it a test tomorrow if we haven't tracked it down.
If you're 100% sure that you're editing the correct file, then my best guess is that there's something else weird in your file that's causing it to ignore the xpack configuration.
YAML is a complex format with lots of weird stuff that you can do to mess things up if you try hard enough.
I suggest you try running your elasticsearch.yml file through a YAML parser/validator and check whether it produces the output you expect. There's a few online parsers that will do that job - Google can point you to them.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.