AWS Kinesis Configuration for Holdings MS

If you execute the install-aws-dynamo.sh / install-aws-postgresql.sh, the <multideployment>-external-holdings-command-event kinesis will be automatically created and it will be linked to the EventProcessor Ingestion Lambda Function

In the AWS portal it will be as follows:

Method 1:

If the Event Processor Kinesis is already created & working, then change the following configuration in install-aws-dynamo.sh / install-aws-postgresql.sh as follows:

EP_INGEST_SOURCE_STREAM - kinesis for Event Processor

Method 2:

If the Event Processor Kinesis is not present in AWS Environment then install-aws-dynamo.sh / install-aws-postgresql.sh will automatically create the kinesis.

If you execute the install-aws-dynamo.sh / install-aws-postgresql.sh, the <multideployment>-external-holdings-command-event Kinesis will be automatically created if it does not exists.

In the AWS portal it will be as follows:

If you execute the install-aws-dynamo.sh / install-aws-postgresql.sh, the assembled-event-MSRetail kinesis will be automatically created and it will be linked to the Internal Ingestion Lambda Function.

In the AWS portal it will be as follows:

Method 1:

If the Transact Kinesis is already created & working, then change the following configuration in install-aws-dynamo.sh / install-aws-postgresql.sh as follows:

INGEST_SOURCE_STREAM - kinesis for T24

temn_msf_schema_registry_url - localhost/subjects for DES Transact

Method 2:

If the Transact Kinesis is not present in AWS Environment then install-aws-dynamo.sh / install-aws-postgresql.sh will automatically create the kinesis.

If you execute the install-aws-dynamo.sh / install-aws-postgresql.sh, the assembled-event-MSRetail Kinesis will be automatically created if it does not exists.

In the AWS portal it will be as follows:

Note that this Kinesis for Transact will have the default name with the syntax of <eventName>-<systemName> eg. assembled-event-MSRetail

Method 1:

If the Account Aggregation Kinesis is already created & working, then change the following configuration in install-aws-dynamo.sh / install-aws-postgresql.sh as follows:

EXT_INGEST_SOURCE_STREAM - kinesis for Account Aggregation

Method 2:

If the Account Aggregation Kinesis is not present in AWS Environment then install-aws-dynamo.sh / install-aws-postgresql.sh will automatically create the kinesis.

If you execute the install-aws-dynamo.sh / install-aws-postgresql.sh, the external-holdings-event Kinesis will be automatically created if it does not exists.

In the AWS portal it will be as follows:

If you execute the install-aws-dynamo.sh / install-aws-postgresql.sh, the external-holdings-event kinesis will be automatically created and it will be linked to the Account Aggregation Ingestion Lambda Function

In the AWS portal it will be as follows: