-
Notifications
You must be signed in to change notification settings - Fork 467
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Overriding Endpoint with Kinesis private link Not Supported #308
Comments
In the process of looking at the code to submit fix I realized there is a workaround which is to set the AwsKinesisAgent explicitly via Worker.Builder().kinesisClient(client). Makes this issue less pressing. |
Can you explain how/where this workaround can be applied in order to patch the issue? I have this problem, but unfortunately I don't understand java well enough to understand how to apply what you are saying. Using the KCL via the Kinesis Python client library. |
In java you use the AmazonKinesisClientBuilder to create the client and set the endpointConfiguration. I will have to look at the Python library to see if equivalent exists. AmazonKinesisClientBuilder builder = AmazonKinesisClientBuilder.standard().withCredentials(credentials)
.withEndpointConfiguration(new EndpointConfiguration(endpoint, regionName));
|
It's currently not possible to override the client in the Python Library. We're currently working on the MultiLang Daemon for 2.0, and will look into supporting private link when explicitly setting the endpoint. Private link should work if you're using instance DNS and the resolution of the |
It would be really nice to be able to override the kinesis endpoint with a simple setting in the properties file in e.g. the KCL for Python. |
I'm using the KCLrb to build a consumer application and I would like to +1 that it would be beneficial to set the kinesis endpoint via a setting in the properties file. 💯 Using KClrb in a docker container with kinesis-mock to isolate the producer/consumer workflow and I am blocked because my consumer can't connect to the internal network kinesis stream. I am able to override the credentials and region, it only makes sense to override the kinesis endpoint/host. |
@pfifer this is a really old and open enhancement. Is this still not supported? |
Using 1.9.0
The text was updated successfully, but these errors were encountered: