Hang on, I'm confused. I thought RIH, from a licensing perspective, is restricted to only be used where Reltio is the sender or receiver of the info. So then why would RIH be involved in traffic between S3 and SQS??
------------------------------
Curt Pearlman
PwC
Agoura Hills CA
------------------------------
Original Message:
Sent: 07-27-2022 18:30
From: Ayan Basu
Subject: Connectivity between SQS and S3
Basudha, Gowthamprabhu stated it correctly. You'd need the access/secret keys for RIH. Either option works - RIH would likely be simpler because of the no-code, low-code aspect of it.
------------------------------
Ayan Basu
Original Message:
Sent: 07-27-2022 13:18
From: Gowthamprabhu Sivaraj
Subject: Connectivity between SQS and S3
The Recommendation varies from Organisation to Organisation based on their Approved Technology and Enterprise Standards. Since SQS is an AWS Component and S3 is also an AWS Component, to keep the stack simple I would prefer a Lambda which is again an AWS Component. By doing this I can easily deal with authentication S3 access via IAM Role attached to Lambda whereas RIH might need Access/Secret keys ( I assume and I could be wrong too).
------------------------------
Gowthamprabhu Sivaraj
AstraZeneca
Original Message:
Sent: 07-27-2022 11:17
From: Basudha Ghosh
Subject: Connectivity between SQS and S3
Hi Reltio team ,
What is recommended option to send the data from SQS to S3 (Customer Specific) ? Should we use RIH there or we should we AWS features ?
Thanks!
------------------------------
Basudha Ghosh
AxTRIA INC
Berkeley Heights
------------------------------