Does LabVIEW Cloud Toolkit for AWS support Amazon Redshift?

[Plínio]

Hello guys,

I saw in LabVIEW Cloud Toolkit for AWS by NI page that the toolkit supports four services: 

-AWS S3: Simple Storage Service
-AWS SNS: Simple Notification Service
-AWS SQS: Simple Queue Service
-AWS IoT: Internet of Things

Does any of those services include or are similar to Redshift in a way that the toolkit will work with it? I don't have expertise on the Amazon web services, sorry if it was a dummy question.

Thanks

[Darren]

Redshift is a different service than S3, SNS, SQS, and IoT, so it is not currently supported by the LabVIEW Cloud Toolkit for AWS. Here is a complete list of all the Amazon services:

https://aws.amazon.com/documentation/

Here is the documentation for Redshift specifically:

https://docs.aws.amazon.com/redshift/latest/APIReference/Welcome.html

The LabVIEW Cloud Toolkit for AWS is implemented in a plug-in fashion that should allow you to implement your own class to support Redshift. You can also post to the LabVIEW Idea Exchange requesting the support be added by NI. For example, this user requested support for DynamoDB:

https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Add-DynamoDB-support-to-the-NI-cloud-toolkit-for-AWS/...

[Plínio]

Would it be possible to implement the communication just using for example the database connectivity toolkit, since communication is through ODBC (https://docs.aws.amazon.com/pt_br/redshift/latest/dg/c_high_level_system_architecture.html)?

https://docs.aws.amazon.com/pt_br/redshift/latest/dg/c_high_level_system_architecture.html

[Darren]

---

@Plínio wrote:

Would it be possible to implement the communication just using for example the database connectivity toolkit, since communication is through ODBC

---

I don't know, I'm only familiar with the REST APIs, which are used for all the services in the LabVIEW Cloud Toolkit for AWS. My guess is that it would be easier to follow the examples set forth in the existing LabVIEW APIs (S3, SQS, SNS, IoT) and implement Redshift with REST, as opposed to starting from scratch with ODBC. But then again, if you're an ODBC expert, you may feel differently. 🙂

[Plínio]

Definitely I'm not an ODBC expert lol. I'll go with REST APIs. I'm going to estimate the effort to develop it using this API so I can decide to go further in the RH or not.

Thanks for you help.