AWS Backup Search
Read list search jobs, list search result export jobs, list search job backups from BackupSearch (SigV4).
OCNORA ships 4 typed AWS Backup Search 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 Backup Search
- 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 Backup Search
Operations, grouped by what they do to your data.
Other operations 1
A sample AWS Backup Search workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no AWS Backup Search trigger is needed.
- 2List Search Job Backupsbackupsearch.list_search_job_backupsThis operation returns a list of all backups (recovery points) in a paginated format that were included in the search job.
- 3Write Actionbackupsearch.callRun one of 5 write actions on BackupSearch.
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 5 write actions on BackupSearch.backupsearch.call
- List Search Job BackupsThis operation returns a list of all backups (recovery points) in a paginated format that were included in the search job.backupsearch.list_search_job_backups
- List Search JobsThis operation returns a list of search jobs belonging to an account.backupsearch.list_search_jobs
- List Search Result Export JobsThis operation exports search results of a search job to a specified destination S3 bucket.backupsearch.list_search_result_export_jobs
AWS Backup Search questions
- How does OCNORA authenticate with AWS Backup Search?
- 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 Backup Search?
- 4 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the AWS Backup Search operation I need is not listed?
- Where AWS Backup Search 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 Backup Search?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are AWS Backup Search 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 Backup Search 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.