Amazon RDS · Arazzo Workflow

Amazon RDS Reboot a DB Instance

Version 1.0.0

Reboot a DB instance with optional failover and poll until it recovers.

1 workflow 1 source API 1 provider
View Spec View on GitHub Cloud DatabasesDatabase ServiceDatabase-as-a-ServiceManaged DatabasesRelational DatabasesArazzoWorkflows

Provider

amazon-rds

Workflows

reboot-instance
Reboot a DB instance and wait for it to return to available.
Confirms the instance is available, reboots it (optionally forcing a failover), then polls until DescribeDBInstances reports the instance available again.
3 steps inputs: dbInstanceIdentifier, forceFailover outputs: endpointAddress, status
1
confirmInstance
Describe the DB instance to confirm it is available before rebooting.
2
rebootInstance
Issue the reboot request, optionally forcing a failover from one Availability Zone to another in a Multi-AZ deployment.
3
pollInstance
Describe the DB instance and inspect its status. While the instance is still rebooting the workflow loops back to poll again; once it is available the flow ends.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Amazon RDS Reboot a DB Instance
  summary: Reboot a DB instance with optional failover and poll until it recovers.
  description: >-
    Reboots a DB instance to apply pending changes or force a Multi-AZ failover,
    then waits for the database to return to service. The workflow confirms the
    instance is available, issues the reboot, and polls DescribeDBInstances until
    the status returns to available, looping while the instance is still
    rebooting. Every step spells out its request inline so the flow can be read
    and executed without opening the underlying OpenAPI description.
  version: 1.0.0
sourceDescriptions:
- name: dbInstancesApi
  url: ../openapi/amazon-rds-db-instances-api-openapi.yml
  type: openapi
workflows:
- workflowId: reboot-instance
  summary: Reboot a DB instance and wait for it to return to available.
  description: >-
    Confirms the instance is available, reboots it (optionally forcing a
    failover), then polls until DescribeDBInstances reports the instance
    available again.
  inputs:
    type: object
    required:
    - dbInstanceIdentifier
    properties:
      dbInstanceIdentifier:
        type: string
        description: The identifier of the DB instance to reboot.
      forceFailover:
        type: boolean
        description: Whether to force a Multi-AZ failover during the reboot.
  steps:
  - stepId: confirmInstance
    description: >-
      Describe the DB instance to confirm it is available before rebooting.
    operationId: describeDBInstances
    parameters:
    - name: DBInstanceIdentifier
      in: query
      value: $inputs.dbInstanceIdentifier
    successCriteria:
    - condition: $statusCode == 200
    - context: $response.body
      condition: $.dBInstances[0].dBInstanceStatus == 'available'
      type: jsonpath
    outputs:
      preRebootStatus: $response.body#/dBInstances/0/dBInstanceStatus
  - stepId: rebootInstance
    description: >-
      Issue the reboot request, optionally forcing a failover from one
      Availability Zone to another in a Multi-AZ deployment.
    operationId: rebootDBInstance
    parameters:
    - name: DBInstanceIdentifier
      in: query
      value: $inputs.dbInstanceIdentifier
    - name: ForceFailover
      in: query
      value: $inputs.forceFailover
    successCriteria:
    - condition: $statusCode == 200
  - stepId: pollInstance
    description: >-
      Describe the DB instance and inspect its status. While the instance is
      still rebooting the workflow loops back to poll again; once it is
      available the flow ends.
    operationId: describeDBInstances
    parameters:
    - name: DBInstanceIdentifier
      in: query
      value: $inputs.dbInstanceIdentifier
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      status: $response.body#/dBInstances/0/dBInstanceStatus
      endpointAddress: $response.body#/dBInstances/0/endpoint/address
    onSuccess:
    - name: stillRebooting
      type: goto
      stepId: pollInstance
      criteria:
      - context: $response.body
        condition: $.dBInstances[0].dBInstanceStatus != 'available'
        type: jsonpath
    - name: available
      type: end
      criteria:
      - context: $response.body
        condition: $.dBInstances[0].dBInstanceStatus == 'available'
        type: jsonpath
  outputs:
    status: $steps.pollInstance.outputs.status
    endpointAddress: $steps.pollInstance.outputs.endpointAddress

Work with this as data

Every workflow here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This workflow
curl "https://apis.io/api/v1/arazzo/amazon-rds-reboot-instance-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.