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

Dynamodb local uses HTTPS instead of HTTP #819

Closed
jamesls opened this issue Mar 2, 2016 · 0 comments · Fixed by #830
Closed

Dynamodb local uses HTTPS instead of HTTP #819

jamesls opened this issue Mar 2, 2016 · 0 comments · Fixed by #830
Assignees
Labels
bug This issue is a confirmed bug.

Comments

@jamesls
Copy link
Member

jamesls commented Mar 2, 2016

In our endpoints.json we have:

            "local": {
              "hostname": "localhost:8000",
              "protocols": [
                "http"
              ],
              "credentialScope": {
                "region": "us-east-1"
              }
            }

However, creating a client with this region will use HTTPS:

>>> import botocore.session
>>> botocore.session.get_session().create_client('dynamodb', 'local').list_tables()
...
botocore.vendored.requests.exceptions.SSLError: [SSL: UNKNOWN_PROTOCOL] unknown protocol (_ssl.c:581)

My best guess is that we're not honoring the protocol key from endpoints.json when creating clients.

@jamesls jamesls added the bug This issue is a confirmed bug. label Mar 2, 2016
jamesls added a commit to jamesls/botocore that referenced this issue Mar 4, 2016
This fixes a bug where if you try to use
DynamoDB Local via `--region local`,
we'll try to connect over https:// despite
the fact that the `protocols` key for that
region indicates that only http is supported.

Also verified I could connect to dynamodb local
after these changes.

Fixes boto#819.
@jamesls jamesls self-assigned this Mar 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a confirmed bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant