Updating the Log Forwarder Parcel

If you want to use a newer set of custom Log Forwarder configuration files to send the logs to an External Audit Store, then you must update, distribute, and activate the PTY_LOGFORWARDER_CONF parcel on all the nodes in the cluster.

To create the updated log forwarder parcel:

  1. Log in to the staging machine.

  2. Nagivate to the directory where you extracted the installation files.

  3. To execute the configurator script, run the following command:

    ./BDPConfigurator_CDP-AWS-DataHub-7.3_<BDP_Version>.sh

  4. Press ENTER. The prompt to continue the installation appears.

    *******************************************************************************
            Welcome to the Big Data Protector Configurator Wizard
*******************************************************************************
This will setup the Big Data Protector Installation Files for CDP AWS Data Hub.

Do you want to continue? [yes or no]:

  5. To continue, type yes.

  6. Press ENTER. The prompt to select the type of installation files appears.

    Big Data Protector Configurator started...
Unpacking...
Extracting files...


Select the type of Installation files you want to generate.
[ 1: Create All ]      : Creates entire Big Data Protector CSDs, Parcels, Recipes and other files.
[ 2: Update PTY_CERT ] : Creates new PTY_CERT parcel with an incremented patch version.
                        Use this if you have updated the ESA certificates.
[ 3: Update PTY_LOGFORWARDER_CONF ]
                    : Creates new PTY_LOGFORWARDER_CONF parcel with an incremented patch version.
                        Use this if you want to set Custom LogForwarder configuration files to
                        forward logs to an External Audit Store.

[ 1, 2 or 3 ]:

  7. To update the PTY_LOGFORWARDER_CONF parcel, type 3.

  8. Press ENTER. The prompt to select the operating system version for the parcel appears.

    Select the OS version for Cloudera Manager Parcel.
This will be used as the OS Distro suffix in the Parcel name.

[ 1: el7 ]    :  RHEL 7 and clones (CentOS, Scientific Linux, etc)
[ 2: el8 ]    :  RHEL 8 and clones (CentOS, Scientific Linux, etc)
[ 3: el9 ]    :  RHEL 9 and clones (CentOS, Scientific Linux, etc)
[ 4: sles12 ] :  SuSE Linux Enterprise Server 12.x
[ 5: sles15 ] :  SuSE Linux Enterprise Server 15.x

Enter the no.:

  9. Depending on the requirements, type 1, 2, 3, 4 or 5 to select the operating system version for the Big Data Protector parcels.

  10. Press ENTER. The prompt to enter the S3 URI to upload the installation files appears.

    Enter the S3 URI where the BDP Installation files are to be uploaded.

