-
Notifications
You must be signed in to change notification settings - Fork 101
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
Connect to local dynamo DB instance #59
Comments
I run dynamodb local on
|
@thegeez just FYI that that namespace is explicitly called out as "Impl, don't call directly." and intentionally missing from API docs. We're thinking through a more comprehensive solution for this and some other related issues, but no guarantee that this code doesn't change before that arrives. |
|
I would like the ability to connect to amazon's local dynamoDB instance that is used for running and testing locally. See https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DynamoDBLocal.html
After getting the dynamo DB instance running on my machine, I try to use the provided endpoint override provided like so:
This give me an error where I'm unable to connect because
endpoint-override
does not expect a port number.To mitigate this I can change the local docker container to listen on port 443 like this library expects (no big deal),and not specify the port on the
:endpoint-override
This yeilds an SSL error, since the local dynamoDB image provided by amazon does not support SSL. Their examples show using a plain http connection.
Some relevant system info:
I've tried running dyanmo DB with amazon's provided jar file. I also tried it with docker (to override the default port).
My clojure dependencies for this project are
I'm not sure what the best solution is, but from a conversation on the aws channel in clojurians slack, it was suggest that providing an option to not use HTTPS may be an answer. I'd be willing to help implement this, or whatever other solution seems best if yall are willing to consider it.
Thanks!
The text was updated successfully, but these errors were encountered: