When redshift is selected as the destination for kinesis firehose, a connection error occurs if Redshift is located on a private subnet.
We are testing the data load by selecting Redshift as the destination for Kinesis fire hose.
when Redshift is located on a private subnet, a connection error occurs in Kinesis firehose, and the same error occurs even when Kinesis firehose vpc enpoint is set.
If I choose Redshift as a firehose destination, is it impossible to communicate inside the VPC even if I create a kinesis firehose endpoint? Do I have to put redshift on the public subnet unconditionally?
I'll attach an error message here
The same error occurs when you open all of Redshift's security groups.
- Newest
- Most votes
- Most comments
Yes, you need to put Redshift in a public subnet if you want to use it as a destination in Kinesis Firehose.
To use Redshift as a destination in Firehose. If your Amazon Redshift cluster is in a virtual private cloud (VPC), it must be publicly accessible with a public IP address. You also need to grant Kinesis Data Firehose access to your Amazon Redshift cluster by unblocking the Kinesis Data Firehose IP addresses.
Reference: https://docs.aws.amazon.com/firehose/latest/dev/controlling-access.html#using-iam-rs-vpc
Relevant content
- asked 2 years ago
- asked 12 days ago
AWS OFFICIALUpdated 5 months ago- AWS OFFICIALUpdated 6 months ago
