Error 504 when creating Redshift connector in POC setup

Slack Knowledge Base Q&A Connector Questions
, , , ,
1

Summary

Error 504 encountered when creating Redshift connector in a POC setup on a local Mac. IAM user associated with the API key only has access to S3. Data seems to be created in S3 and Redshift before the error.


Question

Hey! :wave: Lovely tool you guys have built - love it!
Im currently evaluating it to be used for us, mainly shuffling data from AWS Postgres RDS to Redshift.
As initial solution i am drafting a POC with Airbyte created locally on my mac, having connectors to local postgres instance as well as Redshift in AWS.
When creating the redshift connector i end up with 504 error.
However i do notice that both S3 and Redshift seem to have some data created from airbyte, so something works before 504.
Any idea what it may be? The IAM user associated with the api key only has access to S3


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["error-504", "redshift-connector", "poc-setup", "local-mac", "iam-user", "api-key", "s3-access"]
2

Hi <@U07N0K08JTS>
Majority of the times I get this 504 error is when the “testing of the source” fails for some reason

when you test the source before creating the connector, does it work?

There are some steps that get tested only when setting up the connection, for example getting schemas from the tables/streams it’s going to create

Try to setup the connection and tail the logs while it does that

3

Thanks!
Had some issue with VPC between redshift and S3.
Oddly enough some prior version of the redshift connector worked

4

works now after fixing vpc