Setting up Connect:Direct Node on object store providers

By default, cloud support for Connect:Direct is not enabled. To enable cloud support, complete the following tasks:

Connect:Direct® for UNIX can also be configured to extend support to other S3 object store providers such as Minio, Dell EMC ECS, and Red Hat Ceph or use dedicated endpoints to execute public and on-premise cloud-based operations. For endpoint configuration/override see the dedicated section.

Pre-requisites to set-up Connect:Direct Unix on cloud provider

Before you configure Connect:Direct node definitions necessary for using Connect:Direct for UNIX, you must complete the following tasks:
  1. Set up cloud accounts and credentials
  2. Select and create a compute instance, RedHat or SuSE
  3. Create IAM user/roles
  4. Create Security group. Port numbers which are specific to Connect:Direct should be added to the security group
  5. Create storage
  6. Obtain credentials for cloud storage object access

For more information see, Account (amazon.com), Get started with Google Cloud | Documentation, IBM Cloud Docs, Azure documentation | Microsoft Docs

Connect:Direct for UNIX can also be configured to extend support to other object store providers such as Minio S3, Dell EMC ECS S3, Red Hat Ceph S3 or use dedicated endpoints to execute public and on-premise cloud-based operations. For endpoint configuration/override see the dedicated section.

Installing Connect:Direct Unix node on Cloud

No specific configuration is required to install Connect:Direct for UNIX node on an EC2 instance. For information to install Connect:Direct for UNIX see, Installing Connect:Direct for UNIX.

If you are upgrading from an old release of Connect:Direct for UNIX node note that:
  • CD Unix, Linux platform, and JRE are now included in the base installation
  • Initparms to be included during the S3 plugin configuration are updated during the upgrade process

Configuration considerations

  • All values used to change the default store IO EXIT behavior should be provided through properties, either by declaring them as defaults via. initparms.cfg file or by declaring specific values in sysopts.
  • A properties is searched first in sysopts. If no value is retrieved from sysopts, the default value declared in the initparm.cfg file is used.
  • A parameter declared in sysopts overrides the initparm.cfg file property value.