I’m trying to connect to an S3 bucket named `dieselpj-test` using an IAM user’s access key in KNIME. However, I received the following warning:
“The credentials provided have restricted permissions. File browsing might not work as expected.”
From what I understand, KNIME seems to mechanically check the assigned policy and flags a warning regardless of the actual permissions. The IAM user has a policy that includes `s3:ListBucket`, so I believe the access should be sufficient.
The issue is shown in the attached screenshot.
Has anyone encountered this situation before? Is there a way to bypass or resolve this warning?
list bucket policy is pretty much always required. I haven’t tested that in my AWS accounts what implications it has to not assign it. Maybe none if the exact bucket name is known. Going to keep a reminder to test that out the next time.
Anyways, I’d agree that you can safely ignore the warning. Though, when using a List Files/Folder Node, it might error out if you try to browse as it starts in root. Passing the S3 bucket name in the input field, might mitigate the assumed issue.
Please ignore that warning. That comes that is the way this node works. But if you have correct permission even after this warning the file browsing will work well.
