I Have admin access to AWS and trying to connect to amazon athena through Tableau desktop by providing access key id , security access key. but i am facing below error.
An error occurred while communicating with Amazon Athena
Invalid username or password.
Error Code: E88DBC3B
[Simba]AthenaJDBC An error has been thrown from the AWS Athena client. The security token included in the request is invalid. [Execution ID not available]
Invalid username or password.
To avoid this error, I created IAM user & provided Amazon s3 , Athena Glue & Quick sight full access. Downloaded credentials for the IAM user.
I am able to establish connection between tableau desktop and amazon Athena successfully with these IAM user credentials but i have to establish connection with Domain user credentials ( access key id, security access key) only, Please help me on this?
OFICIAL DE AWSActualizada hace un año
But I don't see option to provide security key in Tableau desktop
It looks like Tableau doesn't yet provide that option - see https://community.tableau.com/s/question/0D78b0000089p0MCAQ/detail?s1oid=00D4T000000Dj8G&t=1657735074796&s1nid=0DB4T000000GnPK for example.
As suggested there, you could try connecting to Athena via ODBC.
Here domain user means , I created user through DSM tool ( Disk share management tool) and it has admin access. After connecting amazon web console with DSM user , able to access Athena and Query data without any error. but when I try to connect amazon Athena from Tableau desktop with this DSM user ( not IAM user, cannot see under IAM - Users) Access key id, Secret access key getting above error.
I have gone through AWS documents and other 3rd party documents also, I don't find any info related to DSM tool user , found only IAM user only. Is it possible to connect amazon Athena from local tableau desktop through DSM tool user?
No, the only options are Access key ID & Secret access key from an IAM User (as per https://help.tableau.com/current/pro/desktop/en-us/examples_amazonathena.htm) or as I mentioned before, connecting via ODBC instead.