add vault integrations

content/vault/accounts/index.md

@@ -9,7 +9,7 @@ images: []
 menu:
     vault:
         parent: "vault"
-weight: 306
+weight: 307
 toc: true
 ---
 

content/vault/first-things-first/index.md

@@ -56,7 +56,9 @@ Each time a Kerberos Agent sends a recording to Kerberos Vault, it is persisted
 - [Kerberos Hub](/hub/first-things-first/)
 - Kerberos Vault (remote forwarding)
 
-Every time an event is delivered, it will be consumed by the configured integrations. For example in case of a Kafka integration, one can build a Kafka consumer with custom application logic; a notification manager, a machine learning service, etc. Find more information about events and integrations on [the integrations page](/vault/integrations).
+Every time an event is delivered, it will be consumed by the configured integrations. For example in case of a Kafka
+integration, one can build a Kafka consumer with custom application logic; a notification manager, a machine learning
+service, etc. Find more information about events and integrations on [the integrations page](/vault/integrations).
 
 {{< figure src="vault-integrations.svg" alt="Build integrations and create your own workflows using the event capability of Kerberos Vault." caption="Build integrations and create your own workflows using the event capability of Kerberos Vault." class="stretch">}}
 

content/vault/forwarding/index.md

@@ -9,7 +9,7 @@ images: []
 menu:
     vault:
         parent: "vault"
-weight: 306
+weight: 309
 toc: true
 ---
 

content/vault/getting-started/index.md

@@ -40,13 +40,13 @@ Providers are the persistence layers, where you will store your recording in the
 - [Minio](https://min.io/)
 - [Ceph](https://ceph.io/)
 
-As explained before, for each provider, the appropriate security settings has to be filled in. For example for AWS you need to define the access and secret key, for GCP you need to define a service account.
+As explained before, for each provider, the appropriate security settings has to be filled in. For example for AWS you need to define the access and secret key, for GCP you need to define a service account. Find more information about storage providers [on the providers page](/vault/providers).
 
 {{< figure src="provider.gif" alt="One or more providers can be configured to centralise your storage." caption="One or more providers can be configured to centralise your storage." class="stretch">}}
 
 ## Integrations
 
-Events or messages are generated each time a recording was uploaded to Kerberos Vault, and are sent to one or more integrations. Those integrations are configured through the Kerberos Vault application. Each time a Kerberos Agent sends a recording to Kerberos Vault, it is persisted on a storage provider, and an event is triggered through one of the following integrations.
+Events or messages are generated each time a recording was uploaded to Kerberos Vault, and are sent to one or more integrations. Those integrations are configured through the Kerberos Vault application. Each time a Kerberos Agent sends a recording to Kerberos Vault, it is persisted on a storage provider, and an event is triggered through one of the following integrations. 
 
 - [Apache Kafka](https://kafka.apache.org/)
 - [Amazon Web Services SQS](https://aws.amazon.com/sqs/)
@@ -63,6 +63,8 @@ The idea of an integration is that you can build your own applications and defin
 - Counting algorithms,
 - and much more.
 
+Find more information about events and integrations on [the integrations page](/vault/integrations).
+
 ## Accounts
 
 Having setup `Providers` and `Integrations`, you need a secure way to interact with them through the creation of an account. 
@@ -81,6 +83,8 @@ Next to credentials, there are a couple of other fields which are specified on a
 
 {{< figure src="account.gif" alt="One or more accounts can be created to secure your storage access." caption="One or more accounts can be created to secure your storage access." class="stretch">}}
 
+Find more information about accounts on [the accounts page](/vault/accounts).
+
 ## Media
 
 Once a recording is stored inside a specific `Provider` it will show up on the `Media` page. The `Media` page is an overview, list page, of all your recordings being uploaded to a `Provider`. It is used for quickly reviewing activity.

content/vault/integrations/index.md

@@ -13,4 +13,59 @@ weight: 306
 toc: true
 ---
 
-ypp
+One of the key differentiators, is the ability to extend and integrate. Next to uploading and persisting recordings on your preferred storage providers, Kerberos Vault can trigger events and be configured through APIs.
+
+Each time a Kerberos Agent sends a recording to Kerberos Vault, it is persisted on a storage provider, and an event is triggered through one of the following integrations.
+
+- [Apache Kafka](https://kafka.apache.org/)
+- [Amazon Web Services SQS](https://aws.amazon.com/sqs/)
+- [Kerberos Hub](/hub/first-things-first/)
+- Kerberos Vault (remote forwarding)
+
+Every time an event is delivered, it will be consumed by the configured integrations. For example in case of a Kafka
+integration, one can build a Kafka consumer with custom application logic; a notification manager, a machine learning
+service, etc.
+
+## Prerequisites
+
+Before you can configure a provider, make sure [you have installed a Kerberos Vault](/vault/installation) inside a Kubernetes cluster.
+
+## Configuration of an integration
+
+Once you have set up your Kerberos Vault instance, and have successfully login to the application, you should see the integration navigation item on the left.
+
+{{< figure src="integrations.gif" alt="One or more providers can be configured to centralise your storage." caption="One or more providers can be configured to centralise your storage." class="stretch">}}
+
+When selecting the `+ Add Integration` button, a modal will open that allows you to configure a specific integration. Go a head and select one from the list.
+
+{{< figure src="add-integration.gif" alt="Configure, add and validate a new integration." caption="Configure, add and validate a new integration." class="stretch">}}
+
+Once completed the necessary credentials, specific to your integration, you can verify the connection by click the `Validate` button. If ok, it should return a `green` confirmation box, if something went wrong you should see the relevant error message in a `red` alert box. When completed you can add multiple and different integrations.
+
+## Cloud event integrations
+
+Kerberos Vault integrates with queues and message brokers in the cloud such as AWS SQS. The advantage is that it takes the complete control of your every growing messaging/event requirements. 
+
+### AWS SQS
+
+> Tutorial to be written.
+
+## Edge event integrations
+
+Alternatives to cloud event integrations are self-hosted variants such as a Kafka broker.
+
+### Kafka
+
+> Tutorial to be written.
+
+## Kerberos integrations
+
+Next to third party integrations such as Kafka or AWS SQS, it is possible to integrate with a remote Kerberos Vault, also called chaining or forwarding or with Kerberos Hub.
+
+### Kerberos Vault
+
+> Tutorial to be written.
+
+### Kerberos Hub
+
+> Tutorial to be written.

content/vault/license/index.md

@@ -9,7 +9,7 @@ images: []
 menu:
   vault:
     parent: "vault"
-weight: 307
+weight: 311
 toc: true
 ---
 

content/vault/machine-learning/index.md

@@ -9,7 +9,7 @@ images: []
 menu:
     vault:
         parent: "vault"
-weight: 306
+weight: 308
 toc: true
 ---
 

content/vault/recycle/index.md

@@ -9,7 +9,7 @@ images: []
 menu:
   vault:
     parent: "vault"
-weight: 306
+weight: 310
 toc: true
 ---
 
@@ -41,4 +41,4 @@ Modify the MongoDB credentials, as you did for the Kerberos Storage yaml file.
 Execute following script to deploy the recycle job.
 
     git clone https://github.com/kerberos-io/storage
-    kubectl apply -f ./storage/yaml/deployment-cleanup.yaml
+    kubectl apply -f ./storage/yaml/deployment-cleanup.yaml