Skip to content
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

No obvious way to use VPC Interface endpoint #16

Open
madsenwattiq opened this issue Oct 10, 2018 · 1 comment
Open

No obvious way to use VPC Interface endpoint #16

madsenwattiq opened this issue Oct 10, 2018 · 1 comment
Assignees

Comments

@madsenwattiq
Copy link

madsenwattiq commented Oct 10, 2018

Maybe I'm missing something, but it looks like there's no obvious way to use this library with a VPC interface endpoint for Kinesis streams, to keep traffic internal to a VPC (and avoid the costs of sending the consumer/producer traffic over the public internet).

This would seem to be supported by Boto3's client constructor, so it should be a simple change.

self.kinesis_client = self.boto3_session.client('kinesis', endpoint_url="https://<URL>").

If you think this would be beneficial, am happy to send a PR.

@borgstrom borgstrom self-assigned this Nov 26, 2018
@victormpa
Copy link

Actually there is no need to fiddle with the application in this case. Having the right settings enabled on the VPC (DNS resolution) and creating the endpoint is enough.

You can read more here https://docs.aws.amazon.com/streams/latest/dev/vpc.html

Just make sure that the application resides in a subnet that has the endpoint enabled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants