querying-data-lake

Run Athena SQL queries across federated catalogs by selecting a workgroup, resolving the target asset, and executing the statement with automatic cost and data-scanned reporting. The query execution validates credentials, classifies statements for safety, and enforces workgroup output location confirmation.

You do not need the AWS MCP server to execute Athena queries. The MCP server provides sandboxed execution and audit logging when available, but the same queries run using standard AWS CLI commands when the MCP server is unavailable.

Statement classification protects Athena SQL queries by evaluating the SQL type before execution. It enforces safe execution controls that validate credentials and confirm workgroup output locations, ensuring only authorized statements run across Glue, S3 Tables, and Redshift catalogs.

The best way to select a workgroup and resolve target assets is to provide a SQL query or named query. The system delegates target asset resolution to discovery guides, automating workgroup selection and asset resolution across default and federated catalogs without manual enumeration.

You can track query cost and data scanned when running Athena queries across multiple data sources. The execution automatically reports cost analysis and data-scanned metrics after running statements across Glue, S3 Tables, and Redshift with workgroup selection.

Athena queries require workgroup output location confirmation as a safe execution control. This validation ensures query results are written to the correct location and credentials are verified before running statements across default and federated catalogs.