Athena Error Version 2

0

HI, I'm facing the following issue when running an UNLOAD query. It has happened just once but as those query are critical to us, i'm doing this post. Is it some kind of instability?

HIVE_WRITER_CLOSE_ERROR: Error committing write to Hive com.amazonaws.SdkClientException: Unable to execute HTTP request: Connect to XXXX.s3.us-east-2.amazonaws.com:443 [XXXX.s3.us-east-2.amazonaws.com/3.5.129.116] failed: Connection refused (Connection refused)

This query ran against the "XXXX" database, unless qualified by the query. Please post the error message on our forum or contact customer support with Query Id: 9e55c53c-b2f9-4eea-a301-d1abdb5e876d

Query format:

UNLOAD ( QUERY* ) TO 's3://XXXXX' WITH (format = 'TEXTFILE', compression = 'gzip', field_delimiter=';' , partitioned_by = ARRAY['dt'] )

thank you!

asked a year ago257 views
1 Answer
0

Hello, thank you for your question!

The error message you encountered while running the UNLOAD query in Amazon Athena indicates a problem with writing the query results to Amazon S3. The error message points to a connection issue when attempting to write the data to the specified S3 location.

This issue can be caused by some network connectivity. The error message you received indicates a connection refusal to the S3 endpoint. You can try checking your network connectivity to ensure that your Amazon Athena instance can reach the S3 endpoint.

This issue can also be caused by some problems in your S3 endpoint or bucket configurations. Please verify that the S3 endpoint (XXXX.s3.us-east-2.amazonaws.com) is correct and accessible. Also, check the permissions and bucket policies to ensure that Athena has the necessary permissions to write data to the specified S3 bucket. Also make sure that the S3 bucket specified in the UNLOAD query is in the same AWS region as the Athena query execution. Data cannot be unloaded across regions in a single UNLOAD query.

Also, please verify that the IAM role or credentials used by the Athena query has the necessary permissions to write to the S3 bucket. The role should have the appropriate s3:PutObject permission.

You may also read this article that is similar to the issue you are having (note that it is for a different service). https://repost.aws/knowledge-center/glue-connect-time-out-error

Hope this answers your question!

AWS
answered 10 months ago
AWS
SUPPORT ENGINEER
reviewed 10 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions