AWS Single Sign-On Admin
Read list instances, list applications, list managed policies in permission set from SSO Admin (SigV4).
OCNORA ships 4 typed AWS Single Sign-On Admin 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 Single Sign-On Admin
- 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 Single Sign-On Admin
Operations, grouped by what they do to your data.
Other operations 1
A sample AWS Single Sign-On Admin workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no AWS Single Sign-On Admin trigger is needed.
- 2List Applicationssso_admin.list_applicationsLists all applications associated with the instance of IAM Identity Center.
- 3Write Actionsso_admin.callRun one of 40 write actions on SSO Admin.
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 40 write actions on SSO Admin.sso_admin.call
- List ApplicationsLists all applications associated with the instance of IAM Identity Center.sso_admin.list_applications
- List InstancesLists the details of the organization and account instances of IAM Identity Center that were created in or visible to the account calling this API.sso_admin.list_instances
- List Managed Policies In Permission SetLists the Amazon Web Services managed policy that is attached to a specified permission set.sso_admin.list_managed_policies_in_permission_set
AWS Single Sign-On Admin questions
- How does OCNORA authenticate with AWS Single Sign-On Admin?
- 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 Single Sign-On Admin?
- 4 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the AWS Single Sign-On Admin operation I need is not listed?
- Where AWS Single Sign-On Admin 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 Single Sign-On Admin?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are AWS Single Sign-On Admin 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 Single Sign-On Admin 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.