Forum Discussion
Gateway Cluster
We have two gateways. Each Gateway connecting to different environment (sandbox vs. prod). We have an odbc driver defined -- awsathena for both sandbox and prod. The only difference between these two are the credentials (Access and Secret key). When we open a dataflow, type in dsn=awsathena, it always defaults to sandbox gateway (the first gateway in the screenshot). If we want to use the dsn=awsathena from prodexp gateway we have to select the prodexp gateway. Except, we keep receiving "Invalkid Credentials" message when we try to use this connection.
I am wondering if the issue is because we have awsathena data source in two gateways and since the first one defaults as soon as I type "dsn=awsathena", it's somehow caching the credentials? Or you cannot have the same datasource name across multiple gateways?
I am certain it's not the credentials because I created another data source using the exact same access and secret key as the awsathena in prodexp gateway called aws-athena-prod-exploratory and this connection works. The only difference is the data source name...
Any feedback? Or has another encountered a similar situation?
1 Reply
- v-kkf-msftCommunity Support
Hi catcollector ,
You can try clearing your browser cache and see if it works. Have you tried using this gateway for a dataset? Can the dataset be refreshed successfully?
Best Regards,
Winniz