👀 Views: 867 💬 Answers: 1 📅 Created: 2025-06-15

oci api-gateway serverless bash

I'm working on a personal project and I'm currently working on an OCI API Gateway setup that involves a custom authorizer for my functions. I'm getting a 500 Internal Server behavior when attempting to invoke the function through the API Gateway. I've confirmed that the authorizer is correctly set up and is of type `CORS`, but the behavior continues. Here’s the basic setup of my API Gateway configuration: ```json { "type": "rest", "displayName": "MyAPIGateway", "endpoint": "https://myapi.example.com", "authorizer": { "type": "custom", "functionId": "ocid1.fnfunc_oc1.region.abc123" } } ``` Upon testing the authorizer function directly, it returns a successful response with a 200 status code, indicating that it can validate tokens correctly. However, when I make a request like this: ```bash curl -X GET https://myapi.example.com/resource -H "Authorization: Bearer mytoken" ``` I receive a 500 Internal Server behavior response. I checked the Logs in the OCI console, and I see this behavior message: ``` Function failed with behavior: Unable to invoke the target function because of an internal server behavior. ``` I've tried various things to troubleshoot, including: - Ensuring that the function has the right permissions set (IAM policies) to be invoked by the API Gateway. - Checking the network security settings to ensure there are no restrictions on the function's access. - Verifying that the integration type in the API Gateway settings is pointing to the correct function and region. I'm using the OCI CLI version 3.0.0 and have followed the best practices outlined in the OCI documentation for setting up API Gateways. Has anyone else encountered a similar scenario or have insights into why this might be happening? Am I missing something obvious? What are your experiences with this?