Hello Retool, we were excited to try the new AWS SQS integration, but unfortunately it is not working as expected. See screenshot for the error "Test connection failed Access key ID cannot be blank" while using the default credential provider chain.
We believe this is a bug because we are very familiar with how to authenticate Retool to the AWS API. Our self-hosted Retool runs on an EC2 instance with an IAM Role & Policy attached to it that allows for certain permissions. For example, for a long time, we've had an AWS Lambda resource that uses this method of authentication "Connect using the default credential provider chain."
As a temporary workaround, we created an IAM User, and created a secret access key. Retool's SQS resource responded well to that, and we are able to move forward now for testing purposes.
However, company policy states that we cannot use IAM Users or Secret keys for machine-to-machine communications. We must use IAM Role&Profiles. So we are currently in violation.
Please advise on how to authenticate Retool to AWS SQS while using the default credential provider chain.
