I’ve set up an IAM user in AWS that has all the requisite permissions and a bucket w/ the specific policy on the LookerBot documentation page (https://github.com/looker/lookerbot) – in fact, I’ve gone a bit overboard for testing purposes and given the IAM user full S3 access as well as both “s3:PutObject”, “s3:PutObjectAcl”.
However, using a custom command with LookerBot returns the vague error, “S3 Error: Access Denied.” This is strange because I’ve verified that the IAM user I created has access to the specific S3 bucket I created to upload files via the AWS CLI, and that the keys used by the AWS CLI are the same that I’ve configured in the .env file of my lookerbot deployment, and that there are no other conflicting environment variables floating around. (And the AWS region is correct, and on and on.)
Has anyone else encountered a similar issue? Any luck either overcoming the issue or at least wringing a more specific error message out of LookerBot?