Merge branch 'develop'

This commit is contained in:
cedricve
2021-10-15 10:11:01 +02:00
16 changed files with 42 additions and 3 deletions

Binary file not shown.

Before

Width:  |  Height:  |  Size: 1.4 MiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 4.9 MiB

View File

@@ -131,7 +131,7 @@ On the other hand it's an open platform, as it allows you build extensions and i
To connect one or more Kerberos Agents to your Kerberos Vault instance, you should open the configuration option and navigate to the `cloud` tab. After selected you need to fill-in the credentials from your Kerberos Vault account.
To connect one or more Kerberos Agents to your Kerberos Vault instance, you should open the configuration option and navigate to the `cloud` tab. After selected you need to fill-in the credentials from your Kerberos Vault account.
- Storage URI: this is the API endpoint of your Kerberos Vault instance. Usually this is in the following format: `http(s)://api.yourdomain.com/storage`. Where `api.yourdomain.com` should match your Kerberos Vault API endpoint.
- Storage URI: this is the API endpoint of your Kerberos Vault instance. Usually this is in the following format: `http(s)://api.yourdomain.com/storage`. Where `api.yourdomain.com` should match your Kerberos Vault API endpoint. If you are deploying Kerberos Vault at the edge, in the same cluster, you can use the internal DNS name, as following `http://kerberos-vault.kerberos-vault:8081/storage`.
- Provider: the name of the provider, which you created on the Kerberos Vault providers page, to which you want to send your recordings to.
@@ -151,7 +151,7 @@ You have two choices when using Kerberos Hub, either you send your recordings fr
Select the Kerberos Hub option, and copy-paste the credentials from your Kerberos Hub subscription.
{{< figure src="enterprise-to-hub.gif" alt="By linking your Enterprise agent to Kerberos Hub, your recordings and livestreams will become available online." caption="By linking your Enterprise agent to Kerberos Hub, your recordings and livestreams will become available online." class="stretch">}}
{{< figure src="hub-integration.gif" alt="By linking the Kerberos Agent to Kerberos Hub, your recordings and livestreams will become available online." caption="By linking your Enterprise agent to Kerberos Hub, your recordings and livestreams will become available online." class="stretch">}}
- Region: this is the region where your recordings will be stored. Only `eu-west-1` for now (will change, on the roadmap).

View File

@@ -55,7 +55,44 @@ Kerberos Vault integrates with storage providers in the cloud such as AWS S3, GC
### Storj
> Tutorial to be written.
#### Introduction
Storj DCS is the worlds first open-source, decentralized cloud storage layer thats private by design and secure by default - enabling developers to build in the best data protection and privacy into their applications as possible. The zero trust architecture, multi-region high availability, default encryption and edge-based access controls minimize risk and give only you, or those you grant permission to, access to your files. The result is that you take back full ownership and control of your data.
The Storj DCS Satellite Admin Console supports uploading and managing objects directly through the browser with no command-line tool required. This component uses our hosted S3-compatible Gateway service.
#### Create an Account
To start using Storj, an account has to be created [on the public Storj cloud application](https://eu1.storj.io/signup). Once you are signed up, you will go through the traditional on-boarding and verification flow.
{{< figure src="storj-signup.gif" alt="Create an account at Storj.io" caption="Create an account at Storj.io" class="stretch">}}
#### Configure Object Browser Access
Once you activated your account, go ahead and sign in to your profile. The first time you've signed in you will be asked to create a Bucket. Select the Upload In Browser, and give a specific name to your Bucket.
{{< figure src="storj-create-bucket.gif" alt="Create a Storj bucket." caption="Create a Storj bucket." class="stretch">}}
#### Create Access Grant
So now we have created a Bucket, we will need to have credentials to interact with it. Go to the "Access" page, select the (Create Access Grant) button at the top. Provide the required fields, and select the option (Generate S3 Gateway Credentials).
{{< figure src="storj-access.gif" alt="Create a Storj Access Grants." caption="Create a Storj Access Grants." class="stretch">}}
#### Integrate
Now you are ready to assign Storj as a storage provider to Kerberos Vault. Open the `Providers` page of Kerberos Vault, and select the Storj provider.
{{< figure src="storj-integrate.gif" alt="Integrate Storj.io with Kerberos Vault." caption="Integrate Storj.io with Kerberos Vault." class="stretch">}}
- Provider name: this a preferred name for the provider.
- Bucket name: the name of a bucket created in Storj, make sure this matches.
- Region: this is not relevant for an edge deployment and can be left blank.
- Hostname: this is the DNS name for the Storj Gateway and relevant region, for example: **gateway.eu1.storjshare.io**.
- Access Key: the `access key` you've received when generating the S3 Gateway credentials.
- Secret Access Key: the `secret key` you've received when generating the S3 Gateway credentials.
## Edge storage providers
@@ -107,6 +144,8 @@ While accessing the console, you can create a new Bucket.
{{< figure src="minio-create-bucket.gif" alt="Create a bucket in Minio." caption="Create a bucket in Minio." class="stretch">}}
#### Integrate
Now you are ready to assign Minio as a storage provider to Kerberos Vault. Open the `Providers` page of Kerberos Vault, and select the Minio provider.
{{< figure src="minio-setup.gif" alt="Configuring the minio provider in Kerberos Vault." caption="Configuring the minio provider in Kerberos Vault." class="stretch">}}

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.3 MiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.5 MiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 832 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 824 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 763 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 814 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 794 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 761 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 772 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 844 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 760 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.1 MiB