This is mostly informational.
curator_cli was working fine with Elastic 6.6.0
When connecting into our new version (7.3.0), actions were failing with Failed to complete action: <type 'exceptions.KeyError'>: 'indices'
I spotted a few a posts out there and followed the step to increase logging.
The logging revealed a 403 - unauthorized
It seems like the first thing curator does is collect stats on all indices.
Security is use and the account has monitor, view_index_metadata permission to "*" indices.