Amazon Bedrock AgentCore Control
Read list datasets, list gateways, list gateway rate limits from Bedrock AgentCore Control (SigV4).
OCNORA ships 4 typed Amazon Bedrock AgentCore Control 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 Bedrock AgentCore Control
- 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 Bedrock AgentCore Control
Operations, grouped by what they do to your data.
Read and search 3
Other operations 1
A sample Amazon Bedrock AgentCore Control workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Amazon Bedrock AgentCore Control trigger is needed.
- 2List Datasetsbedrock_agentcore_control.list_datasetsLists all datasets in the caller's account, paginated.
- 3Write Actionbedrock_agentcore_control.callRun one of 92 write actions on Bedrock AgentCore Control.
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 92 write actions on Bedrock AgentCore Control.bedrock_agentcore_control.call
- List DatasetsLists all datasets in the caller's account, paginated.bedrock_agentcore_control.list_datasets
- List Gateway Rate LimitsLists all rate limits for a gateway. Results are paginated. Use the nextToken parameter to retrieve additional results.bedrock_agentcore_control.list_gateway_rate_limits
- List GatewaysLists all gateways in the account.bedrock_agentcore_control.list_gateways
Amazon Bedrock AgentCore Control questions
- How does OCNORA authenticate with Amazon Bedrock AgentCore Control?
- 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 Bedrock AgentCore Control?
- 4 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Amazon Bedrock AgentCore Control operation I need is not listed?
- Where Amazon Bedrock AgentCore Control 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 Bedrock AgentCore Control?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Amazon Bedrock AgentCore Control 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 Bedrock AgentCore Control 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.