AWS IAM
Using Amazon Web Services Identity and Access Management (AWS IAM) reduces the number of authentication mechanisms and number of secrets to manage. The secret key that you use for authentication is not sent over the wire to Atlas and is not persisted by the driver. Hackolade Studio supports this mechanism starting with v8.1.5
To be able to leverage this capability in Hackolade Studio, you must first set things up according to the MongoDB documentation on Authentication with AWS IAM.
In the connections settings dialog for MongoDB, in the Auth tab, choose the AWS authentication:
Then fill in your Access Key ID and Secret Access Key, or your Session Token.
If you wish to handle AWS authentication through the credentials file, you may leave blank the Access Key ID and Secret Access Key fields, knowing that Hackolade Studio supplies credentials following the recommendations described here.