This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-07-25
Channels
- # aleph (2)
- # aws (2)
- # beginners (37)
- # boot (23)
- # cider (29)
- # clara (34)
- # cljs-dev (2)
- # cljsrn (17)
- # clojure (230)
- # clojure-dev (47)
- # clojure-italy (11)
- # clojure-nl (2)
- # clojure-poland (5)
- # clojure-russia (52)
- # clojure-sg (1)
- # clojure-spec (70)
- # clojure-uk (73)
- # clojurescript (31)
- # core-async (9)
- # cursive (15)
- # datomic (39)
- # events (1)
- # graphql (1)
- # lein-figwheel (2)
- # luminus (13)
- # off-topic (2)
- # onyx (29)
- # other-lisps (1)
- # parinfer (15)
- # pedestal (14)
- # re-frame (41)
- # reagent (24)
- # ring (4)
- # ring-swagger (12)
- # rum (1)
- # spacemacs (3)
- # specter (1)
- # test-check (13)
- # timbre (9)
- # unrepl (29)
- # vim (5)
@stephenmhopper just a shot in the dark, but maybe you forgot to set the region ?
@lmergen Nope. It looks like I needed "sqs:GetQueueUrl"
as well. I was passing in the region and queue-name, so I'm guessing the plugin needed permissions to fetch the URL too. I added "sqs:GetQueueAttributes"
too, but I'm not sure if it was required.
Hello all, I've finally got round to attempting the aforementioned SSL auth test with my Onyx setup and I was wondering if anyone might recognise the madness I've produced in my logs? Any guidance would be greatly appreciated as I expect I'm simply not providing a config parameter that it is expecting or that the plugin simply cannot make an SSL connection even though I am attempting to pass the correct config params.
My apologies if this is Off Topic =D
@lucasbradstreet I created a PR for the AWS role privilege list here: https://github.com/onyx-platform/onyx-amazon-sqs/pull/8
@theblackbox I set up an authenticated Kafka SASL connection once. It.. was difficult. I’d take Onyx completely out of the equation until you make sure that your connection is being established from a normal consumer.
There’s very little in the way to do with Onyx other than provide the right consumer settings, so a plain Kafka broker is your best bet.
@stephenmhopper Thanks for the PR. I’m sure that will save someone a headache in the future.
@michaeldrogalis Yeah, I sure hope so
Debugging AWS permissions is never fun
Top 5 least favorite activities.
What are the other 4?
Classloader / dependency issues?
At least with that one, I can unpack the jar and see what’s inside. Sometimes AWS just feels like a black box for things like security.
That’s true
We’ve put a new interactive post up discussing session windows (built with onyx-local-rt). Hope you like it http://pyroclast.io/blog/2017/07/25/patterns-session-windows.html
Everything in it applies to Onyx as much as Pyroclast
@michaeldrogalis thanks for the heads up. I've got SSL comms established via the command line tools. I haven't checked via the REST API yet. We're using a confluent stack, but that's neither here nor there from what I understand. I was mostly just hoping the logs jogged someone's memory and I'd simply forgotten some setting.
ZK and Kafka versions?
but I think what you are saying to me is get out of Onyx land and use something clojure native to proof my setup
We haven't tested against Kafka 0.11 yet.
And yes that would be ideal
We're happy to help later but it'll be a bit hard without starting from the basics
@lucasbradstreet I'd asked before and was assuming that making the leap from command line consumer/producer to passing those same configs through to onxy/kafka-plugin wouldn't be too great a leap to make
the Kafka 0.11 mention was in case you’re using the latest
definitely not v11 but don't know for certain the versions on confluent, I'd say it uses 0.10.1.2 off the top of my head though
but I'll stop trying to run before I'm walking and head back to clojure and take things slowly
OK, cheers
thanks for the help as ever =D