Skip to content
VeraDocs
Back to main site

Amazon Athena

Create, inspect and delete Athena workgroup metadata.

Plan: Pro69 of 70 operations implemented, 1 failed in testing3Known differences

Running a query returns HTTP 501 NotIncluded in Vera 1.2.0-rc.3: the query engine isn't included, and a Pro license doesn't add it.

Example checked on Vera 1.2.2, 8 November 2026. Each coverage note names its own evidence and date.

Connect

Section titled “Connect”

Activate your license key and start the emulator with the Vera launcher, as in Activate Pro, then run this in a terminal of its own, from an empty scratch directory. It gives the official AWS CLI dummy credentials and a config file of its own, so no AWS account is needed and your own AWS profile isn't touched.

Terminal window
export VERA_ENDPOINT="http://localhost:5003"
export AWS_ACCESS_KEY_ID=test AWS_SECRET_ACCESS_KEY=test
export AWS_REGION=us-east-1 AWS_DEFAULT_REGION=us-east-1
export AWS_SHARED_CREDENTIALS_FILE=/dev/null
export AWS_EC2_METADATA_DISABLED=true
export AWS_PAGER="" AWS_CLI_AUTO_PROMPT=off
unset AWS_PROFILE AWS_DEFAULT_PROFILE
unset AWS_SESSION_TOKEN AWS_SECURITY_TOKEN
unset AWS_WEB_IDENTITY_TOKEN_FILE AWS_ROLE_ARN AWS_ROLE_SESSION_NAME
unset AWS_CONTAINER_CREDENTIALS_FULL_URI
unset AWS_CONTAINER_CREDENTIALS_RELATIVE_URI
cat > vera-aws-config <<'EOF'
[default]
region = us-east-1
output = json
cli_binary_format = base64
s3 =
    addressing_style = path
EOF
export AWS_CONFIG_FILE="$PWD/vera-aws-config"

When you've finished every example in this terminal, close it and delete vera-aws-config, not before.

The example uses the AWS CLI’s athena commands. The emulator serves the 2017-05-18 API over the AWS JSON protocol, and the example was checked with the official AWS CLI 2.31.35.

Example

Section titled “Example”

Create a workgroup and read back its name and state. This example manages workgroup metadata only, so it needs no S3 result bucket.

Terminal window
aws --endpoint-url "$VERA_ENDPOINT" athena create-work-group --name vera-docs-athena
aws --endpoint-url "$VERA_ENDPOINT" athena get-work-group \
  --work-group vera-docs-athena --query 'WorkGroup.{Name:Name,State:State}'

The --query picks the workgroup’s name and state:

Output
{
    "Name": "vera-docs-athena",
    "State": "ENABLED"
}

To clean up, delete the workgroup:

Terminal window
aws --endpoint-url "$VERA_ENDPOINT" athena delete-work-group \
  --work-group vera-docs-athena --recursive-delete-option

Running queries isn’t available in Vera 1.2.0-rc.3. With a workgroup and a result bucket in place, start-query-execution returns HTTP 501 NotIncluded, with the message “Running Athena queries needs an engine that is not included in this Vera release”. A Pro license doesn’t add the engine.

Supported features

Section titled “Supported features”
  • Workgroups, created, read and deleted with --recursive-delete-option, as in the example.
  • Also served, not yet tested: named queries, prepared statements, data catalogs, databases and table metadata, notebooks, sessions and calculations, capacity reservations and tags.

Limitations

Section titled “Limitations”

The main limits are below. A few more apply to every service, and the API coverage notes cover smaller differences.

  • Queries don’t run in Vera 1.2.0-rc.3. StartQueryExecution returns NotIncluded, because this release doesn’t include Athena’s query engine, so there are no new query executions or results to read. In Vera 1.2.0 preview, SELECT 1 and this is not valid SQL were both marked SUCCEEDED without running, and neither returned result rows. Don’t use the emulator to test SQL correctness, result processing or query failures.
  • Calculations may not run either. Earlier source inspection, not a run of a release build, found that StartCalculationExecution reports a completed calculation with an empty result without running its code. Notebooks weren’t run.
  • Permissions and limits weren’t tested. Workgroup permissions, Lake Formation and S3 permissions, result reuse, data catalogs, federated connectors, concurrency and workgroup limits weren’t verified.

API coverage

