Enable Extensions for Applications with Self-Hosted Deployment
- 19 Sep 2024
- 2 Minutes To Read
- Print
- DarkLight
- PDF
Enable Extensions for Applications with Self-Hosted Deployment
- Updated On 19 Sep 2024
- 2 Minutes To Read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Overview
Whatfix introduces an additional layer of security with Self-Hosted Extensions. Users who want to store their Whatfix extensions within their own AWS or Azure storage buckets rather than the Whatfix Cloud or a third-party store can use Whatfix’s Self-Hosted Extensions.
your title goes here
- The AWS and Azure storage access configuration is a one-time activity. This can be performed on the Whatfix dashboard.
- The extensions are hosted automatically on the storage bucket after the configuration.
- Updates to extensions are a one-click process on the Dashboard. Mass roll-out and other existing options remain the same.
Why did we introduce Self-Hosted Extension?
The end-user Whatfix extension package contains sensitive business data. Due to security reasons, some enterprises may not want to store the extension in the browser stores or on Whatfix Cloud. For such enterprises, Whatfix enables you to store the extension on your own cloud premise.
Self Hosted Extension enables you to configure a custom data store and push all the data to it when a push to production is done. Hence, no calls are made to the Whatfix server when publishing content.
Configure a Self-Hosted extension
Use the following steps to configure a Self Hosted extension:
On the Whatfix Guidance dashboard, click Settings.
Click Content Deployment.
In the Browser Extensions section, click Configurations.
Scroll down to the Self Hosted Deployment section and enter the necessary details in the fields provided. Based on the selected provider, AWS or Azure, you need to provide the following information:
Amazon Web Services
| Field Title | Description |
|---|---|
| Provider | Amazon Web Services |
| Bucket Name | Name of the AWS S3 bucket |
| Region | The AWS region where the bucket resides. |
| Access Key | The access key ID that uniquely identifies an AWS account. |
| Secret Key | The access key ID to send authenticated requests to Amazon S3. |
| C Name | Your bucket name must be the same as the C name. |
| End Point | The URL of the entry point for an AWS web service |
| Store Name | Name to indicate the store where you want to host the extension. |
Microsoft Azure
| Field Title | Description |
|---|---|
| Provider | Microsoft Azure |
| Container Name | Unique name for storage container. |
| Storage Account Name | Unique name for Azure Storage account. |
| SAS Token (with Read/Write/Delete access) | Token granting full access. |
| SAS Token (with Read access) | Token for read-only access. |
| Hostname | URL endpoint for storage. |
| Storage Write endpoint | Endpoint for write operations. |
Click Submit.
Click Push to production to validate if the extension is configured correctly.
Was this article helpful?