(E.g. s3://examplebucket/folder):

  11. Enter the location of the S3 bucket to host the installation files.

  12. Press ENTER. The prompt to select the upload type appears.

    Choose one option among the following for BDP Installation files:
[ 1 ] : Upload files to 's3://<bucket_name>/<directory_name>/' S3 URI.
[ 2 ] : Generate files locally to current working directory. (You would have to manually upload the files to the specified S3 URI)

[ 1 or 2 ]:

  13. To upload the installation files to the S3 bucket, type 1.

  14. Press ENTER. The prompt to select the type of AWS access keys appears.

    Choose the Type of AWS Access Keys from the following options:
[ 1 ] : IAM User Access Keys (Permanent access key id & secret access key)
[ 2 ] : Temporary Security Credentials (Temporary access key id, secret access key & session token)

[ 1 or 2 ]:

  15. Depending upon the authentication option, the script will prompt for the following inputs:

    OptionDescription
    1Prompts to enter the following permanent IAM user access keys:
    AWS_ACCESS_KEY_ID
    AWS_SECRET_ACCESS_KEY
    2Prompts to enter the following temporary security credentials:
    AWS_ACCESS_KEY_ID
    AWS_SECRET_ACCESS_KEY
    AWS_SESSION_TOKEN

  16. Enter the required credentials.

  17. Press ENTER.

    The prompt to enter local directory path that stores the LogForwarder configuration files for External Audit Store appears.

    Enter the local directory path on this machine that stores the LogForwarder configuration files for External Audit Store:

  18. Enter the location where the Log Forwarder configuration files are stored.

  19. Press ENTER. The script generates the installation files and the prompt to enter the current version of the PTY_LOGFORWARDER_CONF parcel appears.

    Generating Installation files...

NOTE:
You can verify the version of the activated PTY_LOGFORWARDER_CONF parcel from the parcel
name, such as PTY_LOGFORWARDER_CONF-x.x.x.x_CDPx.x.p<version>-<os>.parcel, where the
<version> parameter denotes the patch version of the PTY_LOGFORWARDER_CONF parcel.

For Example: If the current activated PTY_LOGFORWARDER_CONF parcel is
PTY_LOGFORWARDER_CONF-x.x.x.x_CDPx.x.p0-<os>.parcel, the patch version of the PTY_LOGFORWARDER_CONF
parcel will be 0. Do NOT include 'p' while specifying the version.

Enter the <version> of the current PTY_LOGFORWARDER_CONF Parcel as specified in the parcel name [0]:

  20. Enter the current activated patch version of the PTY_LOGFORWARDER_CONF parcel.

  21. Press ENTER. The script updates the PTY_LOGFORWARDER_CONF parcel and uploads them to the S3 bucket.

    ****************************************************************************************************************************************

Retrieving the S3 bucket's AWS Region via AWS S3 REST API...
Successfully retrieved S3 bucket's AWS region: <region_name>


Started uploading the updated PTY_LOGFORWARDER_CONF parcel to S3 bucket using REST API.

Uploading PTY_LOGFORWARDER_CONF-<BDP_version>_CDP7.3.p<patch_version>-<operating_system_version>.parcel...
-> File uploaded to s3://<bucket_name>/<directory_name>/Updated_LOGFORWARDER_CONF_Parcel/PTY_LOGFORWARDER_CONF-<BDP_version>_CDP7.3.p<patch_version>-<operating_system_version>.parcel

Uploading PTY_LOGFORWARDER_CONF-<BDP_version>_CDP7.3.p<patch_version>-<operating_system_version>.parcel.sha...
-> File uploaded to s3://<bucket_name>/<directory_name>/Updated_LOGFORWARDER_CONF_Parcel/PTY_LOGFORWARDER_CONF-<BDP_version>_CDP7.3.p<patch_version>-<operating_system_version>.parcel.sha

Successfully uploaded the updated PTY_LOGFORWARDER_CONF parcel to S3 URI: s3://<bucket_name>/<directory_name>

****************************************************************************************************************************************

* The updated PTY_CERT parcel 'PTY_LOGFORWARDER_CONF-<BDP_version>_CDP7.3.p<patch_version>-<operating_system_version>.parcel' and sha1 checksum are locally generated in ./Installation_Files/ directory.

****************************************************************************************************************************************

Successfully configured the Updated PTY_LOGFORWARDER_CONF parcel for CDP AWS DataHub.

    If you use the option to locally generate the installation files, the script generates them under the ./Installation_Files/ directory.

    ****************************************************************************************************************************************

* The updated PTY_LOGFORWARDER_CONF parcel 'PTY_LOGFORWARDER_CONF-<BDP_version>_CDP7.3.p<patch_version>-<operating_system_version>.parcel' and sha1 checksum are locally generated in ./Installation_Files/ directory.
-> Manually copy the PTY_LOGFORWARDER_CONF-<BDP_version>_CDP7.3.p<patch_version>-<operating_system_version>.parcel and .sha files to Cloudera Manager Server's local parcel repository on the existing running Data Hub cluster.

****************************************************************************************************************************************

Successfully configured the Updated PTY_LOGFORWARDER_CONF parcel for CDP AWS DataHub.

Last modified : December 18, 2025