Section titled “API coverage”

Every operation in AWS's published 2017-05-18 API (SDK model, botocore 1.43.105), and whether the emulator implements it. Availability combines the earlier implementation inventory with the dated observations below; checking a page's example does not verify every operation. Each note names its evidence first; an observation given without a build or date comes from earlier testing, on 3 November 2026. What the statuses mean

OperationStatusNotes
BatchGetNamedQueryImplemented
BatchGetPreparedStatementImplemented
BatchGetQueryExecutionImplemented
CancelCapacityReservationImplemented
CreateCapacityReservationImplemented
CreateDataCatalogImplemented
CreateNamedQueryImplemented
CreateNotebookImplemented
CreatePreparedStatementImplemented
CreatePresignedNotebookUrlImplemented
CreateWorkGroupImplemented
DeleteCapacityReservationImplemented
DeleteDataCatalogImplemented
DeleteNamedQueryImplemented
DeleteNotebookImplemented
DeletePreparedStatementImplemented
DeleteWorkGroupImplemented
ExportNotebookImplemented
GetCalculationExecutionImplemented
GetCalculationExecutionCodeImplemented
GetCalculationExecutionStatusImplemented
GetCapacityAssignmentConfigurationImplemented
GetCapacityReservationImplemented
GetDataCatalogImplemented
GetDatabaseImplemented
GetNamedQueryImplemented
GetNotebookMetadataImplemented
GetPreparedStatementImplemented
GetQueryExecutionKnown differenceLocal observation: Reported SUCCEEDED for both SELECT 1 and text that isn't SQL, with the same submission and completion time. In Vera 1.2.0-rc.3, StartQueryExecution returns NotIncluded, so this can't be repeated with a new query; this operation itself wasn't retested.
GetQueryResultsKnown differenceLocal observation: Vera 1.2.0 preview, 5 November 2026 — no result rows for SELECT 1 or for text that isn't SQL. The official AWS CLI rendered ResultSetMetadata as null; a boto3 response omitted ResultSet. In Vera 1.2.0-rc.3, StartQueryExecution returns NotIncluded, so this can't be repeated with a new query; this operation itself wasn't retested.
GetQueryRuntimeStatisticsImplemented
GetResourceDashboardImplemented
GetSessionImplemented
GetSessionEndpointImplemented
GetSessionStatusImplemented
GetTableMetadataImplemented
GetWorkGroupImplemented
ImportNotebookImplemented
ListApplicationDPUSizesImplemented
ListCalculationExecutionsImplemented
ListCapacityReservationsImplemented
ListDataCatalogsImplemented
ListDatabasesImplemented
ListEngineVersionsImplemented
ListExecutorsImplemented
ListNamedQueriesImplemented
ListNotebookMetadataImplemented
ListNotebookSessionsImplemented
ListPreparedStatementsImplemented
ListQueryExecutionsImplemented
ListSessionsImplemented
ListTableMetadataImplemented
ListTagsForResourceImplemented
ListWorkGroupsImplemented
PutCapacityAssignmentConfigurationImplemented
StartCalculationExecutionKnown differenceSource inspection: Stores the submitted code with immediate COMPLETED status, 100% progress, zero DPU execution time and an empty calculation result without evaluating the code.
StartQueryExecutionFailed in testingLocal observation: Vera 1.2.0-rc.3, 6 November 2026 — returns HTTP 501 NotIncluded: running Athena queries needs an engine that isn't included in this Vera release. This was after a result bucket and workgroup were created. A Pro license doesn't add the engine. The earlier observations that follow don't describe Vera 1.2.0-rc.3. Local observation: earlier testing, 3 November 2026 — accepted text that isn't SQL as well as SELECT 1, and neither query ran. Local observation: Vera 1.2.0 preview, 5 November 2026 — SELECT 1 and this is not valid SQL were both marked SUCCEEDED, with no result rows.
StartSessionImplemented
StopCalculationExecutionImplemented
StopQueryExecutionImplemented
TagResourceImplemented
TerminateSessionImplemented
UntagResourceImplemented
UpdateCapacityReservationImplemented
UpdateDataCatalogImplemented
UpdateNamedQueryImplemented
UpdateNotebookImplemented
UpdateNotebookMetadataImplemented
UpdatePreparedStatementImplemented
UpdateWorkGroupImplemented