PrizmDoc v13.3 - Updated
PrizmDoc Cloud License & AWS
Administrator Guide > Deployment Licensing > PrizmDoc Cloud License & AWS

Overview

PrizmDoc Cloud Licensing is designed for customers who need the ability to scale or upgrade their servers at any moment. You can easily and flexibly use PrizmDoc Server across a paid number of total CPU cores. Just pay for the peak number of cores you will need and then use your Cloud License for every server you deploy into your cluster. As long as the total number of CPU cores in your cluster does not exceed the limit you paid for, you can add, remove, or upgrade servers at any time, whether you are running one server or one thousand.

PrizmDoc Cloud Licensing only requires your servers be able to communicate with AWS S3 for licensing enforcement. It makes no demands on where your servers reside. You can run your servers in any of the popular cloud providers, like Amazon, Azure, or Google Cloud, or you can even use your own servers on local hardware or VMs. As long as each of the servers in your cluster can communicate with AWS S3, you can use a PrizmDoc Cloud License.

To use a Cloud License, the only thing you need to make available to PrizmDoc is an S3 bucket which PrizmDoc can read and write to. At runtime, each of the PrizmDoc Server instances in your cluster will read and write extremely-small, temporary files into this bucket as part of licensing enforcement.

Setting Up Cloud Licensing

To set up cloud licensing, you will need to do the following:

  1. Set up your Amazon S3 Account and S3 bucket.
  2. Purchase cloud-based licensing from Accusoft.
  3. Obtain License Key from Accusoft by providing Amazon S3 bucket name.
  4. Configure Amazon S3 credentials.
  5. Install Accusoft License Key using OEM Licensing instructions.

The sections below provide additional information for each step.

1 - Set up your Amazon S3 Account and S3 Bucket

First, you must have an Amazon AWS account in order to create an S3 bucket. Log into your AWS account console and create an S3 bucket which PrizmDoc can read and write to at runtime. See the Amazon S3 documentation for more information on setting up an S3 bucket and acquiring credentials. You may want to consider creating a dedicated AWS user which only has read / write credentials for your bucket.

2 - Purchase a Cloud License for PrizmDoc Enterprise

To purchase a PrizmDoc Cloud License, go to Accusoft's website and fill out a quote form online or contact sales at sales@accusoft.com.

During purchase, specify the maximum number of CPU cores to be provided by the license. Make sure you purchase enough cores for your cluster to enable production, support, and any ongoing development efforts. You may want to consider purchasing separate licenses for both production and development.

3 - Obtain a License Key from Accusoft

Once purchased, visit the Accusoft Customer Portal to view your purchased license and provide the S3 bucket name that you will use for Cloud Licensing. After providing your S3 bucket name, your Cloud License key will be given to you. Note: It is your responsibility to provide a valid S3 bucket and to ensure that you have the proper credentials to access that bucket.

  1. Enter your Amazon S3 bucket name in the field provided and click the Activate License button:

  2. Download your solution name and activated license key to be used when configuring PrizmDoc on your server:

4 - Configure Amazon S3 Credentials

When running PrizmDoc with a Cloud License on your server, it will require access to the Amazon S3 bucket you provided when your license was generated. It is important to note that PrizmDoc requires no knowledge of your S3 credentials. PrizmDoc accesses Amazon S3 assuming that your credentials have been provided using one of the methods defined in the Amazon SDK documentation that do not require explicitly providing them to the API. As shown below, using method 1, 2, or 3 will provide access to AWS S3.

If you are new to Amazon Web Services, you should familiarize yourself with the Security Credentials to get an overview.

There are three options for configuring your AWS credentials for cloud licensing. They are listed in the order of recommendation:

  1. Configure IAM roles for Amazon EC2 (if running on EC2), or
  2. Configure the Shared Credentials File (~/.aws/credentials), or
  3. Configure Environment Variables.

NOTE: When setting credentials, be sure that the user under which the PrizmDoc service is running is the same user for which you are configuring the credentials. For example, consider the case where you configure the credentials for your personal user, but PrizmDoc is running as the root user. In this case the service will start, but then shut down shortly after because the root user will be unable to access the S3 bucket specified in your cloud license key.

Examples using IAM Roles are beyond the scope of this document, but if your cluster is running on AWS EC2 instances, you can find information about IAM Roles and their configuration in the Amazon IAM documentation.

An example using method 2 above, Shared Credentials Files, are shown below. You can configure a shared credentials file for the user under which PrizmDoc will execute:

In both Linux and Windows, the credentials file content is the same.

Example Credentials File Content

[default]
aws_access_key_id = your_access_key_id
aws_secret_access_key = your_secret_access_key

Credential files are stored under an .aws directory for the user under which PrizmDoc is executing. The credential file paths below are for an example, prizmdocuser.

In Linux

/home/prizmdocuser/.aws/credentials

In Windows

C:\Users\prizmdocuser\.aws\credentials

Examples using method 3 above, environment variables, are shown below. You can configure your server to export the credentials to the environment for the user under which PrizmDoc will execute:

In Linux

Exporting environment variables under Linux is usually done in the user's .profile file in their home directory (e.g. for a user named prizmdocuser these would be added to /home/prizmdocuser/.profile).

Example

export AWS_ACCESS_KEY_ID=your_access_key_id
export AWS_SECRET_ACCESS_KEY=your_secret_access_key

In Windows

Exporting environment variables under Windows is done in the Environment Variables control panel under the System Properties.

Example

5 - Install Your License Key as an "OEM License"

After configuring the credentials for Amazon S3, install the license key using the instructions provided in the OEM Licensing topic.

 

 

©2018. Accusoft Corporation. All Rights Reserved.

Send Feedback