Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in NYC Sept 4th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

AWS connectivity using Assume Role

Hello,

  I want to connect to AWS S3 using Assume Role option in tS3Connection component.

I am able to connect using AWS Secret and access key but not using Assume Role.

 In which scenario it is better to use Assume role?As if we check "Assume Role" option we need to still enter access and secret keys.

 

For Assume Role, i provided Role ARN,Role session name on my own.

In Advanced settings, i entered STS endpoint as "https://sts.amazonaws.com".

After running the job, it fails with "Roles may not be assumed by root accounts. "

Attaching the error details.

 

 

Labels (5)
1 Reply
Anonymous
Not applicable
Author

Hello,

From the error message, please do not use AWS Root account to call assume role, which has full access to all the AWS resource and service. Take a try to use sub account/user.

Best regards

Sabrina