Writeback Reload Implementation.

[SarveshKumar]

Hello Team,

Can we use Amazon S3 as the source repository, along with AWS Lake Formation and Athena for schema and table creation, and integrate this setup with Qlik Sense to enable writeback and reload functionality?

The objective is to ensure that once users enter and save their data, a reload of the application reflects the latest updates across the dashboard, including all KPIs, charts, bar graphs, and other visualizations.

Could you please clarify whether this approach is feasible and if there are any limitations or considerations that we should be aware of? This is currently a major blocker for me, and your guidance would be greatly appreciated.
Also Please help me with the level of Access like do I need any Automation from Qlik Sense that will write the Data back to S3.

Thanks
Sarvesh

[jasonmiller11tt234 · Accepted solution]

Yes, it’s feasible for analytics, but with a key limitation: Athena is read-only, so no native writeback.

Qlik Sense can reload from S3 via Amazon Athena / AWS Lake Formation, but for saving user input you’ll need a custom writeback layer (e.g., Qlik APIs or Lambda writing to Amazon Web Services S3).

So:
✔ Reloads & dashboards → supported
⚠ Writeback → custom implementation required

[SarveshKumar]

Thank you @jasonmiller11tt234, this will help.

[SarveshKumar]

@jasonmiller11tt234 , thank you for your response. It was very helpful.

I successfully implemented this in the Qlik Trial Environment using the Tenant Admin role. The write-back table values were loaded successfully through Automation in Qlik Sense.

In our production environment, I currently have the Analytics Content Creator role, which does not include permissions to create or manage Automations. Therefore, I have requested the additional access required to implement the same solution in Production.

Need your help to review and validate whether the following access requirements are appropriate?

Qlik Sense Access

• Automation Creator with full permissions:

  • Execute Automations

  • Read Change Store

  • Use third-party connectors

  • Configure Lambda connector

AWS Services Access

Amazon S3

• AmazonS3FullAccess, or equivalent permissions:

  • s3:GetObject

  • s3:PutObject

  • s3:ListBucket

AWS Lambda

• AWSLambdaFullAccess, or permissions to:

  • Create Lambda functions

  • Update Lambda functions

  • Invoke Lambda functions

  • View CloudWatch logs

  • Attach an IAM role to Lambda

AWS IAM
Permissions to:

• Create an IAM user, or

• Create an IAM role, or

• Attach an existing policy to the existing user.

Minimum IAM Policy Requirements

• AWS Lambda permissions

• Amazon S3 permissions

• CloudWatch Logs permissions

Additionally, I Have also requested the Access Key ID and Secret Access Key for the IAM user created.

It is highly appreciated if you could provide your response to this.


Thanks, and Regards
Sarvesh