AWS FinSpace User Environment Management service
Read list kx environments, list kx users, list kx dataviews from finspace (SigV4).
OCNORA ships 4 typed AWS FinSpace User Environment Management service operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect AWS FinSpace User Environment Management service
- Authentication
- API key
- Credential
- {"access_key_id", "secret_access_key"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with AWS FinSpace User Environment Management service
Operations, grouped by what they do to your data.
Read and search 3
Other operations 1
A sample AWS FinSpace User Environment Management service workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no AWS FinSpace User Environment Management service trigger is needed.
- 2List Kx Dataviewsfinspace.list_kx_dataviewsReturns a list of all the dataviews in the database.
- 3Write Actionfinspace.callRun one of 26 write actions on finspace.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 4
- Write ActionRun one of 26 write actions on finspace.finspace.call
- List Kx DataviewsReturns a list of all the dataviews in the database.finspace.list_kx_dataviews
- List Kx EnvironmentsReturns a list of kdb environments created in an account.finspace.list_kx_environments
- List Kx UsersLists all the users in a kdb environment.finspace.list_kx_users
AWS FinSpace User Environment Management service questions
- How does OCNORA authenticate with AWS FinSpace User Environment Management service?
- With a stored API key credential, shaped {"access_key_id", "secret_access_key"}. A connection test can check it when you add it.
- What can I automate with AWS FinSpace User Environment Management service?
- 4 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the AWS FinSpace User Environment Management service operation I need is not listed?
- Where AWS FinSpace User Environment Management service has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use AWS FinSpace User Environment Management service?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are AWS FinSpace User Environment Management service calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first AWS FinSpace User Environment Management service workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.