elasticsearch connection produces 401 when password contains certain characters.

I've only just started trying to use filebeat > logstash > elasticsearch (cloud) but having spent the day yesterday having problems I think I've found a potential bug. Apologies if the below is not in an acceptable format. Please note, I used a 14 day trail on Google for elasticsearch and kibana so I have no idea if this applies to on-prem/self-hosted variants.

• Version: 7.4
• Operating System: Windows
• Config File (if you have sensitive info, please remove it):
• Sample Data:
• Steps to Reproduce:

Create a trail account with Google and when prompted/changing the password for the default elastic user, use a password containing the @ symbol.

Install Logstash and configure with cloud.id and cloud.auth as per trial account.

Run logstash and view log file. Logstash is unable to connect to elasticsearch due to a 401 error.

Back in elasticsearch, change the password for the elastic user so that it contains no @ symbols.

Amend the logstash configuration to use updated password and run. Elasticsearch connection should now work.