-
Notifications
You must be signed in to change notification settings - Fork 191
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
secure=False required? #48
Comments
I use this with boto and it works fine: region = boto.sqs.regioninfo.RegionInfo(name='elasticmq',
endpoint=sqs_endpoint)
conn = boto.connect_sqs(aws_access_key_id='x',
aws_secret_access_key='x',
is_secure=False,
port=sqs_port,
region=region) where |
ElasticMQ exposes the API via HTTP, so it doesn't handle https in any way (would be quite complex given that you would have to provide certificates etc). If you could make a PR with README changes describing how to use EMQ from Boto (I never used that :) ), it would be great! |
Cool, #49 looks good. It doesn't explicitly call out Thanks! |
Hello,
I'm just getting started with elasticmq. I'm using boto (the official aws client) as the client, and I was running into a bunch of errors I didn't understand:
I was able to get it working by setting
is_secure=False
in boto (it defaults tois_secure=True
).I didn't see anything in the README about secure=False, or SSL. Is this expected? Is there some way to get it to work with secure? If not, could you add a note to the docs somewhere about that?
Thanks!
The text was updated successfully, but these errors were encountered: