Lambda function error messages - Amazon Relational Database Service (original) (raw)

In the following list you can find information about error messages, with possible causes and solutions.

ERROR:  invoke API failed  
DETAIL: AWS Lambda client returned 'Unable to connect to endpoint'.  
CONTEXT:  SQL function "invoke" statement 1  

A common cause for this error is improperly configured VPC security group. Make sure you have an outbound rule for TCP open on port 443 of your VPC security group so that your VPC can connect to the Lambda VPC.
If your DB instance is private, check the private DNS setup for your VPC. Make sure that you set the rds.custom_dns_resolution parameter to 1 and setup AWS PrivateLink as outlined in Step 1: Configure your RDS for PostgreSQL DB instance for outbound connections to AWS Lambda. For more information, see Interface VPC endpoints (AWS PrivateLink).

ERROR:  permission denied for schema aws_lambda  
ERROR:  permission denied for function invoke  

A user (role) must be given specific grants to invoke Lambda functions. For more information, see Step 6: Grant other users permission to invoke Lambda functions.

SELECT * FROM aws_lambda.invoke('aws_lambda_arn_1', '{"body": "Hello from Postgres!"}'::json);  
ERROR:  lambda invocation failed  
DETAIL:  "arn:aws:lambda:us-west-2:555555555555:function:my-function" returned error "Unhandled", details: "<Error details string>".  

Be sure to handle errors in your Lambda functions or in your PostgreSQL application.

Examples: Invoking Lambda functions

Lambda function and parameter reference

Did this page help you? - Yes

Thanks for letting us know we're doing a good job!

If you've got a moment, please tell us what we did right so we can do more of it.

Did this page help you? - No

Thanks for letting us know this page needs work. We're sorry we let you down.

If you've got a moment, please tell us how we can make the documentation better.