Skip to content

can't connect to Firehose with VPC Endpoint  #66

Open
@hellotherecsy

Description

@hellotherecsy

HI.
I am having the following same problem.
#64

Both MSK / MSK Connect are in the same subnet and VPC.
and create vpc endpoint for firehose ( contain all subnet )
According to the msk connect log, it is returned as a public firehose ip, so it cannot be connected to the internal network.
( public ip : 52.x.x.x , private ip : 172.x.x.x )

[Worker-0891d75ae83741fe2] Caused by: org.apache.http.conn.ConnectTimeoutException: Connect to firehose.ap-northeast-2.amazonaws.com:443 [firehose.ap-northeast-2.amazonaws.com/52.95.196.17] failed: connect timed out

52.x.x.x mean Public IP

I've been working with a Mac, carriage returns ( \r ) are not visible in the config.

When I test DNS in EC2, it is possible to return a private IP, but in MSK Connect, it is not. I need some advice on where I am doing wrong.

Thank you!

[EC2 Log ]
image

[MSK network]
image

[MSK Connect network]
image

[VPC Endpoint]
image

below is my conf for msk connect

connector.class=com.amazon.kinesis.kafka.FirehoseSinkConnector
batchSizeInBytes=3670016
tasks.max=1
topics=customer
kinesisEndpoint=firehose.ap-northeast-2.amazonaws.com
name=dw-kakfa-to-firehose-08
batch=true
deliveryStream=dw-firehose-test-01
region=ap-northeast-2
batchSize=10

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      can't connect to Firehose with VPC Endpoint · Issue #66 · awslabs/kinesis-kafka-connector