Athena Query timing out connecting to spill bucket

1

I just created my first lambda function using the AWS pre-written jdbc connector for PostgreSQL. It connects to my database but throws an exception when I run a query. I think it can't connect to my spill bucket but I don't know why. My DB is in us-west-2. Here is the error: GENERIC_USER_ERROR: Encountered an exception[com.amazonaws.SdkClientException] from your LambdaFunction[arn:aws:lambda:us-west-2:554283132974:function:lambdapostgresconnector] executed in context[retrieving meta-data] with message[Unable to execute HTTP request: Connect to s3.us-west-2.amazonaws.com:443 [s3.us-west-2.amazonaws.com/52.218.204.48] failed: connect timed out]

preguntada hace 2 años973 visualizaciones
2 Respuestas
2
Respuesta aceptada

If your lambda is VPC enabled, can you create a VPC endpoint for S3 in your VPC - https://docs.aws.amazon.com/AmazonS3/latest/userguide/privatelink-interface-endpoints.html and https://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.html

Also check if the IAM role associated with the lambda function has the necessary permissions to access S3 - https://aws.amazon.com/premiumsupport/knowledge-center/lambda-execution-role-s3-bucket/

Also if you are following any particular tutorial from AWS, can you please provide the URL?

profile pictureAWS
EXPERTO
respondido hace 2 años
profile pictureAWS
EXPERTO
Chris_G
revisado hace 2 años
  • I will try to create your suggestions. thank you so much!!

  • If your lambda function is failing when trying to execute an Athena query, then this document may also help you set the right permissions - https://docs.aws.amazon.com/athena/latest/ug/hive-metastore-iam-access-lambda.html

    If nothing works, please do share some more details on what you are trying to do and where exactly the failure is occuring

  • I had the same issue. I tried to create an S3 endpoint of the type interface and I couldn't make it work.

    Once I created an S3 endpoint of the type gateway it started working.

0

Root cause: VPC have no internet connection issue, causing Lambda can't access S3.

Solution: Add VPC Gateway Endpoint (Select com.amazonaws.us-west-2.s3) in Lambda associated VPC.

respondido hace un año

No has iniciado sesión. Iniciar sesión para publicar una respuesta.

Una buena respuesta responde claramente a la pregunta, proporciona comentarios constructivos y fomenta el crecimiento profesional en la persona que hace la pregunta.

Pautas para responder preguntas