topic Automatically (programatically) rotate AWS credentials for Athena data connection in Integration, Extension & APIs

Automatically (programatically) rotate AWS credentials for Athena data connection

arno_geurts — Mon, 10 Jun 2024 10:58:01 GMT

I would like to rotate the access key ID, secret key and session token for my Athena data connection. I have been looking at the Data Connections REST API (https://qlik.dev/apis/rest/data-connections/) and the Data Credentials REST API (https://qlik.dev/apis/rest/data-credentials/), but I cannot figure out how to do it.

When I call the List data-connections API with extended=true, I get the qCredentialsID in the response. However, when I plug that one into the Get Data Credentials API, I get a 404. I'm using Qlik Cloud and M2M OAuth authentication.

Re: Automatically (programatically) rotate AWS credentials for Athena data connection

matze123 — Fri, 05 Jul 2024 06:42:24 GMT

We are in the same situation with Qlik SaaS here.

It looks like there is an API for managing connection properties [1], but it apparently cannot update credentials. There is a hint to delete and recreate with updated credentials.

Is that the solution?

[1] https://qlik.dev/manage/data-connections/update-data-connections/#change-all-connection-properties-or-credentials

Re: Automatically (programatically) rotate AWS credentials for Athena data connection

jonathan_sq — Mon, 29 Jul 2024 14:16:24 GMT

We have indeed checked on the Qlik Dev Slack and what we have done is the deletion/creation of of data connection with a lambda every 30min. We were told that because of that workaround (you just have to reuse the same connection name), the update API is not a priority.

We also discovered an old/new endpoint to list the data connection properties for a specific connector: https://qlik.dev/apis/rest/data-sources/#get-v1-data-sources-dataSourceId-api-specs

Re: Automatically (programatically) rotate AWS credentials for Athena data connection

Dave_Channon — Fri, 23 Aug 2024 07:56:04 GMT

This thread covers the solution, but I encourage you to add this request to ideation as we still plan on supporting update calls in the future and I'd love to track demand for it.

Thanks!