How to make Orchestrator API calls from Lambda?

Why does the Lambda function fail to establish an SSL connection for an HTTPS request to the Orchestrator?

When executing an API call from Lambda, the function may fail to establish an SSL connection for the HTTPS request.

Root Cause: This occurs because Orchestrator uses HTTPS for communication, and Lambda often cannot verify the Orchestrator certificate, causing the function to fail.

Resolution Steps:

  1. Allow Execution Without Valid SSL:
    If possible, modify the code to execute without requiring a valid SSL certificate. This approach may be suitable for internal systems where SSL verification can be safely bypassed.

  2. Load Required Certificates in Lambda Function:
    Ensure that the Lambda function loads the necessary certificates. This can be done by including the certificate bundle in the deployment package and configuring the Lambda function to use it.

  3. Enable HTTP Communication on Orchestrator:
    This is an alternative solution but should be used with caution. Only enable HTTP communication if the HTTP port is not exposed to the internet, as this could lead to security vulnerabilities.