AWS Migration Hub
Read list migration tasks, list progress update streams, list source resources from Migration Hub (SigV4).
OCNORA ships 4 typed AWS Migration Hub 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 Migration Hub
- 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 Migration Hub
Operations, grouped by what they do to your data.
Other operations 1
A sample AWS Migration Hub workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no AWS Migration Hub trigger is needed.
- 2List Migration Tasksmgh.list_migration_tasksLists all, or filtered by resource name, migration tasks associated with the user account making this call.
- 3Write Actionmgh.callRun one of 12 write actions on Migration Hub.
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 12 write actions on Migration Hub.mgh.call
- List Migration TasksLists all, or filtered by resource name, migration tasks associated with the user account making this call.mgh.list_migration_tasks
- List Progress Update StreamsLists progress update streams associated with the user account making this call.mgh.list_progress_update_streams
- List Source ResourcesLists all the source resource that are associated with the specified MigrationTaskName and ProgressUpdateStream.mgh.list_source_resources
AWS Migration Hub questions
- How does OCNORA authenticate with AWS Migration Hub?
- 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 Migration Hub?
- 4 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the AWS Migration Hub operation I need is not listed?
- Where AWS Migration Hub 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 Migration Hub?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are AWS Migration Hub 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 Migration Hub 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.