InterSystems IRIS Licensing for ICM

InterSystems IRIS instances deployed in containers require licenses just as do noncontainerized instances. General InterSystems IRIS license elements and procedures are discussed in the “LicensingOpens in a new tab” chapter of the System Administration Guide.

License keys cannot be included in InterSystems IRIS container images, but must be added after the container is created and started. ICM addresses this as follows:

The needed license keys are staged in a directory within the ICM container, or on a mounted volume, that is specified by the LicenseDir field in the defaults.json file, for example /Samples/License.
One of the license keys in the staging directory is specified by the LicenseKey field in each definition of node types DATA, COMPUTE, DM, AM, DS, and QS in the definitions.json file, for example:
```
"Role": "DM",
"LicenseKey": "ubuntu-sharding-iris.key”,
"InstanceType": "m4.xlarge",
```
ICM configures a license server on DATA node 1 or the DM node, which serves the specified licenses to the InterSystems IRIS nodes (including itself) during deployment.

Important:

All files staged in the directory indicated by the LicenseDir field and specified by the LicenseKey field must be valid InterSystems IRIS license key files with the .key suffix.

All nodes on which an InterSystems IRIS container is deployed require a sharding-enabled InterSystems IRIS license, regardless of the particular configuration involved.

No license is required for AR, LB, WS, VM, and CN nodes; if included in the definition for one of these, the LicenseKey field is ignored.

A license is optional for SAM nodes, but if one is provided, it will be used.

ICM Security

Storage Volumes Mounted by ICM