# Integrations

## Inbound

Getting data **into** a running Spherical instance is a straightforward process. It can be done by connecting an API gateway by following the relevant instructions on the following pages:

{% content-ref url="integrations/apigee" %}
[apigee](https://guide.sphericaldefence.com/guide/integrations/apigee)
{% endcontent-ref %}

{% content-ref url="integrations/kong" %}
[kong](https://guide.sphericaldefence.com/guide/integrations/kong)
{% endcontent-ref %}

{% content-ref url="integrations/aws-api-gateway" %}
[aws-api-gateway](https://guide.sphericaldefence.com/guide/integrations/aws-api-gateway)
{% endcontent-ref %}

Integrations with these API Gateways are implemented using AWS Lambda functions, in which an inbound HTTP method request from a client is mapped to a [Lambda function invocation](https://docs.aws.amazon.com/lambda/latest/dg/API_Invoke.html). By using a *Lambda Proxy Integration,* the entire request is passed wholesale into the Spherical instance. 

Inbound integrations should be performed ***after*** creating a Spherical instance.

## Outbound

Getting events **out of** a running Spherical instance is also a straightforward process. This is done asynchronously using AWS Lambda functions in a deployed **CloudFormation** stack (as discussed in the Summary). Currently there are only two outbound integrations, but it is very simple to implement your own Lambda functions to integrate with your own (or third party) services:

{% content-ref url="integrations/slack" %}
[slack](https://guide.sphericaldefence.com/guide/integrations/slack)
{% endcontent-ref %}

{% content-ref url="integrations/splunk" %}
[splunk](https://guide.sphericaldefence.com/guide/integrations/splunk)
{% endcontent-ref %}

Outbound integration steps should be performed ***before*** creating a Spherical instance.