Documentation
 

Search Results

AWS Lambda Sidecar Integration Connector

Release Notes

TIBCO Cloud Mashery Release Date Release Type Release Description
November 16, 2021 Enhancement Sidecar Connector change to use Apache http client library for calling AWS Lambda function from Mashery. Support for timeout functionality is added.
October 8, 2020 Enhancement

Sidecar Connector improved with better resiliency in error management by incorporating Lambda function custom runtime exception that comes with X-Amz-Function-Error header.

(AWS Lambda Runtime Error Handling Documentation)

Improvement to secure and encrypt confidential credential like externalID by integrating with AWS Systems Manager Parameter Store.

August 27, 2020 New Feature Supports TIBCO Cloud Mashery sidecar integration for AWS Lambda function.
Supports AssumeRole IAM policy with external ID for enhancement security of AWS Lambda resources access in compliance of AWS shared responsibility model.
Supports configurable sure-fire and fail-safe modes to invoke AWS Lambda function to influence Gateway action.
Supports RESTful POST messages only for AWS Lambda function invocation.
Supports optional configurable parameters to apply business policies to influence API behavior in the end-to-end call flow.

Description

The AWS Lambda Sidecar Integration Connector is a TIBCO Cloud Mashery integration hook for AWS Lambda function.

You can develop business logic or API policies themselves, deploy in AWS Lambda as function and integrate with TIBCO Cloud Mashery to fuel rapid innovations.

The Mashery Gateway Sidecar integration sends API request to back end API server or to the user client using the AWS Lambda function.

The API request can proceed without additional modifications to the API call or with modifications to the API call. Alternatively, if the API request cannot be completed you will be provided with the error code and message.

Features of the connector are as follows:
  • Supports integration with an external application written for business use case implementation using any development platform, platform like TIBCO Flogo, or any AWS Lambda supported languages that is deployed in AWS Lambda as function.
  • Facilitates minimally coupled yet tight integration to apply business policies/rules based on AWS Lambda function response for both user client request to Mashery Gateway and origin server response to Mashery Gateway.
  • Supports enhanced cloud resources security using AWS STS assume role with ExternalId for AWS Lambda function access and invocation.
  • Supports pre processing of user client and post processing of backend response with configurable augmented policies to influence API behavior at Mashery.
  • Supports JSON data structure for outbound call to AWS Lambda function with user client request and back end response.

Integration is AWS Lambda function implementation agnostics if the sidecar integration specifications are followed.

Sidecar Integration in Simple Terms

In simple terms Mashery Gateway Sidecar integration asks AWS Lambda function : "Can I send this API request to backend API server / User Client?". The Lambda function replies either of the following:
  • Yes, without additional modifications to API call.
  • Yes, with provided modifications to the API call.
  • No, with provided error code and message.

AWS Lambda Sidecar Integration Scope

  • TIBCO Cloud Mashery integration with AWS Lambda function only.
  • Configurable support for the following operational modes:
    • As a request/response invocation
      • Sample use case scenario
        • Output of the Lambda function is used to modify a content that is sent to the API provider or to the API consumer
        • The response time as seen by the API consumer incurs communication overhead with the AWS region as well as any processing time taken by the function.
    • As a synchronous non-blocking event invocation
      • Sample use case scenario
        • Invoke Lambda function indicating that it is not expecting to receive a response.
        • Cases such as logging, analytics, quality control, anomaly alerting.
        • The response time as seen by the API consumer incurs only the communication overhead over the stack, without waiting for the response from the Lambda function.
  • Configurable support for following below error handling policy
    • Sure-Fire
      • Should a function fail, the call processing also fails.
      • Fault of the lambda function results in 500 Internal Server Error being sent to the client.
    • Fail-Safe
      • Failure of the Lambda function does not impact serving the traffic.
      • An inevitable response time degradation is observed by the clients.
Additional Notes about Integration Scope
  • Customer can develop business logic or API policies themselves, deploy in AWS Lambda as function and integrate with TIBCO Cloud Mashery to fuel rapid innovations.
  • TIBCO Mashery Sidecar integration facilitates processing output of the Lambda function and apply following business rule polices including but not limited to:
    1. If the API request is allowed without modification
    2. If the API request is allowed with instructions to
      1. Add headers to the request/response
      2. Drop headers from the request/response
    3. If the API request is terminated
      1. The error code to be sent to the consumer
      2. An optional message giving an opaque error message.
  • Sidecar Connector constructs the JSON object as input to the AWS Lambda function by compiling necessary data elements from the request explicitly as well as configurable inputs.
  • Sidecar integration is agnostic to user stories implementation details in AWS Lambda provided AWS Lambda function request and response specs are clearly defined and compliant to integration specs.

Related Links

Last updated November 16, 2021