This article provides instructions for configuring your own custom AWS storage endpoints. This will route media files (images and recordings) to the storage service and region of your choice, and will not be stored on Blitzz Servers.
STEPS
- Step 1: Create an S3 Storage Service on AWS
- Step 2: Configure CORS
- Step 3: Create AWS Access Keys
- Step 4: Configure Blitzz Portal
- Step 5: Finally, test your new endpoints
Step 1: Create an S3 Storage Service on AWS
This is where your images and recordings from Blitzz Sessions will be stored. Please select the region of your choice.
- Sign up and create an account on AWS Console if you don’t have one already.
- Navigate to S3 Services in AWS Portal (https://s3.console.aws.amazon.com/)
- Create a new bucket
- Enable Public access
Step 2: Configure CORS
Cross-origin resource sharing (CORS) defines a way for client web applications that are loaded in one domain to interact with resources in a different domain. Learn more.
Ensure you have Cross-Origin Resource Sharing (CORS) enabled in your storage account and allowed these URLs as the origin URL with GET, POST, PUT, OPTIONS methods.
- https://web.blitzz.co
- https://join.blitzz.co
- https://<subdomain>.blitzz.co - This is your custom subdomain on Blitzz domain
- https://example.company.com - Only for custom host mapping. see instructions
To Set up CORS:
- Go to your Bucket > Permissions > CORS Configuration
- Copy and paste the code below (remember to change the <subdomain> with your own subdomain)
<?xml version="1.0" encoding="UTF-8"?>
<CORSConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<CORSRule>
<AllowedOrigin>https://web.blitzz.co</AllowedOrigin>
<AllowedMethod>GET</AllowedMethod>
</CORSRule>
<CORSRule>
<AllowedOrigin>https://join.blitzz.co</AllowedOrigin>
<AllowedMethod>GET</AllowedMethod>
</CORSRule>
<CORSRule>
<AllowedOrigin>https://<subdomain>.blitzz.co</AllowedOrigin>
<AllowedMethod>GET</AllowedMethod>
</CORSRule>
</CORSConfiguration>
Only for Custom Host Mapping (Eg. https://example.company.com)
If you have set up custom host mapping for your account, it is very important you whitelist your own subdomain as well by including that block of code.
Example:
<?xml version="1.0" encoding="UTF-8"?>
<CORSConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<CORSRule>
<AllowedOrigin>https://web.blitzz.co</AllowedOrigin>
<AllowedMethod>GET</AllowedMethod>
</CORSRule>
<CORSRule>
<AllowedOrigin>https://join.blitzz.co</AllowedOrigin>
<AllowedMethod>GET</AllowedMethod>
</CORSRule>
<CORSRule>
<AllowedOrigin>https://<subdomain>.blitzz.co</AllowedOrigin>
<AllowedMethod>GET</AllowedMethod>
</CORSRule>
<CORSRule>
<AllowedOrigin>https://example.company.com</AllowedOrigin>
<AllowedMethod>GET</AllowedMethod>
</CORSRule>
</CORSConfiguration>
Step 3: Create AWS Access Keys
- Navigate to My Security Credentials from the drop-down menu
- Under Access Keys, select "Create New Access Key"
- Copy your access key. We will need to paste them in your Blitzz Admin Console (see Step 5)
Step 4: Configure Blitzz Portal
- Login to your Blitzz Portal as an Admin
- Click on the Settings gear (top right) > Custom Storage. Select AWS Storage from the options.
- Enter your Access Key, Secret, Bucket Name, and the Region where your S3 Bucket is located.
- Click Next and Test your connection. This step will store a temporary file (temp.jpeg) in the miscellaneous folder of your AWS Bucket.
Step 5: Finally, test your new endpoints
- Navigate to Blitzz ShowMe, and Create a new session.
- Join the session and Capture images during the session. If Recording* is enabled for the Collaboration Profiles, the recorded file will also be stored in your new storage account.
- Navigate to your AWS bucket and locate the images (and recordings if enabled).
* Recordings and Processing time: If your Blitzz Subscription plan includes recording, you can configure your Collaboration Profiles to have the videos recorded. Please note that there may be a delay of about 20 minutes (depending on the length of your call) to process the recordings before you see them in your storage account.
Here is a quick cheat sheet to test everything works well:
Test Number | Test Case | Test Result |
1 | Create and session with recording enabled | Pass / Fail |
2 | Take image | Pass / Fail |
3 | Save Markup Image | Pass / Fail |
4 | Save OCR image | Pass / Fail |
5 | Download images from Azure Portal | Pass / Fail |
6 | Download recording from Azure Portal | Pass / Fail |
7 | Download images from Blitzz Portal | Pass / Fail |
8 | Download recordings from the Blitzz portal | Pass / Fail |
Update on 12 April 2021
We have introduced a new feature "Display Bookmark and Location of images in Session Details and MS Word Report".
This Blitzz Inspect feature adds the Bookmark and Location details and view image details link to the MS Word Report and each image in Session Details.
To use this feature with your AWS storage, you need to add some extra line of configuration in your existing configured S3 bucket. Please see highlighted text below.
[
{
"AllowedHeaders": [
"*"
],
"AllowedMethods": [
"GET",
"HEAD"
],
"AllowedOrigins": [
"*"
],
"ExposeHeaders": [
"x-amz-meta-Latitude",
"x-amz-meta-Longitude",
"x-amz-meta-Bookmark"
],
"MaxAgeSeconds": 3600
}
]
Once you add this to your account you will be able to use this feature.
Note: This will be applicable only for the new images taken once this new configuration is added and not for the older images.
Related articles:
- Configure MS Azure Cloud storage storage
- Saving Images and Recordings to Custom Cloud Storage (Eg. Google Drive, Box, DropBox, etc)