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

    • swissQprint Karibu – Configuration setup

      When installing the swissQprint karibu driver in the RIP, the specific content for this driver (e.g. ink channels, print modes,..) needs to be obtained from the configuration file created on the Lory Front-End of the printer. To find the .sqpe file ...

    • 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 ...

    • Double Sided Nesting with Queues

      This can be setup as follows: 1. Create a new Queue for the Printer that you want to use for DSP. 2. In the layout settings of the queue enable Double Sided Printing and choose the required configuration: 3. Then configure the nesting settings in the ...

    • In-RIP Nesting

      Concept This topic discusses the Nesting functionality available in the RIP. This is important not to confuse with the nesting functionality in the Layout application. Once configured, the Nesting functionality takes jobs from Hotfolders, received ...

    • SwissQprint driver features using PrintAgent

      From V6.6 onwards the SwissQprint uses the PrintAgent service to retrieve job status tracking and job information from the printer to the RIP. More info re PrintAgent, the installer and how to install it can be found here. The PrintAgent also allows ...