This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
This is for reference in case the same thing happens, as I didn't find any information on the community regarding this error message, causing workflow to fail.
If you have a workflow loading any kind of data into AWS Redshift, you ought to use the Bulk Connector.
That Bulk connector includes credentials to a S3 bucket, which acts as a buffer to load the data into Redshift tables.
If suddenly you get hit by that error message related to the InboundNamedPipe, it means that the S3 credentials have been altered in a way.
After much head scratching and investigation, we finally figured out one employee had left the company, with credentials tied to the S3 bucket, which had effectively reset the Secret Key tied to the S3 bucket...
Hopefully, this knowledge tidbit will save you all the investigative effort...