Amazon S3 · Arazzo Workflow

Amazon S3 Delete Object and Confirm Removal

Version 1.0.0

Delete an object then HEAD it to confirm it is gone.

1 workflow 1 source API 1 provider
View Spec View on GitHub ArchiveBackupCloud StorageData StorageObject StorageScalable StorageArazzoWorkflows

Provider

amazon-s3

Workflows

delete-object-and-confirm
Delete an object then verify it returns 404 on HEAD.
Removes a single object and confirms the removal by HEADing the key and expecting a not-found response.
2 steps inputs: bucket, objectKey outputs: deleteMarker, versionId
1
deleteObject
Delete the object from the bucket. S3 responds with 204 No Content on success.
2
confirmGone
HEAD the deleted key. A 404 confirms the object is no longer present.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Amazon S3 Delete Object and Confirm Removal
  summary: Delete an object then HEAD it to confirm it is gone.
  description: >-
    A clean teardown flow for a single Amazon S3 object. The workflow deletes the
    object with a DELETE request and then issues a HEAD request that is expected
    to return 404, confirming the object is no longer retrievable. 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: objectsApi
  url: ../openapi/amazon-s3-objects-api-openapi.yml
  type: openapi
workflows:
- workflowId: delete-object-and-confirm
  summary: Delete an object then verify it returns 404 on HEAD.
  description: >-
    Removes a single object and confirms the removal by HEADing the key and
    expecting a not-found response.
  inputs:
    type: object
    required:
    - bucket
    - objectKey
    properties:
      bucket:
        type: string
        description: The bucket holding the object.
      objectKey:
        type: string
        description: The key of the object to delete.
  steps:
  - stepId: deleteObject
    description: >-
      Delete the object from the bucket. S3 responds with 204 No Content on
      success.
    operationId: DeleteObject
    parameters:
    - name: Bucket
      in: path
      value: $inputs.bucket
    - name: Key+
      in: path
      value: $inputs.objectKey
    successCriteria:
    - condition: $statusCode == 204
    outputs:
      deleteMarker: $response.header.x-amz-delete-marker
      versionId: $response.header.x-amz-version-id
  - stepId: confirmGone
    description: >-
      HEAD the deleted key. A 404 confirms the object is no longer present.
    operationId: HeadObject
    parameters:
    - name: Bucket
      in: path
      value: $inputs.bucket
    - name: Key+
      in: path
      value: $inputs.objectKey
    successCriteria:
    - condition: $statusCode == 404
  outputs:
    deleteMarker: $steps.deleteObject.outputs.deleteMarker
    versionId: $steps.deleteObject.outputs.versionId

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-s3-delete-object-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.