AWS User Experience Customization
Read list services, get account customizations from uxc (SigV4).
OCNORA ships 3 typed AWS User Experience Customization 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 User Experience Customization
- 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 User Experience Customization
Operations, grouped by what they do to your data.
Read and search 2
Other operations 1
A sample AWS User Experience Customization workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no AWS User Experience Customization trigger is needed.
- 2Get Account Customizationsuxc.get_account_customizationsReturns the current account customization settings, including account color, visible services, and visible Regions.
- 3Write Actionuxc.callRun one of 1 write actions on uxc.
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 3
- Write ActionRun one of 1 write actions on uxc.uxc.call
- Get Account CustomizationsReturns the current account customization settings, including account color, visible services, and visible Regions.uxc.get_account_customizations
- List ServicesReturns a paginated list of Amazon Web Services service identifiers that you can use as values for the visibleServices setting in UpdateAccountCustomizations.uxc.list_services
AWS User Experience Customization questions
- How does OCNORA authenticate with AWS User Experience Customization?
- 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 User Experience Customization?
- 3 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the AWS User Experience Customization operation I need is not listed?
- Where AWS User Experience Customization 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 User Experience Customization?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are AWS User Experience Customization 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 User Experience Customization 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.