PrizmDoc v13.2 - Updated
PrizmDoc Cloud License & AWS
Designed for customers who need the ability to scale or upgrade their servers at any moment, PrizmDoc Cloud Licensing allows you to 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.
To set up cloud licensing, you will need to do the following:
The sections below provide additional information for each step.
First, make sure you have an S3 bucket set up which PrizmDoc can read and write to at runtime. See the Amazon S3 documentation for more information on setting up an S3 bucket.
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.
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.
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.
There are several options for loading credentials. They are listed in the order of recommendation:
For example, using method 2 above, you can configure your server to export the credentials to the environment for the user under which PrizmDoc will execute:
In Linux
| Example |
Copy Code
|
|---|---|
export AWS_ACCESS_KEY_ID=XXXXXXXXXX export AWS_SECRET_ACCESS_KEY=XXXXXXXXXX |
|
In Windows
| Example |
Copy Code
|
|---|---|
set AWS_ACCESS_KEY_ID=XXXXXXXXXX set AWS_SECRET_ACCESS_KEY=XXXXXXXXXX |
|
After configuring the credentials for Amazon S3, install the license key using the instructions provided in the OEM Licensing topic.
