AWS OpenSearch configuration

AWS OpenSearch configuration

To enable direct delivery of all job data and have control over the data retention it is possible to have your own ElasticSearch compatible server at Amazon and get it directly connected to the PrintFactory cloud infrastructure under the Automation account for customer with more than 20 printers in the plan.

Below is a short rundown on how to start your own OpenSearch server on Amazon.

  1. Create an AWS OpenSearch domain using the following settings:
    • Domain name: any; for example “data”
    • Deployment type: any (suitable for organisation availability requirements)
    • Version: OpenSearch latest
    • Enable compatibility mode: no
    • Auto-tune: any
    • Availability Zones: any suitable
    • Instance type: t3.small.search or bigger
    • Number of nodes: 1 or more
    • Storage type: EBS
    • EBS storage size per node: 10 GiB or more
    • Network: public access
    • Fine-grained access controle: master user
    • Access policy: “Configure domain level access policy.
      • Visual Editor -> add IP addresses allowed to connect: Cloud service ip address “34.233.221.212” and any ip addresses you are going to access OpenSearch or Kibana”
  2. Login to Kibana with master password
    • Select your tenant: global
    • Add a User for Cloud indexer
      • Open Security
      • Internal users
      • Create internal user
      • Username: any
      • Password: use string password 12+ characters length; digits, special characters etc
    • Create a role
      • Open Roles
      • Name: any
      • Cluster permissions: index_all
      • Index permissions: index *, permissions: index_all
      • Create
      • Open Mapped users tab
      • Map user PrintFactory
  3. Provide to username, password and domain endpint URL to your account manager at PrintFactory. He/She will make sure the PrintFactory cloud is connected to your server. When is reported back that this was successful you can proceed with the next steps.
  4. Create a Job in PF (to be indexed)
  5. Create Index Pattern
    • Open Stack Management -> Index Patterns
    • Create Index pattern
    • Index pattern name: jobxml*
    • Time field: Job.Created
  6. Create more Jobs. Indexed JSON will appear on “Discover” page.


    • Related Articles

    • Rip driver error: Failed to load the driver. Please restart the RIP

      Meaning: This error means that the components in the caches can not be downloaded. Triage: Please check the RIP log. Could be that the driver components are missing on AWS or that the Windows redistrib. needs to be installed. Ref. e.g. Fuji Prime ...

    • Private Cloud Storage

      PrintFactory default account set-up is to store your data in the data center the belongs to your region. This means that if your company is located in Europe then the data will be stored in the European data center. In case you would like to store ...

    • Durst Linux Integration

      Hotfolders When selecting the hotfolder in printfactory RIP, you can select the "Hotfolders" folder and within the PMMs you can choose a numbered folder that you would like to send the output to depending on the PMM. If you send a job, and you do not ...

    • Job Status Tracking with PrintAgent for Zünd Cut Center

      Setting Up Job Status Tracking with PrintAgent for Zünd Cut Center This guide explains how to enable job status tracking between PrintFactory RIP and Zünd Cut Center (ZCC) using PrintAgent. Once configured, job progress will be automatically ...

    • Workflow Menu

      Windows You can find the menu here. Mac You can find the menu here. Preferences Connection Concurrent jobs Number of Jobs Workflow may process simultaneously. Each CPU (core) on your Computer can do 1 Job at a time, so maximum to be set to the amount ...