Error `AWS object not present or incorrect in the constructor` when using IAM role

When IAM role is used for EC2/Lambda and s3 options is not passed to the config, athena-express is not able to create new buckets on its behalf, failing with error AWS object not present or incorrect in the constructor.

It looks here: https://github.com/ghdna/athena-express/blob/master/lib/athenaExpress.js#L232 that it expects either s3 option to be set or credentials keys to be passed.

I had IAM role set up with full access to S3 and Athena, though I had to specify S3 location manually to override behavior.

[KrickyKiki]

I had this error when trying to pass AWS ( caps ) instead of aws. To replicate the issue:

const AWS = require("aws-sdk");
const athenaExpressConfig = {
	AWS
};
const athenaExpress = new AthenaExpress(athenaExpressConfig);

However below worked fine:

const AWS = require("aws-sdk");
const athenaExpressConfig = {
	aws: AWS
};
const athenaExpress = new AthenaExpress(athenaExpressConfig);

[carlosescura]

After a further investigation, I found the issue and why it’s related only with roles:

This line is the cause.

For all of you having this issue, can you specify a custom s3 output directory for your queries? If so, it won’t fail as the exception is thrown because of the lack of both, the s3 value in the constructor, and the lack of a valid AWS access key (because you are using a role/instanceprofile).

const aws = require("aws-sdk");

const athenaExpressConfig = {
	aws,
	s3: "s3://whatever-your-bucket-is"
};
const athenaExpress = new AthenaExpress(athenaExpressConfig);