https://functions.xpander.ai/aws-athena, which fronts the AWS Athena API, and carry a signature from the AWS Operator’s IAM role in your cluster, so there is no key to paste.
What the skill can do
API connector: 17 actions, as they appear in the skill panel. 17 of them create, change or delete something in AWS Athena; mark those under These actions need approval when you add the skill to an agent.- Query execution service (6): Get Execution By Id, Get Results By Id, Metadata List Databases, Start Execution, Stop Execution By Id, List Executions
- Named query management (5): Get Query By Id, Delete Query By Id, List Queries, Batch Get Queries By Ids, Create Query
- Prepared statement service (3): Work Group List Work Groups, Stmt Create Statement, Stmt List Statements
- Metadata management (2): Get Table Metadata, List Table Metadata
- Workgroup management (1): Work Group Get Work Group By Id
Connect AWS Athena
In Xpander Chat, open the agent’s settings, click Add skill, and search for AWS Athena. The connect dialog asks for a connection name and whether the connection is for the Organization (one shared account) or Personal (your own account, so the agent acts with your permissions where systems allow). On an agent other people use, a personal connection runs their requests as you unless the binding requires each person’s own sign-in; see whose credential a shared agent uses. AWS Athena is served by the AWS Operator in your cluster and signs its calls with the pods’ own AWS identity; there is no key to paste. The IAM setup is on AWS Operator. Calls go tohttps://functions.xpander.ai/aws-athena.

