blaze / blaze/odo

s3 connection fails in Frankfurt region due to missing host argument

Open
#494 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
1k
Forks
131
PR merge metrics
No merged PRs in 30d

Description

There is a known issue with Boto in which connections to Frankfurt require SigV4 which in turn requires a 'host' parameter:

BotoClientError: When using SigV4, you must specify a 'host' parameter.
http://stackoverflow.com/questions/26744712/s3-using-boto-and-sigv4-missing-host-parameter

When connecting manually with boto I can make it work by providing the host explicitly:
boto.connect_s3(host='s3.eu-central-1.amazonaws.com')

However, in Odo I don't have the ability to do this as the connect call is buried. Unfortunately I don't think it's possible to fix this in a boto config file. I was able to get it work by patching odo.backends.aws.get_s3_connection locally and hardcoding the host parameter which is not ideal.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.