Reports of 404 issues with 3.1.2

[coolpistachio]

What happened:
We've received multiple reports from users of Amazon Managed Grafana that they're receiving 404 errors while attempting to connect to their Athena datasource using the Athena plugin version 3.1.2.

Customers are seeing the following error when they attempt to configure and connect to the datasource when clicking "Save and Test" in the Athena plugin config UI.

error retrieving credentials: failed to refresh cached credentials, no EC2 IMDS role found, operation error ec2imds: GetMetadata, http response error StatusCode: 404, request to EC2 IMDS failed: Failed to create client

We were able to confirm that rolling back to 3.1.1 fixes the issue. Customers are using IAM role auth.

What you expected to happen:
3.1.2 should not throw an error when connecting to the Athena datasource using IAM role auth.

How to reproduce it (as minimally and precisely as possible):

1. Install Athena plugin 3.1.2 on a workspace with IAM auth
2. Navigate to the Athena plugin config UI, configure the plugin
3. Save and Test

Screenshots

Anything else we need to know?:

Reported through Amazon Grafana customers.

Environment:

• Grafana version: 10.4.1
• Plugin version: 3.1.2
• OS Grafana is installed on: LINUX
• User OS & Browser:
• Others:

[njvrzm]

Hi, and thanks for the report. I've reproduced the issue. I notice that if you select "AWS SDK Default" for the authentication provider rather than "Workspace IAM Role" it appears to work correctly. Could you try this and let me know if it works for your customers? I think we may have incorrectly translated the authentication code around workspace authentication from aws-sdk-go to aws-sdk-go-v2. Tested further and discussed with AWS elsewhere. Will proceed with fixing this with grafana/grafana-aws-sdk#245

[njvrzm]

Version 3.1.3 should fix this - please let us know if you see any more problems. Thanks!