Amazon Verified Permissions
Read list policy stores, list policies, get identity source from VerifiedPermissions (SigV4).
OCNORA ships 4 typed Amazon Verified Permissions 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 Amazon Verified Permissions
- 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 Amazon Verified Permissions
Operations, grouped by what they do to your data.
Read and search 3
Other operations 1
A sample Amazon Verified Permissions workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Amazon Verified Permissions trigger is needed.
- 2Get Identity Sourceverifiedpermissions.get_identity_sourceRetrieves the details about the specified identity source.
- 3Write Actionverifiedpermissions.callRun one of 21 write actions on VerifiedPermissions.
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 21 write actions on VerifiedPermissions.verifiedpermissions.call
- Get Identity SourceRetrieves the details about the specified identity source.verifiedpermissions.get_identity_source
- List PoliciesReturns a paginated list of all policies stored in the specified policy store.verifiedpermissions.list_policies
- List Policy StoresReturns a paginated list of all policy stores in the calling Amazon Web Services account.verifiedpermissions.list_policy_stores
Amazon Verified Permissions questions
- How does OCNORA authenticate with Amazon Verified Permissions?
- 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 Amazon Verified Permissions?
- 4 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Amazon Verified Permissions operation I need is not listed?
- Where Amazon Verified Permissions 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 Amazon Verified Permissions?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Amazon Verified Permissions 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 Amazon Verified Permissions 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.