Impossible to connect to ext. eKuiper instances from ekuiper manager

[kriskonina]

How exactly does one provide a valid pair of ak and sk?

I tried putting signature block in kuiper.yaml like so:

signature:
  method: sha256
  ak: ...
  sk: ...

But can't even tell if this is recognized by ekuiper...

What's the way to achieve it?

[ngjaying]

@kriskonina When adding instance, just select direct link. eKuiper manager is not updated long ago, it does not support jwt authentication.

[ngjaying]

It is possible. Just make sure you can connect to that instance: curl http://your-ekuiper-host:yourport

[kriskonina]

@ngjaying, thanks again for clarifying. Here’s the thing—eKuiper Manager itself asks explicitly for AK/SK credentials when trying to connect to an external eKuiper instance (it won’t let me proceed without entering them). That’s exactly what’s tripping me up here.

If eKuiper Manager genuinely doesn’t support this kind of authentication yet, that’s totally fine—just let me know clearly. But if there’s a way to make it work, could you point me toward any docs or examples showing how the manager uses these AK/SK fields?

Really appreciate your help!

[ngjaying]

@kriskonina When adding new service, there should be a dropdown field to select service type. Select direct link service does not require credentials. If you cannot see this option, try to open in browser's ignite mode or update eKuiper manager version.

[kriskonina]

Ok, that's interesting, I'm running version 1.9.5-plus-ief and only have text input fields:

Should I downgrade?

[ngjaying]

that's it.Don't use ief version