You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After struggling for several hours with Docker Compose, I noticed my problem was actually in this library, which does not seem to support the virtual host addressing for the s3 client.
Looking at boto3 in debug mode, I noticed that when using Virtual host addressing, the HTTP request was aimed towards http://<bucket>.<endpoint_url>:<endpoint_port>. This is not a valid endpoint, and it should be http://<bucket>.s3.<endpoint_url>:<endpoint_port>, as described here.
After delving deeper I noticed localstack_client.config.get_endpoint it is not handling s3 in any special way. I manually patched the function and noticed that with a simple
I know this doesn't handle SSL, it's just a draft. It works for both virtual and path based addressing.
I see three ways simple about this:
Do not support virtual host addressing. This is a problem, as in theory AWS is deprecating path based addressing (also it has been deprecating it for 4 years, so...)
Do a hack like the one proposed.
Honor AWS service specific endpoints through envars (for instance AWS_ENDPOINT_URL_S3) and leave it up to the user to set it up (with appropriate documentation, at least in the README.md).
What are your thoughts on this?
The text was updated successfully, but these errors were encountered:
After struggling for several hours with Docker Compose, I noticed my problem was actually in this library, which does not seem to support the virtual host addressing for the
s3
client.Looking at
boto3
in debug mode, I noticed that when using Virtual host addressing, the HTTP request was aimed towardshttp://<bucket>.<endpoint_url>:<endpoint_port>
. This is not a valid endpoint, and it should behttp://<bucket>.s3.<endpoint_url>:<endpoint_port>
, as described here.After delving deeper I noticed
localstack_client.config.get_endpoint
it is not handlings3
in any special way. I manually patched the function and noticed that with a simpleI know this doesn't handle SSL, it's just a draft. It works for both virtual and path based addressing.
I see three ways simple about this:
AWS_ENDPOINT_URL_S3
) and leave it up to the user to set it up (with appropriate documentation, at least in theREADME.md
).What are your thoughts on this?
The text was updated successfully, but these errors were encountered: