When using AWS our recommendation is to use the OEM/hourly integration which takes care of a lot of the underlying auth issues - more info here and here
Regarding the error message you're seeing it's basically telling you that we cannot connect to S3 to fetch the data. To solve that you need to do one of the following:
a. provide credentials in the vix path (notice using s3n instead of s3)
input path: s3n://[awsAccessKeyId]:[awsSecretAccessKey]@bucket_name/path/to/data
b. provide the credentials in the provider via "Additional settings":
vix.fs.s3n.awsAccessKeyId =
vix.fs.s3n.awsSecretAccessKey =
then in your vix input path use s3n://bucket_name/path/to/data
... View more